• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Upgrade instructions for Chevreto from 3.X up are missing

ghulst

Chevereto Member
I wanted to update the Chevereto v3.18.3 installation on my server to the newest Chevereto v3.20.3 release. So, I went to the update page and found the instructions. Or, so I thought.

The page warns it is outdated, but it would be beneficial to at least have a message there for Chevreto 3.X updates. The way it was set up now, I first spent a lof of time looking for:
Save the DB connection info from includes/config.php
Where the information is really in app/settings.php

The next instruction left me searching a lot more (including this site and Google) because it says:
Save the CHV_CRYPT_SALT that you have in includes/definitions.php
And in 3.X the includes folder does not even exist and a lot of browsing never shows me a "CHV_CRYPT_SALT" anywhere.

In the end, I just downloaded the Chevreto release and uploaded it through FTP. That worked very well. the settings.php file was retained. I then visited the site where it showed me that the database needed to be updated. I clicked the button and everything worked out.
Perhaps it is a good idea to put something along those lines on the upgrade page. 😉
 
That's not a bug, that's you following the instructions to upgrade from V2 😂

(that's upgrade, not updating)

 
like @Rodolfo said, if you look at upgrade page it clearly says following: Update from V2.1 - V2.6 and Update from 2.0.X and older.

So idk how you got this to be instruction for upgrading from v3.18.3 to v3.20.3
 
Back
Top