Well, that was unexpected ...

Hi Folks,
I am resurrecting a system that has version 1.6, and I seek to upgrade to version 1.6.3. I immediately installed 1.6.3 and ran "setup", only to be warned that I should not skip versions. O.K., that sounds like good advice.

So I found versions 1.6.1 and 1.6.2. I installed them and I began to run setup in sequence.

Welcome to Zenphoto! This page will set up Zenphoto 1.6.1 on your web server.

So far, so good. Further down I see:

Upgrade from Zenphoto v1.6 [87 releases skipped]

Whoa! Now, what?

I'm not sure where I'm going to get the intervening 87 versions that I am apparently missing ... (-:

Do I really have to go from1.6 to 1.6.3 via 1.6.1 and 1.6.2?

Tags:

Comments

  • acrylian Administrator, Developer
    edited June 18

    It's a bug solved in the 1.6.4 support build soon to be released as 1.6.4. You can ignore that and just proceed.

  • cjm51213 Member

    Hi acrylian,

    Thanks. I was pretty sure I could ignore that, however my "real" question remains.

    Moving from 1.6 to 1.6.3 can be divided into differences in code and differences in database schema. If it were only code, then none of the intervening versions would matter, since the newer version code completely supersedes the older version code. It is a matter of database schema transformations. If there are no database schema transformations between 1.6 and 1.6.3, then I should be good to go simply upgrading from 1.6 to 1.6.3. Do I dare?

    Thanks for the help,

    Chris.

  • acrylian Administrator, Developer

    You should actually be able to upgrade directly to 1.6.3 respectively 1.6.4 (released today) as those are bugfix updates.

    Database scheme did not change. If we would in any case noted that on the release posts.

    The only larger change is regarding teh dateformats. Those due to bugfixing changed inbetween 1.6.x. Please see the release posts about that.

    There should not be any actual breaking changes. As always there are deprecated functions or plugins that throw notices in the debuglog. Those in the long run should be fixed/removed/updated but for the time being all should still work.

Sign In or Register to comment.