Started by wendycroft, June 05, 2012, 05:08:39 PM

Previous topic - Next topic


My client has come in with this rather weird error message that shows up for him and some of his members in the URL bar. I've attached a picture for your perusal because I don't get it and can't replicate it.

    Version(s) of SMF:    SMF 2.0.2
    Your Setup:
        List any Modifications you have installed:

1.    SMFPacks: SEO Pro Mod    1.1.3    
2.    Next Post Level    1.3.3    
3.    Anti-SID(PHPSESSID) canonical tag    0.4    
4.    Apache Error Handler    1.2    
5.    SMF 2.0.2 Update    1.0    
6.    SMF 2.0.1 Update    1.0    
7.    Welcome Topic Mod    2.1    
8.    reCAPTCHA for SMF    0.9.8a    
9.    SimplePortal    2.3.3

        List any Themes you have installed:

        List any non-English Language packs you have installed

        Are you using UTF-8?

Not sure

        Any other related information?

        What caching level are you using?

Level 1

    Server Software:
        Apache/IIS version?:
        PHP version?:
        Database type and version:
        Any other related server information?

How do I get hold of that?

    Where the Error Occurred
        File: N/A
        Line: N/A
        Any relevant errors in the SMF error log (if so please post them)?:

Please see attachment
We've got pages and pages of these

    How to Reproduce this Error?: I can't
Additional Information?

Client says it's been there for a while.

"Do you know how to disable the PHPSESSID from showing up in the forum URL? It usually shows up on the front page for instance."

"I don't believe this is related with the Plugin. This is happening for quite some time now. Somehow I can't replicate it either."

All I've got to go on is the pic and the error logs. Can anyone shed any light on this, please?


It'll show up on the front page but should disappear thereafter assuming cookies are enabled.

If the user has disabled cookies for your forum, it'll appear, and there's no way around that part of it.



That tip won't actually affect PHPSESSID cookies as created in SMF, however ;)


I bow to your superior knowledge, mate. :)


Whoa, that was quick! So all I have to do is tell the client that it's about whether cookies are enabled or disabled on his browser, and enabling cookies is the solution? Please confirm.


Basically, yes. Once cookies are enabled, the first page load (but ONLY the first page load) will have PHPSESSID in it - it's only put there in the URL when a cookie isn't sent to the site.


Great! Thank you both.   :D