Stuck in maintenance mode !!!

[split63]

I had to change the name of my DB. So I followed these steps:

• Put site in maintenance mode
• exported the DB. (via PHPmyAdmin)
• imported DB into a newly created DB with the new name.
• Updated the two config files,
• went to admin (it was working), set maintenance to false. The Admin screen showed it was no longer in maintenance

But the public shopping cart still showed maintenance mode !!!

checked the two config files, they were correct.

Panic! Updated the config files back to the old DB, it all works.

What did I do wrong?

[g2ktcf]

I had to change the name of my DB. So I followed these steps:

• Put site in maintenance mode
• exported the DB. (via PHPmyAdmin)
• imported DB into a newly created DB with the new name.
• Updated the two config files,
• went to admin (it was working), set maintenance to false. The Admin screen showed it was no longer in maintenance

But the public shopping cart still showed maintenance mode !!!

checked the two config files, they were correct.

Panic! Updated the config files back to the old DB, it all works.

What did I do wrong?

For what it is worth, see previous post on same subject. https://www.zen-cart.com/showthread....!!-Please-help!!

[mc12345678]

In modifying includes/configure.php, was its permissions changed to support write capability just before trying to save it? It is possible that some caching may have been involved with one or more of these operations.

[split63]

When I altered the config files, I commented out the active DB details and copied then modified the details for the new DB, then hit save.
When it would not come off maintenance mode, I just did the reverse, uncommented the original DB details and commented out the new, then hit save. If the 2nd action worked, the 1st must have been okay too in terms of permissions.

I could just try changing the name of the DB directly, but I don't like the idea of touching the golden source....

Where is the state of maintenance mode stored in the DB?

[carlwhat]

SELECT *
FROM `configuration`
WHERE `configuration_key` = 'DOWN_FOR_MAINTENANCE'

turn off maintenance mode:

update  `configuration`
set configuration_value = false
WHERE `configuration_key` = 'DOWN_FOR_MAINTENANCE'

best.

[split63]

turn off maintenance mode:

update  `configuration`
set configuration_value = false
WHERE `configuration_key` = 'DOWN_FOR_MAINTENANCE'

What is so confusing is that when maintenance mode was set to false inside Admin, the Admin screen showed it was no longer in maintenance mode. So something in the DB changed.....yet, the shopping cart itself showed it was still in maintenance mode. How can this be? I tried different browsers, all showed the cart was in maintenance mode. I kept refreshing....no change.

[split63]

I searched the DBs for the term "DOWN_FOR_MAINTENANCE". I find 10 entries in table zen_configuration, shown below.
Comparing the two databases, they are identical with regard to these 10 entries

There must be more to it.

[carlwhat]

I searched the DBs for the term "DOWN_FOR_MAINTENANCE". I find 10 entries in table zen_configuration, shown below.
Comparing the two databases, they are identical with regard to these 10 entries

There must be more to it.

none of those other entries mean anything if the first entry is false.

you have a db config problem. specifically it sounds like your storefront is using a different (ie your original db). now you can say that's untrue and perhaps you are correct... more likely not.

i am not sure of exact load order; but something is setting your storefront db to your old db that is in maintenance mode. perhaps you have a includes/local/configure.php that gets loaded first or something else, as you seem to be insistent that includes/configure.php is correct.

we know that maintenance mode works and works correctly. is it possible it is a caching problem? no idea.... but i think not, especially as you have tried different browsers which would provide new sessions.

so i'm sticking with an issue with your config files.

best.