Demo Backup

admin



This extension lets you create an automated backup schedule,import demo content or even create a demo content archive for migration purposes.

Data protection for physical, virtual, and SaaS environments; either on-premise or in the cloud. Before creating a Content Backup for Demo Install use a plugin to remove post revisions. The next step is to let your users view and select which demo content to install. This page is created in the WordPress admin under Tools Demo Content Install if the theme has at least one demo content available. Watch this interactive product demo to learn more about how NEW Veeam Backup for Microsoft Azure delivers enterprise-ready Azure backup and recovery to cost-effectively and securely protect your cloud data.

  • Demo Content Install
    • Create Demos
  • Troubleshooting

Migration is a term representing moving a WordPress website from one location (e.g. http://localhost/site) to another (e.g. http://site.com).

This is achieved by:

  1. Making a full backup copy of the old site(http://localhost/site).
  2. Moving it in the wp-content/uploads/fw-backup directory on the new site(http://site.com).

After opening the Backup page a new archive will be displayed in the Backup Archive list.

The demo content install might be very useful for your clients.After they install the theme, they won’t need to configure and create content from scratchbut instead they can install the demo content you’ve created.Their site will look exactly like your theme demo page, and they can just start to modify and adapt the existing content.

In order to create a demo content archive, just create a Content Backup.

Tip

Before creating a Content Backup for Demo Install use a plugin to remove post revisions.

The next step is to let your users view and select which demo content to install.This page is created in the WordPress admin under Tools > Demo Content Installif the theme has at least one demo content available.The demo content archives can be placed in theme or can be downloaded from a remote server.

  1. Create Content Backup

  2. Extract the zip in {theme}/demo-content/{demo-name}/

  3. Create {theme}/demo-content/{demo-name}/manifest.php with the following contents:

  4. Go to Tools > Demo Content Install menu in the WordPress admin. The demo(s) should be listed on that page.

  1. Create Content Backup

  2. Upload the zip on your server (in any directory you want, for e.g. your-site.com/demo/)

  3. Upload this download script,let’s say in the same directory your-site.com/demo/

  4. In the same directory with the download script, create a config.phpfile and add your demos in the following format:

  5. Register the demo(s) in your theme. Add in {theme}/inc/hooks.php:

  6. Go to Tools > Demo Content Install menu in the WordPress admin. The demo(s) should be listed on that page.

  • Filter to exclude wp options on database export

  • Filter to exclude wp options on database restore

    Note

    The current options (if exist) will be wiped out. To keep the current options, use the following filter.

Demon Backwards

  • Filter to preserve current wp options values on database restore

  • Filter to register a custom directory that contains theme demos (for e.g. a plugin bundled with theme)

Demo Backup

If you have trouble with install demo content or backup content please make sure you have these recommended php values:

Make sure you have enough disk space. The full backup backups the entire wp-content folder and sometimes users have there a lot of “trash” like backups from other plugins, cache … Some times other plugins backups are really huge 2-4GB. You have to make sure that you do not have the same problem.

The admin notice “Unyson: Your website is hosted using the LiteSpeed web server. Please consult this article if you have problems backing up.” means that your web hosting company uses the LiteSpeed webserver.LiteSpeed appears to have problems with all WordPress scheduled tasks that last more than a very short time – including all backup plugins. Adding this in an early position in the .htaccess file in your WordPress root folder may fix the problem:

Adding the above line does not mean that the problem is definitely fixed, you will only know that via testing. If the above does not help, then you can try to add a line to your wp-config.php(WordPress’s alternative scheduling system):

Demon Background

If that does not help you, then you’ll need the help of your web hosting company to see why WordPress’s scheduler isn’t working on their setup, or is terminating it prematurely. Or failing that, you’ll need a different web hosting company. This problem is a generic one affecting all backup plugins on WordPress that run via the scheduler (which is all of them, as far as we know).