Local by Flywheel: Upload Own Database

Local By FlywheelThis post is part of the series on Local by Flywheel.

To migrate an existing site into Local by Flywheel, the first step is to restore your database. To make the backup, I used the mySQL Workbench, but many tools can be used to make and restore a backup of the database.

The first step is to backup your database from your current web host. Once you have this backup file, you need to restore it to the Local by Flywheel database.

The connection details for this database are available from the Local by Flywheel app on the Database tab:

azurecurve Database page

With these details you can use mySQL Workbench to connect and restore the database.

Local by Flywheel: Migrate Site to Local by Flywheel

Local By FlywheelThis post is part of the series on Local by Flywheel.

Over the last few posts, I’ve installed Local by Flywheel and used it to deploy a WordPress site for local development and testing. However, it is capable of so much more than this.

The WordPress site it creates can be migrated to ClassicPress using the migration plugin so that you can test that fork of WordPress 4.9.8.

You can also load an existing site into Local by Flywheel so that you can develop and test on a replica of your site. Over the next few posts, I am going to cover the steps I used to migrate my blog.

Local by Flywheel: Access Site From External Location

Local By FlywheelThis post is part of the series on Local by Flywheel.

You are able to give access to people externally in order that they can view your site in Local by Flywheel. You do this from the site overview page, by clicking the Enable button at the bottom of the screen:

Site Overview screen

Continue reading “Local by Flywheel: Access Site From External Location”

Local by Flywheel: Access Site

Local By FlywheelThis post is part of the series on Local by Flywheel.

Once you have a site created, it can be access by clicking the View Site button in the top-right corner:

Site Overview screen

Continue reading “Local by Flywheel: Access Site”

Is Newspack The Reason for Gutenberg in WordPress?

WordPressAutomattic/Wordpress.com have just announced Newspack by WordPress.com – A New Publishing Solution for News Organizations.

Newspack by WordPress.com is a new platform aimed at small and medium-sized news organisations, receiving a total of $2.4m funding, with half of that from from Google. Other contributors include The Lenfest Institute for Journalism, ConsenSys and The John S. and James L. Knight Foundation.

Google have a post on how a new publishing platform can help local news. I do wonder about the intentions behind this, as Google have a history of opposition from news organisations around the world who don’t like the aggregation which Google does.

Continue reading “Is Newspack The Reason for Gutenberg in WordPress?”

Local by Flywheel: Create New Site

Local By FlywheelThis post is part of the series on Local by Flywheel.

Once Local by Flywheel is installed, starting the application will show a page with a large green Create a new site button; click this button :

Create a new site stage

Continue reading “Local by Flywheel: Create New Site”

Local by Flywheel: Installation

Local By FlywheelThis post is part of the series on Local by Flywheel.

Now that we have Local by Flywheel downloaded, we need to install it (which is a very simple install). Launch the downloaded installer and click the Let’s Go! button to start the installation:

Click Let

The installation of the two components, VirtualBox and Host machine, may take a few minutes, but once completed you’ll be taken to the Create aew site step.

I’ll cover the creation of a site in the next post in this series.

Local by Flywheel: VT-X/AMD Error During Installation

Local By FlywheelThis post is part of the series on Local by Flywheel.

If when you install Local by Flywheel you receive the following error, it possibly means you have another hypervisor, such as Hyper-V, running:

Error message: Error with pre-create check: "This computer doesn

Disable the other hypervisor (see the last post in this series for how to disable the Hyper-V one) and restart the installation.

Migrating to ClassicPress: Using Migration Plugin With Unsupported WordPress Version

ClassicPressThis post is part of a series on migrating to ClassicPress from WordPress.

ClassicPress provide a migration plugin which you can use to migrate from WordPress to ClassicPress. The developers working on ClassicPress are also keeping the plugin updated for new releases of WordPress, but will lag a little behind as they need to wait for WordPress to release the new version before they can update the migration plugin.

I’ve been doing testing on ClassicPress and this has also included testing the plugin. Sometimes I’ve wanted to upgrade from an version not supported by the plugin.

The easiest way, in my experience, to use the plugin on a new version of WordPress before it is officially supported, is to amend the plugin to change the value to which the $wp_version_max parameter is being set:

admin-page.php showing line 318

Changing the value from 5.0.2 to 5.0.3 will allow the migration plugin to be run against the latest version of WordPress.

Instead of updating the plugin, you can also add the following line to your theme’s functions.php:

add_filter( 'classicpress_ignore_wp_version', '__return_true' );

I’ve tended to go with updating the plugin code, rather than adding the code to my functions file as I prefer to only have code in my theme that is for the benefit of the theme itself.

Local by Flywheel: Disable Other Hypervisors Before Installing Local by Flywheel

Local By FlywheelThis post is part of the series on Local by Flywheel.

Local by Flywheel works by installing VirtualBox; if you are running any other visrtualsiation software, you need to make sure that it, and the related hypervisor, is disabled.

In my case, I am using Hyper-V so will need to use bcdedit to stop the hypervisor via an elevated command prompt.

The command to use is:

Adminstrator: Command Prompt showing hypervisor successful disabled

bcdedit /set hypervisorlaunchtype off

Once the command has successfully completed, the machine will need to be rebooted; if a reboot is done performed, then the hypervisor will not be fully disabled and will cause problems.

Once you’ve finished installing and shutdown Local by Flywheel, you can restart the Hyper-V hypervisor using the following command (again a reboot will be required):

bcdedit /set hypervisorlaunchtype auto