Thanks, but the error only happens when the template override file exists.
And after using the debugger, it doesn't seem to be an error at all as there was no file added to the cache.
Thanks, but the error only happens when the template override file exists.
And after using the debugger, it doesn't seem to be an error at all as there was no file added to the cache.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
so the debugger would give no error result if there was a syntax error?
I initially only used the actual file downloaded from this page
http://jam.jrox.com/docs/index.php?article=228
the url was the only change as indicated in the instructions
What software program/editor are you using to edit your PHP file?
If you are not using a plain text editor - such as Crimson Editor or Notepad++ - then you may inadvertently be corrupting the file.
WinSCP's internal simple text editor, which I use for basically all development.
I even tried uploading the page again, but as binary, and editing it live, and I get the same result.
Have you tried doing a WINMERGE comparison of your edited file and the original file?
(Perhaps you can do another edit of the original in plain old "notepad", rather than WinSCP).
In any event, as Dr Byte has hinted, there's likely to be a syntax error, and (as you know), this can be as small as a misplaced ' in PHP.
I have jrox working just fine on my sites, so I know my footer tracking code works OK.
I even tried it with the code for less than v 1.3.8 and I get the same result, so there must be an error in how the footer file is being included or something like that.
Next I'm going to try to just edit a copy of my regular footer template to include the integration code myself