We’re extremely excited about Fortress and what it brings to the table. Below is all the information about getting started, and we’ll follow up with you directly over email to get you access to the plugin.
Access & Info
Here’s a breakdown of everything related to Fortress.
Right now, Fortress is in beta and, like anything in beta, should be used carefully. This includes thoroughly testing on a staging environment before using on any live site, and use on any live site is at your own risk.
That all said, the faster we can get real-world data in, the faster the Fortress team can get the plugin into production, and if you have the time to test, please do. You can also use this time to get acquainted with the plugin and how it works and begin building your own customizations if that’s something you want to do. You can find our documentation here:
- Fortress Security Part 1: How Fortress Secures WordPress
- Fortress Security Part 2: Quick Start Configuration Guide
For any questions, beta feedback, or general support, you can post in our community forum here in the new Fortress section.
On our end, we are working on our integration with the plugin, and this includes automating a 7G WAF exclusion, a page caching exclusion, and setting a default define path for the user configuration file in the user-configs.php file. Installing the plugin will be available from the UI, and it will be done as a must-use plugin, and we’re making it compatible with our staging and cloning functionality where there’s a change in the URL.
Essentially, all the stuff you need to do manually right now will be automated as much as practically possible.
The process for accessing Fortress will all be streamlined in the near future. Right now, we’ll provide direct access via email ASAP.
Once you have the plugin, you simply install it like any other plugin for testing, but for any production sites in the future it should be added as a must-use plugin.