Posts

I’ve just re-written the basic upgrade instructions as below. Can anyone see anything that could / should be changed?
This will of course be supplemented by any version-specific extra information at each new upgrade.

=============================================================

The standard way to upgrade kiwitrees to a new version is very simple. You should upgrade whenever a new version is made available. Even minor kiwitrees version updates usually contain a significant number of bug fixes as well as interface improvements and program enhancements. Registered users will be notified whenever an update is available.

1. As a precaution it is always a good idea to back up your kiwitrees database before proceeding with an upgrade. A useful tool to simplify this process is the kiwitrees add-on module “Simpl_MySqlDumper“.
2. Download the latest version of kiwitrees available from here.
3. While you are in the middle of uploading the new files a visitor to your site would encounter a mixture of new and old files. This could cause unpredictable behaviour or errors. To prevent this put your site into “maintenance mode”. Go to Administration > Site administration > Site configuration, tick ‘yes’ by Site maintenance and save. While you continue with the next step, leave your browser open at that page.
4. Unzip the .ZIP file on your desktop computer, and upload all the files to your web server, overwriting the existing files.
5. When everything has been copied (and do check as some FTP software can miss a few files) go back to your open browser tab (from 3. above) and click on Dashboard > Home. This is an important step in most upgrades and should be done before you disable the site maintenance setting. Most upgrades will include automatically deleting old files, and some will need database changes. These are triggered by visiting the dashboard home page. This will generally take less than one second.
6. Now you can check your site is still working correctly. Review the main pages and look for anything obviously wrong. Take special note of any changes or new additions described on this site and our news letter / email and see if any of those need configuring.
7. Once you are happy the upgrade is OK, return to Administration > Site administration > Site configuration, tick ‘no’ by Site maintenance and save. Your users can now access the site and enjoy the new features!

===========================================================
From http://kiwitrees.net/faqs/introduction/upgrade-kiwitrees/

Nigel
My personal kiwitrees site is www.our-families.info

Step 5 is new to me, and I’d like to know how mysqldumper will be implemented since I saw a warning in one of your earlier posts.

Regards
Paul

Penguins Are  Boss

https://bootesgowland.kiwitrees.net

Happy to be hosted by kiwitrees.net

pab wrote:

Step 5 is new to me, and I’d like to know how mysqldumper will be implemented since I saw a warning in one of your earlier posts.

Yes step 5 (and to a lesser extent step 4) is the main addition. It’s always been a good idea, but never stated before. Not doing it has in the past been the cause of things like broken menus, resulting in the rest of the page being broken. Until the dashboard home page trigger does some tidying up, there are settings left looking for files that no longer exist.

Previously I’ve suggested remedies like “delete xxxx file or module”, whereas really step 5 is a better answer, and if done at the described stage will avoid the errors ever being seen. All made easier by having a “maintenance mode” switch.

Re MySQLDumper – I will amend the warning. It should say “if also using PHP 7+ don’t use MSD for now“. But I soon hope to have that fixed, and possibly even the whole thing built into a core kiwitrees module.

Nigel
My personal kiwitrees site is www.our-families.info