這個外掛並未在最新的 3 個 WordPress 主要版本上進行測試。開發者可能不再對這個外掛進行維護或提供技術支援,並可能會與更新版本的 WordPress 產生使用上的相容性問題。

WP Shield

描述

This plugin will allow you to secure your development, staging and UAT environments
with an http authentication block that can be controlled in admin but also turned
off via a declared variable in your config file. It allows you to bring your Database
back to non-production environments without having to physically turn off the plugin each time.

Variable: define('WP_SHIELD_UN', '');

This simple line of code (recommended to add to a file ignored by your code management
software and required into your wp_config.php file) will override the enabled flag
if the plugin’s settings. Enable in production and add the above code. If that
require file doesn’t exist in your other environments, it will prompt users for the
set username and password.

安裝

  1. Download WP Shield from the WordPress plugin directory
  2. Activate the plugin through the ‘Plugins’ screen in WordPress
  3. Use the Settings->’WP Shield’ screen to configure the plugin
  4. Enter the username and password you want use for the shield
  5. Check the enabled checkbox and Submit
  6. Add the following code to your wp_config.php file:

    if(file_exists('shield-settings.php')) {
      include('shield-settings.php');
    }
    

For production environments:
7. Add the above snippet of code to the shield_settings.php file in the root of
your WordPress installation.

NOTE: Depending on your setup you may need to add one of the following to your .htaccess
or apache conf file:

.htaccess

RewriteRule .* index.php [QSA,E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

Apache conf

SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

常見問題

TBD

評價

There are no reviews for this plugin.

貢獻者及開發者

“WP Shield” 是一個開源的軟體。以下的人對這個外掛作出了貢獻。

貢獻者

將 WP Shield 外掛本地化為台灣繁體中文版。

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

修改日誌

1.0

  • Initial release of the Plugin

1.2

  • Add code to bypass shield on WP-CLI calls

1.3

  • Update readme for authorization setup

1.4

  • Fix for caching of credentials

1.5

  • Tested and confirmed for WordPress 6.1

1.6

  • Tested and confirmed for WordPress 6.4