WordPress.org

1. robnalexpress
   Member
   Posted 10 months ago #

   Version 0.9.2.3 In preparing for a migration to a new server, we found that W3TC was creating thousands of redundant directories, mostly for the folders "static" and "buyers" which are for the 2 self-hosted CDNs. This is a sampling:

   ./public_html/wp-content/uploads/home/*****/public_html/wp-content
   ./public_html/wp-content/plugins/w3-total-cache/wp-content
   ./public_html/buyers/wp-content ./public_html/buyers/wp-content/wp-content
   ./public_html/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyer/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/static/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/static/buyers/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/static/static/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/static/wp-content
   ./public_html/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/buyers/static/buyers/wp-content

   You get the idea. Tried deleting the redundant files, but they would be recreated in minutes. Had to disable W3TC

2. robnalexpress
   Member
   Posted 10 months ago #

   Bump. Anyone else seeing this with self-hosted CDN? Just moved my main sites to a new server/host, and would like to get W3TC running again.

3. robnalexpress
   Member
   Posted 10 months ago #

   This is related to the use of favicon.ico files. Another user posted about it here.

   On all 3 of my sites, this behavior began after uploading a favicon and adding the favicon to the site at WP admin/headway 2.0.11/Configuration/Options/Favicon Location.

   Anyone else using self-hosted CDN and favicons?

   I've submitted a bug report- waiting on help from Frederick.

4. robnalexpress
   Member
   Posted 10 months ago #

   This solution worked for me:

   On W3TC CDN configuration page, I removed favicon.ico from the custom file list and added the original (non-CDN) location of the favicon(s) to the rejected file list.

   I am still able to serve the favicons from the CDN by uploading them to the corresponding location in the CDN folder and designating this location in my theme.

   This is working for me on a 2-site multisite and a single site installation, all using self-hosted CDN.

   Hope it works for you too!

Reply

You must log in to post.