bitweaverUpgrade
How to Upgrade bitweaver
Always make a backup first. A lot of effort was put into creating reliable installation and upgrade processes and making them as easy and quick as possible. However, there are many different server setups, some of which might cause a problem.
Your data
The following files and directories resume service contain dynamically stored data - in other words, data that you or your users created. Copy these files or directories to your new installation:- /kernel/config_inc.php
- Contains database access information.
- /storage/
- Contains files that have been uploaded by you or your users.
- /temp/nexus/modules/
- Contains Nexus modules created by you or your users.
- /themes/styles/your_style/
- Your custom style (if present).
- 3rd party
- Applications like phpBB, Gallery2, FCKeditor and so forth might have their own configuration files, e.g., /phpbb/config.php.
Release Numbering Convention
Bitweaver is released using X.Y.Z numerical notations:| Rev | Rev | Rev | Desription | Upgrade Instructions |
|---|---|---|---|---|
| X | 0 | 0 | This is the major release, and indicates significant architectural changes in the database schema and code structure. This is the number used for "R1" or "R2", etc. | You will need to run the GUI installer and follow the upgrade path. Be sure to run a test upgrade on a backup database first in case there are errors in the upgrade. |
| X | Y | 0 | This is the minor release which indicates no architectural or database changes have been made, however new packages or significant features have been added. | Simply replace your install with the last source (being mindful of retaining your storage/ directory and kernel/config_ing.php - we highly recommend cvs checkouts to make upgrading a breeze. |
| X | Y | Z | This is a bug fix release that simply fixes issues with existing code. No architectural or database changes have been made. | Same as minor release. See above. |
Database changes:
Please consult the schema changelog page for any changes that have been made to any package. We never make table alterations to stable branches. However, you might find that some permissions have been added to the database.General procedure to upgrade:
- make a backup of your files and database
- upload/unpack the downloaded archive to your bitweaver directory
- copy the files and directories mentioned above to your bitweaver directory
- review Install Doc if there are problems
- point your browser to http://your.bitweaver.site/
Sample Upgrade Process
# dump the database
$ mysqldump bitweaver > bitweaver.dump
# create new database
$ mysqladmin create bitweaver-bak
# make sure dump worked as planned. this will also allow you to switch back to
# original database if needed by modifying your kernel/config_inc.php.
$ mysql bitweaver-bak < bitweaver.dump
# move to your apache document root
$ cd /var/www/html/
# rename your old bitweaver directory
$ mv bitweaver/ bitweaver-old/
# copy accross your custom theme if you have one
# please note that your custom templates might have to be updated
# usually it's easiest to diff the custom templates with the originals and update appropriately
$ cp -a bitweaver-old/themes/styles/mytheme bitweaver/themes/
# extract the new version of bitweaver
$ tar -zxvf ~/downloads/bitweaver_1.2.0.tar.gz
# copy storage/
$ cp -ru --reply=yes bitweaver-old/storage/* bitweaver/storage/
# copy temp/
$ cp -ru --reply=yes bitweaver-old/temp/* bitweaver/temp/
# make sure apache has permissions to access them
$ chmod -R 777 bitweaver/storage/ bitweaver/temp/
# copy your config_inc.php
$ cp bitweaver-old/kernel/config_inc.php bitweaver/kernel/config_inc.php
If all that worked, you should be able to visit your site. Please look at specific upgrade instructions below.
When using postgresql, replace the first 3 lines:
$ pg_dump bitweaver > bitweaver.dump
$ createdb bitweaver-bak
$ psql bitweaver-bak < bitweaver.dump
When using firebird, replace the first 3 lines:
'Backup and restore database via your favourite tool'
There should be a scheduled backup happening anyway on a well configured firebird installation
If you are using the package phpBB, also do the following steps:
# copy your old PHPBB configuration
$ cp --reply=yes bitweaver-old/phpbb/config.php bitweaver/phpbb/config.php
# PHPBB will not run when these directories exist
$ rm -rf bitweaver/phpbb/install/ bitweaver/phpbb/contrib/
Post Upgrade Steps
- First visit your site at http://my.bitweaver.site/. In some cases we force you to visit the installer.
- If you don't have to visit the installer, please go to Administration >> Kernel >> Packages. Here you will see various tabs that will inform you if you should visit the installer and what needs to be done to fix your bitweaver install.
- Finally, please visit Administration >> Kernel >> System Cache and clear out your entire cache to get rid of old files.
Upgrades in version 2
from 2.1.x to 2.5.0
Our installer has undergone a major overhaul. Now it is possible to do database upgrades independently of release versions and now packages can register requirements. The installer should guide you through the upgrade. Please follow the instructions in the installer carefully.from 2.0.x to 2.1.0
Despite our best efforts, we were unable to avoid a couple of small database changes. We've tried to keep things as simple as possible for you to upgrade.- Follow the steps above by creating a backup of the database and moving the old files out of the way and placing the new files in their stead.
- Copy across your storage folder, configuration files, and custom theme.
- As soon as you try to browse bitweaver now, you will be forced to visit the installer.
- Visit the installer on the Resolve Conflicts page. On this page you will see a couple of things that should be done. These can all be dealt with by clicking on the buttons:
Resolve Conflicts
http://your.bitweaver.site/install/install.php?step=4
- If you have been using Treasury, please visit the upgrade script:
Treasury upgrade
http://your.bitweaver.site/treasury/admin/database_to_libertymime.php
from 2.0.x to 2.0.x
These are bugfix releases and have no database changes whatsoever.Upgrade from version 1 to version 2
from 1.3 to 2.0
Unpack bitweaver version 2 to some directory and copy your old directories /storage/ and /temp/ into there. Point your browser to yourbitweaver.org/install/install.php and chose the option Upgrade from R1. The installer will now ask for database details. Then, the installer converts your database and your installed packages. After this is done, you can intall new packages from the new version. If something went not so perfect, the installer will point you to it later. This could be missing tables (installer will then try to create them) or unassigned permissions (installer lets you fix them). Some tricks and tipps:- be sure to have the file /storage/bit_setup_inc.php in place
- compare your old /kernel/config_inc.php with the new one just created
- don't copy files from /temp/templates_c/, rather delete the contents of this folder (or click admin -> system cache -> clear all)
- if you're using your own custom style, it might hold incompatible modules or templates that cause errors. please don't copy these just yet.
- upgrading from version 1.1 or 1.2 to version 2.0 does not require you to install 1.3 first, any version 1 can be upgraded directly by the installer of version 2