elmuerte
07-23-2009, 05:57 PM
vbDrupal 6.13.0 alpha release notes
Disclaimer
!WARNING! This is under development software, a lot of features do not work, and some things might be severely broken. DO NOT use this on a production site unless you are absolutely certain you know what you are doing.
Thank you for trying out this indevelopment software. Please help us test this software. Without proper testing bug might be missed before a stable release is made. So we value your effort to test this software.
In order to get the best testing performance it is best to test the software on a backup copy of your original site. That why you'll be sure the features you use are also operational. But we also appreciate testing on mockup sites. Please see the installation notes below on how to get this working.
vbDrupal 6 will require (at least) vBulletin 3.8. vBulletin 3.7 will not be supported during the development phase. This does not mean that it will not work at all with vBulletin 3.7, it just means that we are not going to validate proper operation. We will accept patches for vBulletin 3.7 compatibility.
State of the software
As mentioned earlier not everything in this release is operational. This build is based on Drupal 6.13, which should mean that all features of Drupal 6.13 should work. ONLY the following vbDrupal specific features are operational:
- the core vbDrupal functionality
- comment_vb module
- vbbirthdays module
All other modules and themes have not been updated yet. So you will need to disable those modules and themes before installing this alpha. The following modules and themes DO NOT WORK:
- vbforumblocks
- vblist
- vbnode
- vbpm
- vbpolls
- defaultangy
Instructions
Currently there is no 'install from scratch' functionality. The installer is scheduled for a later milestone. This means that you will have to start from a vbDrupal 5 installation.
So, either get a copy of your vbDrupal 5 site, or first install a clean copy of vbDrupal 5. Make sure you're using the latest version of vbDrupal 5. Also make sure you updated vBulletin to at least 3.8.0.
Before you continue, be sure you have a backup of the database. This will make it easier to reset your test environment.
Override the current setup with the files from this development release and execute the update script ( http://example.org/drupal/update.php ). Follow the onscreen instructions to update to vbDrupal 6.
During the update you might get the following error:
user warning: Multiple primary key defined query: ALTER TABLE drupal_permission ADD pid int NOT NULL AUTO_INCREMENT PRIMARY KEY in [...]/drupal/modules/system/system.install on line 1449.
In that case you should also see the following notice:
Fixed failed permission table alteration from system update #6016
This means that the reported error has been fixed. If you do not get that notice, then please report it. Also report any other errors you might receive.
Bug reporting
If you encounter any issues, please report them. The prefered method of reporting it via our bug tracker at:
http://sourceforge.net/apps/trac/vbdrupal/
But you can also fall back to the vbDrupal 6 forum at:
http://www.vbdrupal.org/forum/forumdisplay.php?f=26
Thank you for testing the software,
vbDrupal team.
Disclaimer
!WARNING! This is under development software, a lot of features do not work, and some things might be severely broken. DO NOT use this on a production site unless you are absolutely certain you know what you are doing.
Thank you for trying out this indevelopment software. Please help us test this software. Without proper testing bug might be missed before a stable release is made. So we value your effort to test this software.
In order to get the best testing performance it is best to test the software on a backup copy of your original site. That why you'll be sure the features you use are also operational. But we also appreciate testing on mockup sites. Please see the installation notes below on how to get this working.
vbDrupal 6 will require (at least) vBulletin 3.8. vBulletin 3.7 will not be supported during the development phase. This does not mean that it will not work at all with vBulletin 3.7, it just means that we are not going to validate proper operation. We will accept patches for vBulletin 3.7 compatibility.
State of the software
As mentioned earlier not everything in this release is operational. This build is based on Drupal 6.13, which should mean that all features of Drupal 6.13 should work. ONLY the following vbDrupal specific features are operational:
- the core vbDrupal functionality
- comment_vb module
- vbbirthdays module
All other modules and themes have not been updated yet. So you will need to disable those modules and themes before installing this alpha. The following modules and themes DO NOT WORK:
- vbforumblocks
- vblist
- vbnode
- vbpm
- vbpolls
- defaultangy
Instructions
Currently there is no 'install from scratch' functionality. The installer is scheduled for a later milestone. This means that you will have to start from a vbDrupal 5 installation.
So, either get a copy of your vbDrupal 5 site, or first install a clean copy of vbDrupal 5. Make sure you're using the latest version of vbDrupal 5. Also make sure you updated vBulletin to at least 3.8.0.
Before you continue, be sure you have a backup of the database. This will make it easier to reset your test environment.
Override the current setup with the files from this development release and execute the update script ( http://example.org/drupal/update.php ). Follow the onscreen instructions to update to vbDrupal 6.
During the update you might get the following error:
user warning: Multiple primary key defined query: ALTER TABLE drupal_permission ADD pid int NOT NULL AUTO_INCREMENT PRIMARY KEY in [...]/drupal/modules/system/system.install on line 1449.
In that case you should also see the following notice:
Fixed failed permission table alteration from system update #6016
This means that the reported error has been fixed. If you do not get that notice, then please report it. Also report any other errors you might receive.
Bug reporting
If you encounter any issues, please report them. The prefered method of reporting it via our bug tracker at:
http://sourceforge.net/apps/trac/vbdrupal/
But you can also fall back to the vbDrupal 6 forum at:
http://www.vbdrupal.org/forum/forumdisplay.php?f=26
Thank you for testing the software,
vbDrupal team.