Disappearing $_COOKIE question

The htaccess idea has not worked. I will use it though since I find it useful.

I think the problem could be Wayfinder.

In Firefox the "About Medicine Garden" link points to [www.medicine-garden.com.au] even though I have set the htaccess to use [www.medicinegarden.com.au]. In Opera it points correctly to [www.medicinegarden.com.au] only when it is clicked the result is the same, if I put the home page in manually using [index.php?id=2] the cart summary works fine.

I think I’ve isolated it all down to Opera and Wayfinder.

Is there a way to get Wayfinder to work they way it used to? IE. refer to start page by using index.php?id=##. This might be a quick fix for me. I can’t locate it in Wayfinder.inc.php.

I think you are still confused a little; I dont see how this has anything to do with a component in your site, least of all Wayfinder. The issue here is whatever domain is being reported by the client device to the web server when accessing a page will likely get cached into that page’s base tag. This will cause all the links to go to whatever domain is cached their, or if not cached, whatever domain the current client device is using to access it.

In addition to www and non-www urls being on different sessions, if you can access your site from more than one domain, you likely need to force all requests to the correct one. Here is an example of doing that, which you should be able to combine with your www/non-www rule...

I’ve already done the htaccess. It has worked okay for so far with testing on all but Opera. I have repeatedly cleared all cookie/history and repeating the process I still get the same results.

If it is not Wayfinder, then it only leaves Opera as a possible source of the problem. Even if Wayfinder is not the problem the work around to get it working in Opera is to get Wayfinder pointing once again using index.php?id=##.

Please post the exact links that you’re seeing in WayFinder (the code generated for your menus) and your .htaccess rewrite rules. If you have your .htaccess set up properly to force all requests to use "www.yourdomain.com" (or whatever) then you shouldn’t have cookie/session problems in any browser (this is really not a browser-dependent issue). You also want to make sure that your base href is set properly in your templates, but even if that’s wrong if your .htaccess is right it shouldn’t matter afaik.

I found this post which might explain a bit, I tested the issue with Opera 9.24, 9.26.

http://forums.digitalpoint.com/showthread.php?t=700430


As the post states, if I type in the address all works fine in Opera.

Thanks ZAP for the support.

I won’t post your requests yet.

For the moment I am going to try and locate the issue in the Opera forums. If I can get the answers there I will leave it as an Opera issue.

Quote from: Tybek at Feb 27, 2008, 08:10 PM

For the moment I am going to try and locate the issue in the Opera forums. If I can get the answers there I will leave it as an Opera issue.

If it does turn out to be a weird Opera issue, please do let us know (since it will likely come up again).

I am awaiting a response on the Opera forums.

So what follows is a guess only.

It appears Opera caches the page for 5 minutes, particularly the one page that is the start page.

The thing is though it checks the page if it has changed. I don’t know how this check works since it affects the only one link that shows the start page. That it does not affect the current site in Opera is also interesting, I am going to take a guess and ask ’what if’ this is an issue with the way eval() and snippets work in MODx, the result to Opera is an unchanged page.

Either way I’ll put an update here if I get a reply on the Opera forums.

Below is the complete reply to my post on Opera forums by yngve - Senior Developer.

Whole topic post is http://my.opera.com/community/forums/topic.dml?id=222819&t=1204171393&page=1#comment2467555

why is it affecting caching of a specific link. Since the site works fine in Opera without the CMS and the CMS uses PHP eval’d() may be this could be the issue because maybe does not see the change. Still the question is why it affects one link is puzzling.

PHP? If an ordinary webresource is expired then Opera will send a "is this updated?" request to the server. The problem is that many servers do not know that PHP generates content, so they check the last modified date sent by Opera against the PHP-file’s last modified date, not the date of the content that would have been produced. This is a quite possibly just a configuration problem on the server.

Why is it not a problem for certain other clients? They apparently send full unconditional requests far more often than we do, quite possibly increasing the load and bandwidth cost for servers that mostly deliver static content.

I guess Opera sees their function as a feature. Strange that the site works fine in Opera without MODx. I might be missing something obvious here.