This section provides answers to questions frequently asked in the WebsiteBaker forum. This prevents the forum from being spamed by the same question and helps the moderator to focus on the real problems.
There were and are many different spellings. The association decided the correct spelling is "WebsiteBaker" - and nothing else. It is one word without any space, and "W" and "B" are written in capital letters.
So please do not use other spellings except "WebsiteBaker" - we know it's not easy, but give it a try.
The navigation menu is styled by external CSS. If you're not a CSS pro, you might want to review a few resources dedicated to CSS found elsewhere on the net. Google is your friend in a big way here. Two great CSS resources to help you understand before you start asking questions in the forums:
Try to realize your navigation style in straight HTML first. Once you know how to do it, you can automate it by the WB menu function show_menu2(). See the documentation available to learn more about the CSS classes and parameters supported.
On the Add-ons Side, you can find the replacement function show_menu2(), which adds a lot of features not implemented in the WB menu function. If you want to learn more, visit the webpage of the developer for further details. With show_menu2() and CSS you can realise any navigation menu style you want.
Note:
Search the WWW to learn more about the styling of lists with CSS. The WebsiteBaker forum is no support forum for CSS / HTML related problems!
First try the "Forgotten your details?" function - it will send your password to the email address you defined in WB admin.
If that is not possible:
All passwords are stored as encrypted MD5 hash in the WB database. If you have access to your MySQL database (e.g. via phpMyAdmin), you can replace any password in the field: password of the database table users by executing the following SQL statement.
UPDATE prefix_users SET password = md5('mypass') WHERE username = "admin"
Adjust prefix_ to the table prefix you have choosen during installation, mypass to the new password you want to set and admin to the username where you want to apply the new password.
Then clear the browser cache and log into the WB backend using the username of the user and the password you have defined. Please choose a more secure password than mypass.
WebsiteBaker is released under the GNU General Public License, more commonly known as the GPL. For further information about the GPL visit the link below: http://www.gnu.org/copyleft/gpl.html.
This license give you a maximum of freedom. However, you have to stick to the following rules:
For more information visit the License page .
The error message 'Cannot modify header information - headers already sent.' occurs if a WB routine tries to send a header after text is displayed in the browser. If this error occurs during installation process, try to clean your browser cache and session variables, then try again.
If you have accesss to the php.ini file, you may want to enable PHP buffering ( output_buffering ) to prevent such kind of errors.
This depends on the version used.
For very old versions (2.6.x or earlier) it is generally recommended not to upgrade them anymore.
You can read here how to upgrade from WebsiteBaker 2.7 to WebsiteBaker 2.8.3 and what you need to be aware of.
WebsiteBaker 2.8.3 UPGRADE Instructions THX ruebenwurzel
Step 1 depends on the WB version you want to upgrade from
Step 2 - Step 9 are the same, no matter which version you upgrade from.
*********************************************
Upgrade from WB 2.8.2SP2 to WB 2.8.3
Upgrade from WB 2.8.2SP1 to WB 2.8.3
Upgrade from WB 2.8.2 to WB 2.8.3
*********************************************
Step 1 - Preparing the system
- Create backup of all personally changed files in the module or template directory ( .css, .js, .htt ...)
- Create backup of droplets
- Delete the directory "/templates/argos_theme".
- Delete the directory "/templates/wb_theme".
*********************************************
Upgrade from WB 2.8.1 to WB 2.8.3
Upgrade from WB 2.8.0 to WB 2.8.3
*********************************************
Step 1 - Preparing the system
- Create backup of all personally changed files in the module or template directory ( .css, .js, .htt ...)
- Create backup of droplets
- Delete the file "/admin/preferences/details.php".
- Delete the file "/admin/preferences/email.php".
- Delete the file "/admin/preferences/password.php".
- Delete the directory "/modules/backup".
- Delete the directory "/modules/droplets/js".
- Delete the directory "/templates/argos_theme".
- Delete the directory "/templates/classic_theme".
- Delete the directory "/templates/wb_theme".
*********************************************
Upgrade from WB 2.7 to WB 2.8.3
*********************************************
Step 1 - Preparing the system
- Create backup of all personally changed files in the module or template directory ( .css, .js, .htt ...)
- Create backup of droplets
- Delete the file "/account/stylesheet.css".
- Delete the "/admin" directory
- Delete the directory "/include/captcha".
- Delete the directory "/include/codepress".
- Delete the directory "/modules/code".
- Delete the directory "/modules/fckeditor".
- Delete the directory "/modules/reload".
- Delete the directory "/modules/show_menu2".
- Delete the directory "/modules/wrapper".
- Delete the directory "/templates/allcss".
- Delete the directory "/templates/round".
- Delete the directory "/templates/simple".
*********************************************
Upgrade from WB 2.8.2SP2 to WB 2.8.3
Upgrade from WB 2.8.2SP1 to WB 2.8.3
Upgrade from WB 2.8.2 to WB 2.8.3
Upgrade from WB 2.8.1 to WB 2.8.3
Upgrade from WB 2.8.0 to WB 2.8.3
Upgrade from WB 2.7 to WB 2.8.3
*********************************************
Step 2 - Download WebsiteBaker
- Download "WebsiteBaker 2.8.3" from http://wiki.WebsiteBaker.org/doku.php/downloads (see WebsiteBaker 2.8.3 Feb 2012 )
Unpacking the Package on the Local Machine
Step 3 - Prepare the package
- Delete the file "config.php.new"
- Delete the "/install" directory
- replace the favicon with your own if necessary
Step 4 - Update the files on the server
- Transfer all files of the customized package from step 3 to the server.
- After uploading, check that all new files are on the server.
Step 5 - Update the database
- if you upgrade from WB 2.8.x:
Log in as superadmin in the backend, the upgrade script starts automatically
- if the upgrade script does not start automatically, or you upgrade from WB 2.7:
Call the script in your browser via www.yourdomainname. com/upgrade-script.php manually to
- Follow the instructions
Step 6 - Clean-up work
-Delete the file upgrade-script.php
Step 7 - Update table with extensions (just to be sure)
- Go to "Enhancements" - "Enhanced"
- Load "Modules", "Design Templates" and "Languages" new
Step 8 - Activate the changed/new droplets
- Go to "Extensions" - "Modules" - "Advanced"
- execute the "install.php" of the "Droplets" module
Step 9 - Update the WYSIWYG-sections to the new URL-Handling
- Go to "Extensions" - "Modules" - "Advanced"
- execute the "upgrade.php" of the "WYSIWYG" module
Upgrade to WebsiteBaker 2.12.2 from all 2.8.3 versions
Important: For an upgrade to WB 2.12.2 one of the WB 2.8.3 versions is required. It is not possible to upgrade from an older WB version to WB 2.12.1. Please first upgrade to WB 2.8.3 according to the instructions above.
Important: Only the SuperAdmin (User-ID == 1) can start the upgrade script.
- Check that the web space has the required minimum requirements:
- download WB-2.12.2 from our Wiki - Downloads
- Make sure that the desired database is accessible and that the required authorizations are available.
- Upload the files of the package via FTP, the option "Overwrite All" must be activated in the FTP program.
- Change PHP version to PHP 5.6 or higher (if not already done)
- The Upgrade-Script starts automatically after logging into the WB-Backend or can be started via the link on the homepage of the backend. You can also start the Upgrade-Script at any time via the Info Window (i-Button in the Top-Menubar).
- It is not necessary to delete the install folder. This is protected by the core and is required for the upgrade script.
- It is not necessary to run the file upgrade-script.php in the WB main directory. The file is also protected by the core and can no longer be called from outside.
- It is recommended to have a look into the WB error.log from time to time. Any existing content should be copied to a local text file for documentation and repair purposes. The content can then be deleted using the "Delete error.log" button.
Translated with www.DeepL.com/Translator
If the backend language changes without any user interaction, one should check the database entries for inconsistent settings. If you have access to pypMyAdmin, login to your database and execute the following SQL statements. The database statements asumes that English is your default language.
UPDATE xxx_settings SET value = 'EN' WHERE name = 'default_language' UPDATE xxx_pages SET language = 'EN' UPDATE xxx_users SET language = 'EN'
Attention: Change the DB table prefix: xxx_ according your database setting.
This error occurs, when you install a template which requires the snippet show_menu2(), which is not installed on your system. Simply download show_menu2() from the Add-ons page and install it via the WB-Backend: Add-Ons -> Modules -> Install module. Thats it.
This is possible. However, Javascript and PHP statements will only be parsed when invoked from a pages or sections of type: Code. It is not possible to put working PHP or Javascript statements to a WYSIWYG page or section (you can add it, but the statements will not be executed!!!).
You have to use the echo or print commands of PHP, when using Javascript and HTML statements within a page or section of type code (page type code is made for parsing PHP). You need to escape all special characters by yourself. Best way of mixing HTML code with Javascript statements is to use the PHP Heredoc Syntax (consult the PHP manual for details). Copy the following code into a page/section of type code and view the results.
$a = '12';
$mixed_output = <<< EOT
<h2>HTML statements</h2>
<p>possibility to evaluate PHP variables a:= $a</p>
<script type="text/javascript" language="javascript">
alert('Javascript code: Hello world');
</script>
EOT;
echo $mixed_output;