Yep, but... you might want to make sure and wait for someone else to confirm this as I am not completely sure. Better yet, why don't you ask the iPage guys because they can give you an answer better...
Apologies - misread post - tis late..
This post has been edited by.
: 25 April 2004, 22:07..
Thats ok. Just wondering if it is a bug/typo (perhaps intended to be called if $SID is.
Empty, rather than empty...).
In case it is relevent, our store uses the following other session type settings:.
STORE_SESSIONS = mysql.
Prevent Spider sessions = TRUE.
Force cookie use = FALSE.
Check SSL Session ID = FALSE.
Check User Agent = FALSE.
Check IP Address = FALSE.
Recreate Session = FALSE.
Running OSC2.2MS2 on PHP v4.3.4 (Zend: 1.3.0) and MySQL 3.23.58.
Your cookie iPage domain and path must be wrong in includes/configure.php. Links with SIDs cant be cached but once a cookie is recieved the SIDs should go away...
Ah, so the cache feature is not designed to work with Force Cookies = False....
Thanks for clearing this up. This should perhaps get into the documentation somehow as the forums are full of people trying to get this working by creating empty files in their cache folders....
No, the cache works fine with force_cookies as false. osC tries to set a cookie - if it succeeds, all is well. If not, then it tacks on the SID to each URL. This is how I set up my store and the cache works just fine...
Referencing the following page:.
That means if SID is not empty, that the session ID is being used on the URL..
If session ID's are then cached, then everyone on the iPage site would share the same session ID (due to it existing in pure HTML form in the cached file)..
The check to see if SID is empty is to ensure that session IDs are never cached - meaning those with session IDs in the urls (cookies disabled?) never receive a cached segment and those with session IDs in the cookie do receive the cached segment..
The new database class implementation that will be finalized in the 2.2 Milestone 3 release will fix such cases where database results are cached instead of HTML segments...
Thanks to all for clearing this up - there was a typo in our cookies directory path in configure.php which was causing the issue. As you said, no cookies, no cache....
I have the cache feature enabled (correctly) - i.e..
Use Cache -> True.
Cache Directory set (with ending slash) and permissions correct.
But the files do not show up. I have figured out that the issue is to do with the 'if' statement that calls the cache in the column_left.php page:.
If the code is changed to exclude the && empty($SID) part, the cache works just fine..
Can anyone explain the reason for the $SID to be empty in order to use cache, if this can safely be removed to ensure cache works, or any other setting that shoudl be looked at to make cache work with code as is..
Thanks for posting, but this wasn't useful - as I said,.
Cache is set up correctly.
It is just not being called becuase the SID is set as soon as a page is loaded (unless by a spider, of course)..
I am looking for more than the newbies answer.