W3 Total Cache "unresolved errors"

  • I’m getting the error

    The unsuccessful transfer queue has unresolved errors. Empty the queue to restore normal operation."

    I am running multiple sites on the same domain.

    domain is a blog
    domain/site2 is also a blog, etc.

    when I click “unsuccessful transfer queue” I can see…

    Local Path
/var/www/vhosts/domain.com/httpdocs/site2/wp-includes/js/thickbox/some.png

Remote Path
site2/wp-includes/js/thickbox/some.png

    … under the Upload Queue errors list.

    /site2 is not a real directory, so that may be the problem, WordPress generates it, and W3 Total Cache is acting like it exists.

    I do not get this type of error on the primary blog.

    The site displays properly, so I’m not sure there are actual upload errors. Does anyone know what this is and how to resolve it?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Frederick Townes

    (@fredericktownes)

    Is it possible to switch to an origin pull CDN? Otherwise please submit a bug submission form from the support tab of the plugin.

    I get the same error, always get unsuccessful transfer queue when uploading images to this 1 blog via Live Writer, it happens only on this 1 blog out of 5 (3 hosted on same provider don’t have same issue).

    Total Cache sucks when it comes to cdn and there are very few solutions, just the suggestion to submit a bug report. I’ve now binned it to try something that works….

    Thread Starter cbmc

    (@cbmc)

    I wish Rackspace would make their own WordPress CDN plug-in to replace this.

    funny enough, it’s Rackspace I’m with. and yes, it would be good if the got something to replace this…

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    The problem isn’t W3TC per se, it’s the randomly updated API and the poor performance of it when it does work. Maintain a list of files to update is stupid and cloud files is not the modern CDN paradigm, origin pull or copying files directly from the web site to the CDN is the modern approach, which is much more sustainable and easy to maintain. WordPress is for publishing, not for maintaining for queues of files from the file system.

    CDN providers are not going to make plugins because they don’t want to optimize applications they want to sell bandwidth. If it were easy for them to replace me it would have happened before I started.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘W3 Total Cache "unresolved errors"’ is closed to new replies.