Upgrading 2.12.1 to 2.12.2

[richwingerter]

I have 2.12.1 installed and it is giving me an error message when a new user tries to register. In an effort to fix this problem, I want to upgrade to 2.12.2.

I checked a bunch of the documentation:

• https://forum.WebsiteBaker.org/index.php/topic,31528.0.html
• https://help.WebsiteBaker.org/en/userguide/installation/prior-to-installation.php
• DOCU/README_EN.md

This leaves me very uncertain the correct procedure to do the upgrade.

I have 2.12.1 installed in a directory, call it /home/admin/WB. That directory has subdirectories, like account, admin, etc.

I unzipped WebsiteBaker-2_12_2.zip and created WebsiteBaker-2_12_2.tar.gz from the directory structure, on my Windows system. I uploaded it to the production (Linux) server and tested. It gives me a wb directory with all the 2.12.2 files in their proper directory structure.

Should I delete the existing WB files in /home/admin/WB and then extract the files from this tar.gz file into it, so that /home/admin/WB has the new, 2.12.2 files, and then run upgrade_script.php (which would be the one coming from the 2.12.2 distribution)? If not, what's the best way to upgrade?

Thank you.

[dbs]

Hi, is the word "delete" somewhere in the upgrade instructions?
Why you want delete something?
You want delete also your images in media and also your template inclusive all changes?

Extract your tar.gz in home/admin/WB.
Login as user with id 1.
click the upgrade link.

You can help us to understand what is unclear in the upgrade instructions.

[richwingerter]

If I extract it in /home/admin/WB, it will very likely overwrite the existing files. That would surely delete some of them, and possibly leave others. Is that what's intended? It seems like that would create an enormous mess, with files for the new version intermixed with files from the old one. Is that how others are upgrading?

[jacobi22]

Is that how others are upgrading?

Yes, it is!

Files that are no longer needed will automatically delete by the upgrade script later

[dbs]

You know now the upgrade instructions and you ask "Is that how others are upgrading?".
New WB versions have not many new files, but many changed files. The upgrade script delete some of old not needed files.

Yes, you can delete self all WB files before uploading (except config.php, your images in media, your template).
Don't forget step 1: make a backup of database and files.

[hgs]

This method has already worked 100 times successfully.

Short version:
- make a backup of all files and the database (!important)

 +Recommanded way: (fast & safe)
 - download WB ZIP package & unzip.php.zip
 - rename unzip.php.zip to unzip.php
 - upload WB ZIP package & unzip.php to your WB root folder (where the config.php is located)
 - run unzip.php in your browser (https://yourdomain.com/unzip.php) (please replace yourdomain.com with your own domain)
 - login in your backend as Super-Admin (admin with id 1) and run upgrade-script via upgrade link or via wb-info panel (i-button)

The unzip.php and the WB ZIP delete themselves after the successful execution of the unzip.php.

[richwingerter]

I unpacked the tar file of the 2.12.2 distribution into the directory where I had 2.12.1. Then, I logged into the back end, as Luisehahne suggested, as admin (user ID 1). This gave me a button to press to start the upgrade.

I selected options (in this case, show upgrade details and confirm back up options), and clicked the "Start upgrade script" button. It finished without any evident error. I got an error when I went to the front end, but that's because I've added some functions and they were not represented in the new files. I added those and the front end came up.

I was able to add a new user without getting an error, which was the reason I originally went through this upgrade. I have a number of other issues, but I'll put them in their own messages.

[dbs]

What do you mean with this post?
Thanks for upgrade help?
You're welcome.

[richwingerter]

I mean a little more than that, dbs. I mean not just thank you for the help but also that upgrading was successful at fixing the original problem, which was that adding a new user resulted in an error message. Now it doesn't.