Possible to ONLY upgrade database when going from 1.5.5a to 1.5.5b?

[amart79196]

I know this has been asked in another thread, but this is a bit more specific here with this set of circumstances.

I had 1.5.5a running and just downloaded 1.5.5b. I did exactly what the thread said that if you are going from 1.5.5a to 1.5.5b that it is simply copying over the files effected in the update and add your customizations if any. I luckily didn't have any customizations that I needed to change in the files and just copied over the new files and got rid of the old ones.

When inside of the Admin panel I clicked on "VERSION" and I noticed it says that I'm on 1.5.5 in big bold letters and below it says that I went from 1.5.4 to 1.5.5a (Which is what I did a while back when 1.5.5a first came out and I installed it).

I'm wondering if I need to have the database updated now to 1.5.5b. If so, How does this get done?

One very important fact. Out of all of the files that were listed on the page that shows the updated files that need to be changed, it listed last the zc_install folder. Since I do not have this folder in my live store I didn't find it necessary to put it onto the server.

Did I do something wrong here?? The instructions said to copy over the files...it never said to run the web gui zc_install setup program.

Any guidance would be greatly appreciated...many thanks in advance!

[mc12345678]

If not mistaken the section of text from which that came addresses updating the files only and not ZC as a whole.

The installation/upgrade process involves both the files and the database. The interface for that is the zc_install folder.

While this upgrade may be handled differently, it is considered to always be prudent to upload the zc_install folder, access it and if offered the ability to upgrade the database only (at this point having updated the files to match the ZC version to be installed) to step through those actions.

[DrByte]

The upgrade from v155a to v155b had no database changes. There's no need to run zc_install to go from 155a to 155b.

(Yes, your Admin "version" screen may say the db is still at v155a, but that's fine.)