Client-side mystery

lucianoes

    Dear friends, one of my browsers is not working properly with PHP. Read on...
    The browser: I test my site in several browsers. Among them, there is one called Act 7. It is a very old and limited browser. Version 7 is not even distributed anymore, and is currently replaced by version 10. If you're very very curious, you can find it at http://www.jansfreeware.com/jfinternet.htm, but I don't think you should bother. I just use it to bullet-proof my HTML code, making sure I am not using design that will look awful in very humble browsers. I prefer version 7 exactly because it is more feature-limited (but looks a lot better) than version 10.
    The problem: I am using a single PHP template and a wide range of includes to generate all pages on the fly. Links are passed as variables to let PHP know what it is supposed to generate, but some of the links are not working with Act 7. PHP generates error messages telling me that it cannot find the includes. The paths to the includes displayed in the error message are slightly messed up, not the correct ones. Sometimes it fails to find pictures too. It only happens with PHP. If I use plain HTML, I have no problems. I am sure there is nothing wrong with the code. It only happens with Act, and only with version 7. Many of the links are present in more than one page, and will work from a page but fail from another.
    My question: already convinced and in peace with the fact that something is wrong with Act 7 and that the chances of someone visiting my site using Act 7 are absolutely remote, isn't PHP supposed to be client-proof? How far can I rely on the server-side aspect of PHP?

    Thank you all,
    Luciano ES
    Santos - SP - Brasil

matto

messed-up filenames and paths remind me of one issue:
have you tried using urlencode() and urldecode() befor/after transferring such data? (maybe newer browsers do this encoding automatically while act doesn't.)

if no, have a look at the reference. perhaps it's a solution.

glowball

When it gets to the browser it isn't PHP anymore (it's just HTML or Javascript, etc.), so if you view the source code you should find the answer there. Can we get a link to the page? Could these be Javascript errors and not PHP errors?