b2evolution b2evolution

  • Sign in
  • Sign up
  • About
  • Downloads
  • Hosting
  • Docs
  • Support
  • Sign in
  • Sign up
  • Manuals Home
  • Latest Updates
 
  1. b2evolution CMS User Manual
  2. Installation / Upgrade
  3. Upgrade
  4. Manual / Standard Upgrade Procedure

Manual / Standard Upgrade Procedure

Upgrading b2evolution is a simple process:

  1. Backup
  2. Upload the files for the new version
  3. Run the installer in order to upgrade your database

The installer is able to upgrade any older version of b2evo, no matter how old it is.

We will detail this simple process below with probably more information than you need. The details are there to reassure the less tech savvy users among us…

Rest assured: you will NOT lose the contents of your collections when you upgrade. See Faq Install Upgrade for additional information.

Also note that all the folders mentioned below have blogs as root folder in early standard releases, but it may vary depending on your own setup.

Before you begin, please note that some network features of b2evolution require you to agree to our simple Terms of Service.

Warning: Note that there will be some minor downtime to your site by following these instructions.


Detailed Upgrade Procedure

Step 1: Backup your b2evolution folder

Remember to take special care of the files you may have modified, including /conf, /skins, /plugins, your /media directory and possibly stubfiles, hacks or custom templates…

If you need help with this, please see: Make a Backup.

Step 2: Backup your b2evolution database

The most critical data (posts, comments, users) is stored in a MySQL database. Do not forget to back it up in addition to your files.

If you need help with this, please see: Make a Backup.

Optional: validate your existing DB

You can do this by restoring the /install folder of your current (old) b2evolution version (be very careful to use the correct version and NOT to mix different versions).

Then run the install script and select "upgrade" even though there should be nothing to upgrade. b2evolution will detect that the DB is up to date but will still validate it to see if everything is as expected. If not, it will propose to do some repairs.

Do not continue upgrading until this step terminates without detecting any error.

Step 3: Delete existing (old) files

This is not strictly necessary but we recommend you delete all your existing b2evolution files from your site before uploading the new ones. This will ensure you don’t keep unnecessary files on your site after upgrading. It’s also better for security.

Do NOT delete the following files and folders (that you will find in the directory where your b2evolution is installed):

  • conf/_basic_config.php (it contains the configuration to access your database; if you deleted it, you would have to reconfigure)
  • media/ (it contains your uploaded files/images; if you delete it, you would have to restore from backup)
  • skins/*your_custom_skin_folders* if you have custom skins. (if you delete them, you would have to restore from backup later)

Note: It is best to delete all hacks & plugins for now and re-add them progressively. 3rd party plugins may not work with the new version.

Step 4: Upload all the new files

We cannot stress this enough: ALL FILES!

If you haven’t done step 3, it means you must OVERWRITE all the old files that have a new file equivalent. And that means you can’t reuse your old customized files. You must also overwrite all the files in the /conf folder (the DB connection information will not be overwritten, the file /conf/_basic_config.php is not part of the distribution).

Step 5: Run the installation/upgrade script

It is located in /install/index.php. It is the same script for installation and upgrade. It will offer you to upgrade if it detects an existing b2evolution database.

Then, simply follow the on screen instructions.

If you deleted your /conf/_basic_config.php file, you will be asked to reconfigure the database access information.

Step 6: Check the installation

If it doesn’t work, check if there are specific upgrade instructions for your specific version.

Step 7: Delete the /install subfolder

Deleting the /install is important for best security and will prevent others from overwriting your settings.

Step 8: Restore previous customizations

If you had made some hacks/customizations to your b2evolution installation, we recommend you get yourself a diff/merge tool like Beyond Compare or WinMerge. This will allow you to easily compare your old (backed-up) files with the new files (even whole directories at once) and report changes accordingly.

In the specific instructions section above, you may find useful information for upgrading from and to your specific versions.

You can also check the Forums for experience from other users.

Step 9: Check up on the tricky stuff

Now would be a good time to go through the After Installation / Upgrade page and check that everything has been taken care of.

Congratulations! You are now done with upgrading your b2evolution application!


Common upgrade mistakes, problems & solutions

  • If you get big fat ugly PHP errors that you don’t see on the demo site, something went wrong with your FTP upload. Check for 0 byte long files on your server. Upload again.
  • If your CSS looks ugly or your javascript menus & buttons don’t work: *Refresh! Shift Refresh! Control Refresh!* Restart your browser. Clear your cache. (Normally a simple refresh is enough but it depends a lot of browser, browser plugins, OS and ISP)
  • If the back-office works fine but the public interface to your collections has problems, please try switching back to one of the standard skins included in the distribution in order to make sure whether or not the problem is due to a third party/custom skin.
  • If you still have problems, please try disabling all your plugins (you won’t lose your settings) in order to assess whether or not the problem might be caused by an incompatible plugin.

See also

  • Upgrading Evoskins
Tags: 6.11.1
Created by fplanque • Last edit by fplanque on 2020-07-28 23:27 • •

No feedback yet

On this page

  • Detailed Upgrade Procedure
  • Step 1: Backup your b2evolution folder
  • Step 2: Backup your b2evolution database
  • Optional: validate your existing DB
  • Step 3: Delete existing (old) files
  • Step 4: Upload all the new files
  • Step 5: Run the installation/upgrade script
  • Step 6: Check the installation
  • Step 7: Delete the /install subfolder
  • Step 8: Restore previous customizations
  • Step 9: Check up on the tricky stuff
  • Common upgrade mistakes, problems & solutions
  • See also

Search the Manual

Content Hierarchy

  • b2evolution CMS User Manual
  • User's Guide
  • Installation / Upgrade
    • New Installation
    • Upgrade
      • Manual Upgrade Procedure
      • Auto-Upgrade Procedure
      • After Installation / Upgrade
      • Automated Install / Upgrade
      • Upgrading Evoskins
      • Unexpected SQL Error during upgrade
      • Upgrading your database to UTF-8
      • Instructions for specific versions
    • Configuration files
    • Advanced Setup
    • Migrating from Another System
    • Moving your b2evolution Site
    • FAQ & Troubleshooting (Installation / Upgrade)
    • Assumed User Skills
  • Front-office Reference
  • Back-office Reference
  • Developer Reference
  • Operations Reference
  • Advanced Topics
  • Glossary
  • Archives
Website builder

This online manual is powered by b2evolution CMS – A complete engine for your website.

About b2evolution

  • What is it?
  • Features
  • Getting Started
  • Screenshots
  • Online demo
  • Testimonials
  • Design philosophy
  • Free & open source
  • Terms of service

Downloads

  • Latest releases
  • Skins
  • Plugins
  • Language packs

About us

  • About us
  • Contact

Webhosting Guide

  • Web hosting blog
  • Best web hosting
  • Cheap web hosting
  • Green web hosting
  • Hosting with SSH
  • VPS hosting
  • Dedicated servers
  • Reseller hosting
  • Int'l: UK / France

Docs & Support

  • Online manual
  • Forums
  • Hire a pro !

Other

  • Adsense
  • Press room
  • Privacy policy

Stay in touch

  • GitHub
  • Twitter
  • Facebook
  • LinkedIn
  • News blog
  • RSS feed
  • Atom feed

Founded & Maintained by François Planque