History of bitweaverUpgrade
Version 14 | Current version | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
bitweaverRelease Upgradeswhatever you do, always make a backup. whether you are about to do minor upgrades or large ones, please always backup your files and database first. we put a lot of effort into creating reliable installation / upgrade processes and making them as easy and quick as possible, however there are so many different setups and you might be using the one that causes probems ;)bitweaver Files and Directoriesthe following files and directories contain dynamically stored data, which you have to copy to your new installation:
1.0.* --> 1.0.3These are bugfix releases and have no database changes whatsoever.follow the following procedure:
Generic Database Upgrades / Conversionsbitweaver has a powerfull yet simple upgrader that is part of the InstallPackage. With a single click you can give your old site the power of bitweaver.Our architecture for upgrading, like all of bitweaver, is modular and powerful. Every BitweaverPackage maintains its own upgrade script. This architecture enables you to upgrade *any* CMS to *any* bitweaver version. Anyone up for a drupal upgrader? *nuke upgrader? TW1.9 upgrader? Currently it handles TikiWiki 1.8 and bitweaver ReleaseZero updates. It uses a lot of subselects so you will need a real database or at least MySQL 4.1. How does it work?install/upgrade.php does all the magic by looking at every BitweaverPackage's <package>/admin/upgrade_inc.php. This file has upgrade hashes of SQL *and* php for each package version and particular RDBMS as necessary. Below is a brief example. We suggest you look at liberty/admin/upgrade_inc.php if you are interested in seeing a complete example of how it works, or shoutbox/admin/upgrade_inc.php for a simpler example.
</package> | 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 dataThe 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:
Release Numbering ConventionBitweaver is released using X.Y.Z numerical notations:
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:
Sample Upgrade Process
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:
When using firebird, replace the first 3 lines:
If you are using the package phpBB, also do the following steps:
Post Upgrade Steps
Upgrades in version 2from 2.1.x to 2.5.0Our 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.0Despite 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.
from 2.0.x to 2.0.xThese are bugfix releases and have no database changes whatsoever.Upgrade from version 1 to version 2from 1.3 to 2.0Unpack 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:
Upgrades in version 1from 1.3 to 1.3.1Upgrade of bitweaver: As usual, no database changes have been made. Please upgrade in a similar fashion as outlined 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: phpBB install and upgrade instructionsfrom 1.2.1 to 1.3.xThe 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.1Upgrade 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 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: install and upgrade instructions at phpBB.com.from 1.0.4 to 1.2.0As 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.4These are bugfix releases and have no database changes whatsoever.Problems?If you encounter problems, please ask for support in the forum. |