开发者 | swte |
---|---|
更新时间 | 2015年3月16日 13:59 |
捐献地址: | 去捐款 |
PHP版本: | 3.5 及以上 |
WordPress版本: | 4.1.1 |
版权: | GPLv2 or later |
版权网址: | 版权信息 |
Swift Security can be fine-tuned in its smallest details, however, to use the plugin you don't need any technical skills, you only have to activate the plugin. That's all. If there is a need for any custom settings, the plugin will help you with several messages (e.g. if the cache directory cannot be opened).
Yes, because Swift Security does not rename your directories and files, it only masks them, so if you deactivate the module or the plugin, everything will return to its original state.
No problem. Rename the wp-content/plugins/SwiftSecurityLite directory for example to SwiftSecurity_x or delete the directory and delete the lines between ######BEGIN SwiftSecurity###### and ######END SwiftSecurity###### in the .htaccess file. Following this, you can log in with your old admin URL (http://yoursite.com/wp-login.php or http://yoursite.com/wp-admin) Next, install the plugin again and be careful to remember the login URL :)
Swift Security is compatible with most security plugins, however, conflicts may occur when both plugins rename the admin URL or two firewalls are activated at once. Because the Swift Security plugin offers an integrated solution, there is no need (and it is not recommended) to be used with other firewalls or “hide WordPress'' plugins.
Of course, but don't forget to clear the cache after activation or modifications.
Officially the WPEngine and Godaddy hostings are supported, however, the plugin should work with all hosting providers. If you notice any issues with any managed hostings, please contact us at support@swte.ch Please take it into account that these providers may use other cache solutions as well, and only WPEngine is handled automatically by Swift Security.
If you're logged in, these pages are not hidden. Log out, close all browser windows and try again or simply try it in private (or incognito) mode or from a different device.
Yes and no. You won't have any SEO problems if you're not going to change the content URLs (post, tag, category, author, feed), but if you decide to change them, it's probably not going to hurt you, however, these will be removed from Google's index eventually. But if you have a broken link pointing to a 404 then yes, you are leaking PR. With a new WordPress site you will not have any problems when you change these URLs.
Yes. Try it yourself at wpthemedetector.co.uk.