Upgrade problem in admin only

[oavs]

I have upgraded from 1.5.5f to 1.5.6a


I had my admin in a different folder named 'dif-admin', so I copied my existing admin 'dif-admin' to 'dif-admin_old'
All installed v156 a correctly.
I then copied the new 'zcadmin' contents to 'dif-admin' after installations.

I can see public site fine.
When I tried to login to admin I get "ERROR 0071: There appears to be a problem with the database. Maintenance is required."
My database prefixs are correct.

After renaming new install to 'dif-admin_new' then I switch back to my 'dif-admin_old' by after renaming 'dif-admin_old' to 'dif-admin' my admin works. Admin also shows that it is version v1.5.6a

Can anyone help to solve this please?

[Mauari]

try to upload the files in parts.
From 1.56ADMIN to 1.55ADMIN
That way you can isolate the problem

Upload a block of files. and try to access 1.56ADMIN.
If you can access, upload another file block. And try to access.

If you can not enter after a file block you will know that the problem is in this block ...

Repeat the operation from the beginning, restore the 1.56ADMIN from the 1.55ADMIN.

Start again, the block that has given problem upload it one by one and try to enter 1.56ADMIN ... so you know which file generates the problem.

[Mauari]

There appears to be a problem with the database. Maintenance is required."

Be sure configure.php is correct and uploaded in 1.56ADMIN

[mc12345678]

There is a *lot* of detail missing here.

If file copying was all that was performed which is what the OP implies, then that is the primary issue.

So a few things. The admin folder in a default ZC install can have any name that is acceptable to the file system. There can even be multiple admin folders (highly recommend only having an admin folder that is related to the current software version).

The reporting of the software version 1.5.6a is based on the contents of the catalog side version information. Because the catalog side is presumably up-to-date with all files associated with ZC 1.5.6a, that is why the admin is seeing 1.5.6a.

But, because the database has not been upgraded (no discussion of the database upgrade being performed), the admin side is reporting that an upgrade is needed by identifying that maintenance is required or there really is a problem with the database.

Really before accessing the admin, the zc_install database upgrade should have been performed. (again, if it was, such detail was omitted.) now, because there are multiple admin folders, when attempting to do the zc_install upgrade, you will be asked which admin folder is intended to be the one to use for ZC 1.5.6a. Be sure to select the correct one when performing this, though afterwards it's name can be changed to whatever is desired/needed.

As to the actions described to have been done: copied existing admin to another location and then overwrote the files in the existing admin with files from the new admin, there are going to be files that straggle and are either not needed, not used, or may cause problems by being present.

Note that the process to perform the upgrade is best identified here: http://www.zen-cart.com/entry.php?3-...d-of-upgrading

Would recommend that in moving forwards on this issue to provide in detail the operations taken to get to where this site is without writing a reference to the original post so that it can be understood what was done to get to this point.

[Mauari]

There is a *lot* of detail missing here...

Hello,
I have updated my website to the latest version the 1.56a

I did it from 1.55f, with a very modified TEMPLATE.
Even with several plugins and alterations in the database.

As I did...
I made a fresh installation. standard
and upload only Produtos and Clients to the 1.56a DB.

Then I made the modifications, installed plugins and alterations in the Responsible template.
But firts I renamed it to RESPONSIBLE_ISCARLY_TEMPLATE
these folders where responsible_Clasic just put the "new_name_template", This way in new actualization 1.56b will not overwrite my modifactios will only merge

I have a lot os plugins and alterations and uploaded one by one..
Extrafield, QuickView, AdminNotes, RecoverCart, LayoutGrid ... and my own modifications, comparing one file with another ..

It took me a long time
but I know that I do not have "leftover" or obsolete file.

The updates of Zen-cart is the worst thing that this great script has.
I have tried over 10 shopping Cart scripts and the ZC is the best without a doubt, but it is not for lazy people. (No offense)

using since over 10 years

[mc12345678]

Hello,
I have updated my website to the latest version the 1.56a

I did it from 1.55f, with a very modified TEMPLATE.
Even with several plugins and alterations in the database.

As I did...
I made a fresh installation. standard
and upload only Produtos and Clients to the 1.56a DB.

Then I made the modifications, installed plugins and alterations in the Responsible template.
But firts I renamed it to RESPONSIBLE_ISCARLY_TEMPLATE
these folders where responsible_Clasic just put the "new_name_template", This way in new actualization 1.56b will not overwrite my modifactios will only merge

I have a lot os plugins and alterations and uploaded one by one..
Extrafield, QuickView, AdminNotes, RecoverCart, LayoutGrid ... and my own modifications, comparing one file with another ..

It took me a long time
but I know that I do not have "leftover" or obsolete file.

The updates of Zen-cart is the worst thing that this great script has.
I have tried over 10 shopping Cart scripts and the ZC is the best without a doubt, but it is not for lazy people. (No offense)

using since over 10 years

Mauri, by my statement of missing a lot of information I was referring to oavs as the original poster (OP). I commend you on the ability to sustain a Zen Cart store for so long, though would say that the process described to do the upgrade is incomplete as well. Primarily the entire database (possibly after exporting and removing the admin log) should be transferred in the upgrade process instead of just the products and customers tables. The upgrade script supports this process quite well. Yes, upgrading requires more than just press a button and walk away, though improvements in the structure continue to be made in addition to modifying the code to comply with new PHP requirements.

Anyways, my post was directed more to oavs in solving the problem that seemed to be described. The results of what was done appear to be provided, but what was done to get there was not so clearly stated.