Re: Admin Login - Loop Of Death II
Good morning.
Thank you for your continued attempts to help me. I think you're suggesting that I update the three files as outlined in this github post:
https://github.com/zencart/zencart/pull/6038/files
The third file is in the zc_install directory, which, if I'm not mistaken, is a directory that gets deleted after the install, so it is no longer there for me to update. I've updated the other two files just as the github files outline, but the problem persists. I still cannot login.
I tried clearing my browser cache, and I tried from another computer with a cleared browser cache.
I appreciate your time. Is there anything else that you can suggest, or should I throw in the towel at this point?
Re: Admin Login - Loop Of Death II
Please post the upper section of the site's /zcadmin/includes/configure.php, starting with the HTTP_SERVER definition and ending with the DIR_FS_CATALOG one.
Re: Admin Login - Loop Of Death II
Quote:
Originally Posted by
lat9
Please post the upper section of the site's /zcadmin/includes/configure.php, starting with the HTTP_SERVER definition and ending with the DIR_FS_CATALOG one.
Certainly. Thank you.
define('HTTP_SERVER', 'https://www.dans.com');
/**
* Note about HTTPS_SERVER:
* There is no longer an HTTPS_SERVER setting for the Admin. Instead, put your SSL URL in the HTTP_SERVER setting above.
*/
/**
* Note about DIR_WS_ADMIN
* The DIR_WS_ADMIN value is now auto-detected.
* In the rare case where it cannot be detected properly, you can add your own DIR_WS_ADMIN definition below.
*/
/**
* Enter the domain for your storefront URL.
* Enter a separate SSL URL in HTTPS_CATALOG_SERVER if your store supports SSL.
*/
define('HTTP_CATALOG_SERVER', 'https://www.dans.com');
define('HTTPS_CATALOG_SERVER', 'https://www.dans.com');
/**
* Do you use SSL for your customers login/checkout on the storefront? If so, enter 'true'. Else 'false'.
*/
define('ENABLE_SSL_CATALOG', 'true');
/**
* These DIR_WS_xxxx values refer to the name of any subdirectory in which your store is located.
* These values get added to the HTTP_CATALOG_SERVER and HTTPS_CATALOG_SERVER values to form the complete URLs to your storefront.
* They should always start and end with a slash ... ie: '/' or '/foldername/'
*/
define('DIR_WS_CATALOG', '/zencart/');
define('DIR_WS_HTTPS_CATALOG', '/zencart/');
Re: Admin Login - Loop Of Death II
... and the DIR_FS_CATALOG setting?
Re: Admin Login - Loop Of Death II
Quote:
Originally Posted by
lat9
... and the DIR_FS_CATALOG setting?
oh, sorry, I didn't see that one:
define('DIR_FS_CATALOG', '/var/www/vhosts/dans.com/httpdocs/zencart/');
Re: Admin Login - Loop Of Death II
Re: Admin Login - Loop Of Death II
I had a nice telephone conversation with lat9. She is very knowledgeable, and helpful. Not too long into our investigation, we realized that the permissions on my zencart/zcadmin/includes/configure.php file were 444. I updated them to 644 and that appears to have solved the problem. I can now access the admin area. Lat9 is going planning some additional testing when time permits, to see if she can duplicate the issue and confirm this for us.
Meanwhile - thank you!
Re: Admin Login - Loop Of Death II
Quote:
Originally Posted by
OrangeCrush
I had a nice telephone conversation with lat9. She is very knowledgeable, and helpful. Not too long into our investigation, we realized that the permissions on my zencart/zcadmin/includes/configure.php file were 444. I updated them to 644 and that appears to have solved the problem. I can now access the admin area. Lat9 is going planning some additional testing when time permits, to see if she can duplicate the issue and confirm this for us.
Meanwhile - thank you!
... and I did that additional testing.:smile:
The admin's /includes/configure.php permissions-setting was not, in and of itself, the root-cause of the issue. My best guess is that the originally-suggested changes to that file were not applied, due to its read-only status. I now believe that my attempt to get a define('NOTIFIER_TRACE', 'true'); injected into that file exposed the file's read-only permissions and subsequently applied those initial settings which resulted in a successful admin login.