Resolving Azure CDN file issues in WordPress on Azure App Service using W3 Total Cache

Ilias el Matani

Introduction

Hosting WordPress on Azure App Service offers numerous advantages, but a common hiccup arises when using the W3 Total Cache plugin: certain plugin files aren't served via Azure's CDN. This can lead not only to suboptimal site performance but, more critically, to some files not being found at all. If you're grappling with this issue, this article will help.

The challenge with W3 Total Cache, plugins, and Azure

On Azure's WordPress PaaS, integrating plugins in WordPress is straightforward. However, ensuring their associated files are served through Azure's CDN is not. This oversight can result in missing files, causing broken links or functionalities on your site.

The solution: Custom File Hosting with W3 Total Cache

W3 Total Cache has a feature to remedy this: "Host Custom Files." Here's how to ensure all your plugin files are correctly served via Azure's CDN:

  1. Access the WordPress Admin Dashboard: Log in to your WordPress backend.
  2. Navigate to W3 Total Cache Settings: From the dashboard sidebar, select Performance > CDN.
  3. Go to the Advanced Tab: Within the CDN settings, click on the "Advanced" tab.
  4. Specify Custom File Paths: In the "Custom file list" section, add the following lines, replacing <nameOfPlugin> with the actual name of your plugin:

{wp_content_dir}/uploads/<nameOfPlugin>/css/* {plugins_dir}/<nameOfPlugin>/assets/*

  1. Activate Custom File Hosting: Return to the "General" tab in the CDN settings. Check the "Host custom files" box and click "Upload."
  2. Refresh the Caches: To apply your changes and ensure all files are found and served correctly, clear all caches in the W3 Total Cache settings.

By following these steps, you'll address the issue of missing files and ensure a smoother, more reliable user experience on your WordPress site hosted on Azure App Service.