The database configuration table row for SESSION_WRITE_DIRECTORY keeps getting reset to <my-renamed-admin>/includes/cache, and the admin page would not load until I created this directory and made it writable.
The database configuration table row for SESSION_WRITE_DIRECTORY keeps getting reset to <my-renamed-admin>/includes/cache, and the admin page would not load until I created this directory and made it writable.
That Software Guy. My Store: Zen Cart Support
Available for hire - See my ad in Services
Plugin Moderator, Documentation Curator, Chief Cook and Bottle-Washer.
Do you benefit from Zen Cart? Then please support the project.
I've not seen this happen, at least not on a multitude of linux servers. What's your environment?
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Fedora Core 13, Apache, PHP 5.3.15.
That Software Guy. My Store: Zen Cart Support
Available for hire - See my ad in Services
Plugin Moderator, Documentation Curator, Chief Cook and Bottle-Washer.
Do you benefit from Zen Cart? Then please support the project.
I just did a test by changing the value for SESSION_WRITE_DIRECTORY to point to an invalid folder. Then went to the admin URL and it let me log in and work fine without any unexpected redirects.
Help me trigger the problem. Were you starting from a point of having just an import of an old database which had the wrong SESSION_WRITE_DIRECTORY set? Or was it an old configure.php that was pointing to wrong folders too? or both?
I would assume that all of the logic for the symptom you're reporting is handled by /admin/includes/init_includes/init_cache_key_check.php
Upon looking at it I can only think of one thing that might be a problem, and that's if you had put the init_cache_key_check.php file into the init_includes/overrides folder for some reason ... in which case it might generate the wrong path. We'll consider addressing that in a future version, but there should be no need to do an override on that file, so that issue feels minor.
Not sure how exactly to trigger what you're reporting though.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
The only thing old was an old configure.php file, which I pulled from my 151 installation and updated the catalog dir, logs dir, db, etc. I didn't notice any new entries in this file that were added since 1.5.1, but maybe I missed something. The file is attached.
A new db with test data was used. No other changes from vanilla 1.5.3 were made.
That Software Guy. My Store: Zen Cart Support
Available for hire - See my ad in Services
Plugin Moderator, Documentation Curator, Chief Cook and Bottle-Washer.
Do you benefit from Zen Cart? Then please support the project.
Hmmmm. Even testing with that I can't seem to trigger it.![]()
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.