Just as a wild guess, the character encoding on the local server may be different than what you expect. But that may not be it at all.
To get an accurate idea of where in which script the actual error is, you must put all of the scripts on the page (no external script tags). That way when the error is reported, you should be able to go to that line number to see what is happen either on that line, just above or below it.
If the error is in the served source, but not in the page as an HTML page, once you have all of the scripts on the page serve it as PHP and use the browser's 'view source' to see the served code. Copy that to your editor to find the line number.
It helps if you have a text editor that shows and can jump to specific line numbers. Notepad++ (a free program available on the web) is good for that, if you have nothing like that already.
One other thing worth mentioning is that localhost servers don't always accurately reflect what will happen on the web, so it would be a good idea to actually publish the page to see if it works OK on the web. If you need more help with it, you will need to do that anyway, as we cannot guess what the problem is without seeing it:
Please post a link to the page on your site that contains the problematic code so we can check it out.
Even with that, this one may be a bit of a problem if we cannot recreate the problem locally from the served files. But we will worry about that when and if we get that far, as it may be quite simple to solve once we see it. That's assuming you cannot fix it yourself, or it doesn't go away in a live implementation.
Bookmarks