Printable View
Quote:
Originally Posted by Congerman
Umm, well, other technology changes (PHP specifically) may force you to do otherwise. Any currently acceptable version of PHP is already ahead of the original design parameters of ZC 1.5.1... PHP 5.4 is considered even below minimum recommended by the PHP community and with that ZC 1.5.1 requires minor mods...5.6 is the minimum suggested and 7.0 is becoming commonplace (ZC 1.5.5 is the first version that will support that).
ok dam more work on my, and my customers, 22 zen cart shops lol Good night and thank you for the advice
I've just moved my site to a new server, and have expereinced the same error.
The Fix Cache Key module is not supposed to be needed after v1.5.3. I'm running v1.5.5d, so should I still use this, or will this cause problems?
I had a dedicated IP with SSL on the old server. Had my whole cpanel account moved over to another server, including the SSL certificate (no dedicated IP on the new server, don't think I need it). Not sure if all that is relevant, but everything appears to be working perfectly on the new server, except the logout page throwing up re-direct errors.
Perhaps there's just a cache I need to clear???
So I just went to https://tabletennisshop.com[dot]au/ (based off of the signature in your post), didn't create an account, but went to index.php?main_page=logoff, and had no difficulties. Perhaps things would be different if I had an account, but that would require you to confirm that you also had issues when attempting what I did. Ie. If you had problems but I didn't, then would suspect something local to your computer/browser. If I (and others including yourself) could do the above, then there is something with being logged in that is likely the issue. Understand that finding that issue requires more than just saying I have a problem... need to understand what is installed, how things have been modified away from the default installation and what has been incorporated to cause/allow the issue...
Thank you for trying that. yes that is the correctg site.
Yes that URL worked fine for me as well. But it does not work if I actually log in, then click the logout link.
I also tried from a browser (IE), that I had not used before for this site. I created an account, logged in, then logged out. It worked first time (although it seemed to take a long time). Tried it again, then it came up with the same error (too many redirects).
I've since cleared all the data and cookies from the browser, it still comes up with the error.
Old server: SSL + dedicated IP
New server: same SSL certificate but no dedicicated IP
Old server PHP 5.4
New server: PHP 5.6 or 7.1
As I mentioned, the site worked perfectly on the old server. When the complete cpanel account was moved to a new server, this issue started happening.
Should I run the Fix Cache Key module, or will this not work on v1.5.5d?
The site is pretty much a standard installation, freshly installed from v1.5.5d with the sheffield blue responsive module. No other modules installed that modifiy URLs or anything like that.
I temporarily renamed my .htaccess to see if that was causing it, but that made no difference.
I'm really don't know where to start with this... if anyone can offer any tips, I'd really appreciate it!
Check your /includes/configure.php file, making sure that it's "in sync" with any .htaccess redirect directives.
That is, if your configure.php contains a www. prefix, make sure that the .htaccess isn't redirecting to non-www. (and vice versa).
Make sure, too, that your configure.php specifies either 'true' or 'false' for the USE_SSL definition; I've seen 1.5.5 upgrades where it's set to '' (an empty string), which can be problematic.
to make sure i understand, this worked perfectly before; the site was moved to a new server; and now you are getting too many redirects before it errors out? is that correct?
if so, it seems that your new server is configured differently than the old server. from what i can gather, the logoff page is NOT destroying the session data. the code from:
includes/modules/pages/logoff/header_php.php
this would explain why the page works perfectly if one is not logged in, but fails when the customer is logged in. so something is different on the server with regards to the session data.Code:/**
* Check if there is still a customer_id
* If so, kill the session, and redirect back to the logoff page
* This will cause the header logic to see that the customer_id is gone, and thus not display another logoff link
*/
if (!empty($_SESSION['customer_id']) || !empty($_SESSION['customer_guest_id'])) {
zen_session_destroy();
zen_redirect(zen_href_link(FILENAME_LOGOFF, $logoff_lang));
}
one could try the following code:
and see if that addresses the problem.... but i'm really guessing blind based on some reading i'm doing.Code:/**
* Check if there is still a customer_id
* If so, kill the session, and redirect back to the logoff page
* This will cause the header logic to see that the customer_id is gone, and thus not display another logoff link
*/
if (!empty($_SESSION['customer_id']) || !empty($_SESSION['customer_guest_id'])) {
session_start();
zen_session_destroy();
zen_redirect(zen_href_link(FILENAME_LOGOFF, $logoff_lang));
}
there are plenty of threads out there on session_destroy not deleting $_SESSION variables. the above references one such solution.
good luck!