yappa-ng Regular Documentation

UPGRADE

Upgrade Instructions for upgrading yappa-ng


Standard Procedure
Safe Mode Upgrade
Special Upgrade Instructions (release-specific)

ALL to 2.3.1
ALL to 2.3.0
2.2.0 or 2.2.1-r3 to 2.2.2-stable
2.2.0 to 2.2.1-r3
2.1.0stable to 2.2.0
2.0.x to 2.1.0
2.0.0beta to 2.0.1stable
previous < 2.0.0beta to 2.0.1stable
previous to 2.0.0beta

Standard Procedure:

Starting with release "2.2.2-stable" the Upgrade Process gets drastically simplyfied! :-)

After downloading the new release and reading the Upgrade instructions below take a view at the CHANGELOG to get an idea what is new and changed! :-)

Upgrading a system is always the perfect time to make a backup! Recommended are backups of all your hits.log, captions_xxx.txt and info_xxx.txt files. (Starting with release "2.2.2-stable" this is only a reminder to do a backup, it is not necessary for the Upgrade process anymore!)

If not stated otherwise for a particular release below you should copy all files from the new yappa-ng release into the appropriate directories, overwriting all existing files.
Of course you have to be careful with files you changed yourself. This implies themefiles, headers, footers, css, and all the others. If you changed a value in the "config_private.inc.php" note this change and overwrite this file with the new one nevertheless. Than change the value back again in the new file. (You do not need to be careful with all the news files, hits.logs, captionfiles or similar. They are not included in this form in the distribution anymore!. They are copied from the directory /install to the appropriate directories and many files just get created with the Setup Tool! If they already exist they will not be touched anymore!!)

The Upgrade Process in short:

Thats all there is to it! :-)

If you want to know IF there have been changes since date XYZ / release ZYX in a specific file and/or if you want to know WHAT the changes are in a specific file:
Take a look at the yappa-ng CVS repository on sourceforge.net

->Back to TOP


Safe Mode Upgrade:

Starting with release 2.3.0 there is a special "Safe Mode Upgrade Procedure" in place.
As everything in connection to Safe Mode its a little bit more to do, but it works! :-)

At the moment this Safe Mode Upgrade procedure with the 2 scripts is BETA!!

Thats the procedure for Safe Mode Upgrade. :-)


Special Upgrade Instructions (release-specific)

ALL to 2.3.1

In addition (!) to the Standard Procedure keep an eye on the following items:

enjoy! :-)

->Back to TOP


ALL to 2.3.0

In addition (!) to the Standard Procedure keep an eye on the following items:

enjoy! :-)

->Back to TOP


2.2.0 or 2.2.1-r3 to 2.2.2-stable

In addition (!) to the Standard Procedure keep an eye on the following items:

enjoy! :-)

->Back to TOP


2.2.0 to 2.2.1-r3

In addition (!) to the Standard Procedure keep an eye on the following items:

enjoy! :-)

->Back to TOP


2.1.0stable to 2.2.0

There have been many changes introduced into the 2.2.0 as you can see in the CHANGELOG. One of the most visual changes for the setup is the Setup Tool. You will use it from now on - it will make changes and upgrading much easier!

No Panic! :-) The Upgrade Process is not difficult - this description is longer than usual because I describe everything in great detail and for some parts I describe even more than one way to do it. :-)

The short description: Backup some critical files like your personal hits.log, overwrite everything with the new release, run the setup.php, restore the backuped critical files and that's it! :-)

The detailed description:

First step in the upgrade process is (as always) to make backups of the following files:

The images and all files below your Photos Main Directory will not get touched during upgrade. All other scriptfiles should be unchanged from you and can be obtained via download again! :-)

Now you have 2 options, depending on how frequented your site is! :)

In both cases copy your backuped files (hits.log, news_xxx.html, captions_xxx.txt, info_xxx.txt and config_album.inc.php) into the same places where you had them befor backup!

As always make sure your file/directory-permissions are correct again after upgrade ;-)
The file permission for the "setup.php" have to be the same as the "index.php" and the "show.php" (Important for "safe_mode" environments!)

Log into every Album as Album-Admin and check the new settings and save them. The "General Album Settings" have been split into 3 Menu items ("General Album Settings", "Thumbnail Display Settings" and "Image Display Settings").
All new parameters are set to default values that your user will not see any difference to the way yappa-ng was before if you have not the time to log into each Album and set the parameters new.
If you have no other Album-Admins and all Albums have the same setup (and same password!) configure one Album to your preferences and copy the "config_album.inc.php" into all other Albums!

There have been changes in the Themes Headers too!! If you changed the header to suit your needs please adapt the NEW header again (not try to adapt the old one!)!! I know its maybe more work for you - but you will not get the desired results if done the other way round. One of the changes is that you can now change / adapt the used icons within the themes to your liking - and for every theme differently. They are defined in the file "themes/themes_support.inc.php". Now its easy to take your own "keys icon" for example!

->Back to TOP


2.0.x to 2.1.0

There are MANY changes in this release - especially in the language-handling and new themes!

As always make a backup of your current setup. ;-)

Just replace _ALL_ files (*NOT* config.inc.php, news_xxx.html and your hits.log !!!) with the new ones. WARNING: be careful to _NOT_ overwrite the config_album.inc.php in your photo_root! ==> (You would have the default admin password for the photo "Home" directory again!!! <== Be sure to replace the config_private.inc.php! The language-handling has changed completely - and so has the header of the language files! Overwrite all language files!

There are 2 new config-parameters: "source_root" and "lang_intuitive" (descriptions of these parameters are in the config-file itself).

There are 3 new themes - take a look at the "themes_installed" - array in the config.inc.php!

Make sure to delete/rename the check_setup.php script after everything is running (and delete the check_setup.txt file if you used the check_setup.php script !!)

As always make sure your file/directory-permissions are correct again after upgrade ;-)

->Back to TOP


2.0.0beta to 2.0.1stable

I did not want to change much - it should be a bugfix-release only. But I validated yappa-ng to HTML 4.01 and CSS 2. Because ALL CSS-Tags have been incorrect (NO underscores "_" are allowed in CSS-tags!) there is really much change from 2.0.0beta to 2.0.1stable within the source code. "The Good News": no new files, no moves to other directories, no renamed files, no functional changes. :-)

Just replace all files (*NOT* config.inc.php, news_xxx.html and your hits.log !!!) with the new ones. There are 2 new config-parameters: If your setup is running smoothly just ignore them (or copy them into your old config.inc.php).

As always make sure your file/directory-permissions are correct again after upgrade ;-)

->Back to TOP


previous < 2.0.0beta to 2.0.1stable

Please follow the instructions and recommendations for the change as described in:
=> All previous to 2.0.0beta

->Back to TOP


previous to 2.0.0beta

If you do not follow the above procedure (e.g. don't delete the files first) there could be some freak side effects. Be warned!

->Back to TOP




Part of yappa-ng Documentation by Fritz 'wizard' Berger: >> yappa-ng Homepage <<