History of bitweaverUpgrade


__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 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 ((NexusPackage|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 "((ReleaseOne|R1))" or "((ReleaseTwo|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 ((SchemaChangelog|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 [#Yourdata|above] to your bitweaver directory
# __review [http://www.bitweaver.org/wiki/InstallbitweaverDoc|Install Doc]__ if there are problems
# point your browser to http://your.bitweaver.site/

{code source=Bash title="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.

{code source=Bash title="When using postgresql, replace the first 3 lines:"}
$ pg_dump bitweaver > bitweaver.dump
$ createdb bitweaver-bak
$ psql bitweaver-bak < bitweaver.dump

{code source=Bash title="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

{code source=Bash title="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/

! Upgrades in version 2
!! 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: {code source=Text title="Resolve Conflicts"}http://your.bitweaver.site/install/install.php?step=4{/code}
# If you have been using ((TreasuryPackage|Treasury)), please visit the upgrade script: {code source=Text title="Treasury upgrade"}http://your.bitweaver.site/treasury/admin/database_to_libertymime.php{/code}

!! 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 ((ReleaseTwo|version 2))
__Further R1 to R2 reading:__
* [/wiki/bitweaver+R1+to+R2+Upgrade|bitweaver R1 to R2 Upgrade]
* [/wiki/phpBB+to+Boards+Upgrade|phpBB to Boards Upgrade]

! Upgrades in version 1
!! from 1.3 to 1.3.1
__Upgrade of bitweaver:__ As usual, no database changes have been made. Please upgrade in a similar fashion as outlined [#SampleUpgradeProcess|below]. Please make sure to backup your data. __Upgrade of phpBB:__ phpBB was upgraded to 2.0.20 and requires that you use the phpBB upgrade script. Please view the upgrade instructions that are supplied with phpBB on how to proceed: [http://www.phpbb.com/support/documents.php?mode=install|phpBB install and upgrade instructions]

!! from 1.2.1 to 1.3.x
The __search package__ has undergone a major re-vamp. It now allows you to re-index your entire site in the admin screen. Make sure to do so after you install 1.3. this will allow users to search all the content on your site reliably. Other than that, all you need to do is visit the installer to install the __newsletters package__ (if you want to use them on your site). Third party applications have all stayed the same and things like phpBB don't require any special treatment.

!! from 1.2.0 to 1.2.1
__Upgrade of bitweaver:__ Beginning with this version, the installer informs you of any permissions that might not be in use anymore and of permissions that have not been added to your database yet. Please visit this screen after upgrading the filebase of your bitweaver install. You can access the page by pointing your browser to the __Resolve Conflicts__ page in the installer (my.site.com/install/install.php?step=4). We have had several reports about __not being able to log in__ to the site after upgrading. If you are experiencing such a problem, please visit [/phpbb/viewtopic.php?t=1311|this forum thread] and post your problems there, should they persist. __Upgrade of phpBB:__ phpBB was upgraded to 2.0.19 and requires that you use the phpBB upgrade script. Please view the upgrade instructions that are supplied with phpBB on how to proceed: [http://www.phpbb.com/support/documents.php?mode=install|install and upgrade instructions at phpBB.com].

!! from 1.0.4 to 1.2.0
As with all stable branches, such as ((ReleaseOne)), no alterations of your database are required. We have added a few new permissions. Most of these will probably not interfere with the running of your site, however we recommend that you have a look through ((SchemaChangelog)) for further details and instructions on how to add them to your database.

!! from 1.0.x to 1.0.4
These are bugfix releases and have no database changes whatsoever.

! Problems?
If you encounter problems, please [/forums/|ask for support in the forum].
Page History
22 May 2010 (12:21 UTC)
Current • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
Lester Caine81.138.11.13663
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
Lester Caine81.138.11.13658
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source