This page lists all changes in WB 2.7 with respect to WB 2.6.7.
This section provides information for upgrading an existing WB 2.6.7 installation. If you are using a Website Baker installation prior to 2.6.7, please follow the steps described on the WB Help site.
Before upgrading to Website Baker 2.7, it is highly recommended to create a backup of the /pages and /templates folder (including all sub-folders and files) by the use of FTP. Apart from that you should create a backup of the entire Website Baker database (e.g. via the WB-Backup module, phpMyAdmin, or MySQLDumper).
Note: It is not recommended to upgrade without a backup in place. The backup allows to restore your previous Website Baker installation in the case something goes wrong during the upgrade process.
Step 1: Language files
Please check if you can overwrite the files in the folder /languages with your FTP tool. If you can overwrite the files, please proceed with Step 2.
If you can not overwrite the files, you need to update the language files manually via the WB Backend. Simply install all languages files (or the ones you are interested in). The source are the languages files of the WB 2.7 installation packet. Remove the /languages folder from the WB 2.7 installation packet before uploading the package to the server.
Step 2: FCKEditor
FCKEditor is the new default WYSIWYG editor. If you have already installed FCKEditor, please uninstall your version via the WB backend (or delete the folder /modules/fckeditor via FTP in case you installed FCK via FTP). Remember to backup the files located in /fckeditor/wb_config before deinstalling the editor.
Step 3: show_menu2
The additional menu function show_menu2 is is part of the Website Baker 2.7 installation package. If you are already using show_menu2, please uninstall your version via the WB backend (or delete the folder /modules/show_menu2 via FTP in case you installed showmenu2 via FTP).
Step 4: Administration tools
If you are using administration tools listed on the Add-ons site, please upgrade your version with the version from the Add-ons site. You do not need to deinstall the module, just install the latest version over the existing ones.
Step 5: Form and News module
WB 2.7 uses the advanced modules per default. We have removed the CSS styles from the database and moved it to the frontend.css files. Please copy the CSS styles from the module settings to a textfile and store this file on your local computer. This way you can copy the styles back after the upgrade.
Unpack the WB 2.7 installation package on your local computer. Please make sure you have followed all the steps listed in the section Prerequisites above (including backups).
Copy all installation files except folder /install and the file config.php via FTP to your server (simply overwrite the files of your existing WB installation).
Note: If your are using one of the four default Website Baker templates, any modifications made will be overwritten. Please backup the entire /templates folder before copying the WB 2.7 installation files via FTP on your server.
Then log-out from Website Baker and delete the browser cache and cookies. Once you cleared cache and cookies, call the upgrade script from your browser via: http://www.domain.com/upgrade-script.php and follow the steps mentioned in the script.
Step 1: Delete the upgrade-script.php
Delete the upgrade-script.php via FTP from your server.
Step 2: Modify your templates
In the future, modules will provide a frontend.css and backend.css file to store the CSS definitions of the modules. To automatically add those files into the head section of your template, please add the following code to the index.php of your template.
<?php // allows to include optional module files (frontend.css, frontend.js) into the head
if(function_exists('register_frontend_modfiles')) {
register_frontend_modfiles('css');
register_frontend_modfiles('js');
} ?>
Step 3: Adjust styles of news and form modules
Click on the "edit frontend.css" button which can be found in the module settings of the advanced news/form modul. Open the local textfile with the CSS styles of the previous modules and paste them into the text area.
Note: PHP needs read/write access to edit the module files frontend.css und backend.css from the WB backend (group: php, wwrun-user ...). Detailed informationen about file permissions can be found on the WB Help site.
Step 4: Adjust FCKEditor
Update the FCK configuration settings in folder /modules/fckeditor/wb_config with your backup files (if exists).
Apart from the "critical" bugs listed, we fixed a lot of smaller issues with WB 2.6.7 not listed explicitely above.