Upgrading WebsiteBaker

This section provides information for upgrading an existing WebsiteBaker 2.7 installation.

Backup

Step 1: Backup pages and templates

Before upgrading to WebsiteBaker 2.8.1, 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 WebsiteBaker database (e.g. via the WebsiteBaker-Backup module, phpMyAdmin, or MySQLDumper).

Note: It is not recommended to upgrade without a backup in place. The backup allows to restore your previous WebsiteBaker installation in the case something goes wrong during the upgrade process.

 

Step 2: Backup User settings of form and news Modul

- Please make a backup of the frontend.css in modules/news and modules/form dir.
- As the settings of the news modul are changed to use language variables now, the news modul settings in the database gets overwritten by the upgrade script. Only if you have made changes in these settings you also should make a backup (f.e. storing settings in a text file) of your news modul settings.

Prerequisites

Note: Please do the following steps before you upload the WB 2.8.1 files
Step 1: Editarea replaces Codepress

As codepress gets replaced with editarea the whole codepress code isn't needed anymore. So please delete the whole include/codepress folder.

Step 2: Admin-Tool "Reload" is moved to another place

The place for reloading addons is moved from admin-tools to add-ons page. So the admin-tool Reload isn't needed anymore. Please delete the whole folder /modules/reload.

Step 3: Changes in FCKEditor

We changed in all folders and subfolders of FCKEditor the files which prevents directory spoofing from index.html to index.php. All index.html files (50) should be deleted. The easiest way is to delete the whole /modules/fckeditor/fckeditor folder with all subfolders. 

Note: Please don't delete ../fckeditor/wb_config/wb_fckeditorarea.css and ../fckeditor/wb_config/wb_fckstyles.xml if you have made personally adaptions in these files.
Step 4: Admin Interface

One of the major changes of WebsiteBaker 2.8 is introducing skinable admin interfaces.This means the whole admin dir is rewritten. So best is to delete the whole /admin folder.

Step 5: New Captchas

We introduce new better to read captchas. To get rid of the old ones please delete:
- bg_01a.png from /include/captcha/backgrounds
- bg_02a.png from /include/captcha/backgrounds
- bg_03a.png from /include/captcha/backgrounds
- bg_04a.png from /include/captcha/backgrounds 

Upgrading from 2.8.0 to 2.8.1

  • Backup WebsiteBaker as described above, otherwise changed files will get lost
  • Download the upgrade files and unzip it to your local machine
  • Upload the files to your server (be sure that all files are overwritten with the new ones)
  • Remove from your server the include/jquery/plugins folder (isn't needed anymore)
  • Log-in to your backend
  • Choose "Addons" then "Modules" then "Advanced" and execute the upgrade.php from news modul
  • Choose "Addons" then "Advanced" and reload the modules, templates and languages

Upgrading from 2.7 to 2.8.1

Unpack the WebsiteBaker 2.8.1 installation package on your local computer. Please make sure you have followed all the steps listed in the section Prerequisites above (including backups).

The following Files/folders should always be deleted from the package:

  • config.php
  • /install

The following files from the package should be renamed if you have made personally adaptions on these files:

  • modules/news/frontend.css to frontend_org.css
  • modules/form/frontend.css to frontend_org.css
  • modules/fckeditor/wb_config/wb_fckeditorarea.css to wb_fckeditorarea_org.css
  • modules/fckeditor/wb_config/wb_fckstyles.xml to wb_fckstyles_org.xml
Note: If your are using one of the four default WebsiteBaker templates, you should remove this also from the package, otherwise your changes get's overwritten.

 

Copy now all files via FTP to your server (simply overwrite the files of your existing WebsiteBaker installation).

Then 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.

Wrap up

 

Step 1: Delete the upgrade-script.php

Delete the upgrade-script.php via FTP from your server.

Step 2: Check News and Form Modul

- Check if news and form modul looks well formed in the frontend. If not incoporate the new classes from frontend_org.css to your frontend.css and style them to your needs.
- Also habe a look at the settings of the news modul. Incorporate your changes from your backup-file to the settings of the news modul.

Step 3: Modify your modules

If any of your modules uses images from admin/images dir (mostly move_up and move_down arrows or edit_files icons) you have to change the path to use now the images from your backend theme. Basically you have to change:

<?php echo ADMIN_URL; ?>/images/...

to

<?php echo THEME_URL; ?>/images/...

btw.

ADMIN_URL.'/images/...

to

THEME_URL.'/images/..

 

Once you have adapted all your modules the /admin/images folder can be deleted.

 

Upgrading from 2.6.x to 2.8.1

A direct update from 2.6.x to 2.8.1 is not possible. Please download first the necessary older versions from the archive (2.6.x > 2.6.7 > 2.7 > 2.8.1) and make an update like written there. After that update as described here.

 

 « Previous  Next »