This 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:
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.
This 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:
Disable the other hypervisor (see the last post in this series for how to disable the Hyper-V one) and restart the installation.
This 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:
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.
This 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:
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
This post is part of the series on Local by Flywheel.
Local by Flywheel can be downloaded from the homepage by clicking the Free Download button:
This post is part of the series on Local by Flywheel.
Local by Flywheel is a development tool for WordPress which provides a very easy way of creating a definable environment hosting a WordPress instance. As well as deploying an OS, it also deploys a web server, PHP and everything else required to develop or test a WordPress site, including WordPress itself.
Key features listed on the Local by Flywheel site are:
The extensive set of features can be read here.
The Community edition of Local by Flywheel is free, but there are additional versions coming soon which provide more functionality; details are here.
In the next few posts, I’m going to cover the download, installation and use of Local by Flywheel.
This post is part of the series on Local by Flywheel.
Before I start delving into Local by Flywheel itself, I thought it would be appropriate to do a post on who Flywheel themselves are. Flywheel are a managed WordPress hosting provider aimed at developers and agencies who create sites for others. The aim is to remove the hassle of hosting and allow you to focus on streamlining your processes and work for clients.
Full details on the services available from Flywheel are available from here.
The Flywheel site also has additional resources available in the form of ebooks aiming to help you create fast, secure sites on WordPress.
Local by Flywheel is one of the tools they’ve created to help develop new sites or features for sites. In the next post, I’ll take a more detailed look at what Local by Flywheel is and how it works.
I’ve recently started taking a look at ClassicPress, a fork of WordPress 4.9.8 (the one without the Gutenberg block editor). In order to test the migration from WordPress to ClassicPress, I needed a website which had PHP 7 (and due to my web host being crap; arvixe to those interested) I needed another way.
I was looking for a free webhost when I stumbled across Local by Flywheel which described itself as:
The #1 local WordPress development tool
This sounded like it would be very useful for the testing requirement that I had. In this series of posts, I’m going to be taking a look at the installation and use of Local by Flywheel. This post is the series index and will automatically update as each post goes live.
I’ve recently been taking a look at ClassicPress and one of the subjects that came up was that it might, for the plugin directory, use GutHub instead of SVN like WordPress.
I create an account and started looking into creating repositories for my plugins. Hot all of my plugins are on that site however, as not all have been released to the public. Some of them are only going to be usable to me (for example plugins drive both the GP Table Reference and my distilleries website) and you were limited on GitHub to a certain number of private repositories.
However, GitHub yesterday announced the following:
The second point isn’t relevant to me, but the first might be useful as it will allow me to store both my public and private plugins in the same place.
More details are available from the GitHub blog.
This post is part of a series on migrating to ClassicPress from WordPress.
As ClassicPress is based off WordPress 4.9.8, all current, non-Gutenberg, WordPress plugins and themes will be compatible with ClassicPress.
A growing number of plugins are stating that they are and will continue to be compatible with ClassicPress. There is a < forum post listing plugins confirmed as working with ClassicPress v1 on the ClassicPress forums; this is not to say that other plugins won’t work, but they haven’t been confirmed yet. This thread will be maintained for v2 of ClassicPress as well, which is when potentially breaking changes could be introduced.
If you think you might migrate to ClassicPress and want to confirm if the plugins you use will be supported with it, reach out to the authors of your favourite plugins and ask them to support ClassicPress. There is even a sample email message you can adapt and use.