By default, when a WordPress page loads, several PHP and SQL processes have to run on the server, and the browser has to fetch every image and file needed to render the page. That takes time.
The cache is a stored version of the result of all of those processes. The server basically “remembers” the finished page, in order to load it faster in the future. This way, instead of making the server load all that stuff every time your site has a visitor, those processes can be skipped entirely, making the page load much more quickly and saving your server unnecessary work.
Caching is a great and fully automatic way to speed up your site, but sometimes you might want to flush (i.e., erase) the cache if you’ve just made changes to your site, so that those new changes show up immediately. It should be noted, however, that this may also slow the site down temporarily as the server builds up a new cache.
Want to learn more about caching? Our free ebook will teach you everything you need to know!
Flywheel Development Mode is just a permanent version of the “Flush cache” feature; it disables all caching until you turn Development Mode back off again (and hides the “Flush cache” option in the meantime, since it would be redundant).
WarningWhile enabling Development Mode will allow you to see all file changes as soon as they’re made, it will also prevent your site from running as fast as possible, particularly on heavily trafficked sites or those that run lots of server processes, since it completely disables caching. So it’s highly inadvisable to leave Development Mode on for any longer than necessary.
WP_DEBUG is a WordPress feature that allows PHP warnings and errors that are normally hidden to be shown directly on your site for debugging purposes. It’s usually best to leave this off, especially on live sites, as it will likely ruin your site’s appearance by putting unwanted error messages on your pages.
WP_DEBUG can be helpful if your site is showing a white screen or a 500 error in Chrome, however, as it may display the fatal error or syntax error leading to the source of the issue.
Enabling Staging will create an exact duplicate of your live site on a Flywheel staging subdomain. You can make changes to the Staging site and, when you’re ready, push those changes back to the live site.
We keep copies of your site’s access logs, slow error logs, PHP error logs, and PHP server logs for seven days. You can have these log files emailed to you, for your live site or staging site (or both) with this button at any time.
This feature is primarily useful if you notice that your site seems slow or is experiencing errors, and you’d like to check the logs to find out what might be the cause. Generally in these cases, you’ll notice a plugin name showing up repeatedly in the files, or a fatal error or syntax error repeatedly coming from a specific file.
Reading the logs can be a bit difficult, though, so don’t hesitate to contact [email protected] and pass your error log files along if you spot any issues or need any assistance.
Flywheel automatically updates WordPress for you, but we wait to push out major version releases for an average of about two weeks, to allow any unknown bugs and issues to be discovered and patched first.
We usually roll out smaller security updates much more quickly, but in both of those cases, if there’s a version available and we haven’t run the update yet, you can do it yourself from here to get up-to-date right away!
And if you’d prefer to opt out of major version updates, be sure to check out this help guide.
This is where you can get access to your site’s SQL database directly. If you’re unsure about working with SQL databases, it’s probably a good idea to leave this alone; things can get messy in a database pretty quickly, even for seasoned developers, and you shouldn’t ever need to edit your database directly with WordPress.
But if you do know your way around a WordPress database, you can view and modify your database’s tables from here, run SQL commands, and import or export your database if need be. You can also update your database table prefix here, which you should never do on a live site, but which you may need to do if you’re manually migrating a database to Flywheel.
The most commonly asked questions, and a few we just think you should know.25 Articles
Questions that don't fit elsewhere, or those about Flywheel in general.56 Articles
Everything you need to know to get your first Flywheel site up and running.16 Articles
Details about how to manage DNS and point your domain names at Flywheel.11 Articles
Questions relating to payments, billing and managing your account on Flywheel.13 Articles
Learn everything there is to know about what Blueprints are, how to create them and how to make the best use of them.5 Articles
How to access your WordPress database to make changes and update content.3 Articles
Everything you need to know about our amazing, free local WordPress development software for Mac and PC.5 Articles
Everything you need to know about managing your team with our Organizations feature.8 Articles
Which plugins work best, which plugins work worst, and everything in between.7 Articles
Details about everything Flywheel does to makes your site so secure.13 Articles
Information on setting up and troubleshooting with SFTP connections and file transfers.4 Articles
All there is to know about our free, automatically installed and activated SSL certificates.9 Articles
How to get the most out of Staging, which allows you to duplicate a site, make changes, and then push those changes to the live site.7 Articles
Everything you need to know about our Whitelabel subscriptions for branding and reselling Flywheel.4 Articles
Here's a free ebook!