外掛說明
- Manual Purge Control: Execute a global cache purge (/*) at the click of a button from the admin interface.
- Connection Validator: Quickly verify if your Azure credentials (Tenant ID, Client ID, etc.) are correctly configured.
- Detailed Activity Logs: A comprehensive history of all purge actions, showing who triggered the purge, the result, and the API response time.
- Security Focused: Built using WordPress best practices, including Settings API and secure AJAX handlers.
This plugin uses Azure’s REST API to send cache invalidation requests. It is lightweight and non-intrusive.
This plugin is not affiliated with Microsoft. “Azure” and “Azure Front Door” are trademarks of Microsoft Corporation.
For more details, see the official Azure Front Door Purge Content API documentation.
External Services
This plugin relies on the Azure Management API to perform cache purges.
- Service: Azure Management API (https://management.azure.com)
- Purpose: This service is used to send purge commands to your Azure Front Door profile.
- Data Sent: No user data is sent. The plugin only sends the content paths (URLs) to be purged and the authentication token provided by your Azure Tenant.
- Terms of Service: Azure Legal Information
Privacy
This plugin sends requests to the Azure API to purge cache. It does not transmit or store any personal user data. It is fully GDPR-compliant.
螢幕擷圖
The Activity Log page with the “Manually Purge Cache” button. 
The Settings page where Azure credentials are securely stored.
安裝方式
- Upload the plugin folder to the
/wp-content/plugins/directory. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- Go to Azure Purge menu and select Settings tab to enter your Azure credentials (Tenant ID, Client ID, Secret, etc.).
- Go to Azure Purge menu and select Activity tab to verify the connection.
常見問題集
-
Can I target specific URLs?
-
Currently, the plugin purges /* (all cached content) by default. Custom patterns will be supported in a future version.
-
Where are logs stored?
-
The plugin creates a custom database table (wp_azure_cache_logs) to store purge attempts and their results.
-
What permissions do I need in Azure?
-
The App Registration used must have at least the “CDN Endpoint Contributor” role on your Azure Front Door resource.
使用者評論
這個外掛目前沒有任何使用者評論。
參與者及開發者
以下人員參與了開源軟體〈Cache Purge for Azure Front Door〉的開發相關工作。
參與者
變更記錄
1.3
- Added filters to the logs table: date range (start and end), action, result contains, user, and duration range.
- Improved internationalization: Spanish translations for filter labels and buttons.
- Improved security in AJAX actions by enforcing nonce validation.
- Introduced a custom plugin capability (
access_azure_cache) and replaced all usage ofmanage_options. - Standardized activation and uninstall processes:
- Activation: creates logs table and assigns the plugin capability to Administrators.
- Uninstall: safely removes custom DB table and plugin options.
- Improved internationalization loading (textdomain) and added localized strings to JavaScript.
- Codebase hardening and structural cleanup, without modifying core purge logic.
1.2
- Unified menu structure: Single “Azure Purge” menu with “Activity” and “Settings” tabs.
- Added full internationalization (i18n) support.
- Added Spanish translations for all plugin text and JavaScript buttons.
- Added descriptive help text below all configuration inputs in Settings.
1.1
- Added Settings API for secure credential storage.
- Implemented Object Caching for log performance.
- Improved security with Nonces and SQL preparation.
1.0
- Initial release to the public repository.