I am getting this error message
the unsuccessful transfer queue has unresolved errors. Empty the queue to restore normal operation.
and
A configuration issue prevents CDN from working: The "Replace default hostname with" field cannot be empty. Enter CDN provider hostname here. (This is the hostname used in order to view objects in a browser.)
What to do please explain. I am really fed up of this issue and i am using cloudflare but it is not working so suggest me what to do asap
Hi petrich
Bit of a longshot here (you posted 4 months ago) I was just wondering if:
a) You resolved this problem?
b) You can remember how?
I have the exact same issue on my IIS server.
Thanks!
@pwizard this has been the issue. it only seems to work when you either make a slight change in the plugin or clear the cache.
naturally a caching plugin is rendered obsolete when it requires the user to constantly clear out the cache for it to work properly...
I've even submitted a bug report with no response and I've been a paying customer of them too this year!
It has disappeared and remained that way since disabling the plugin...
Further Googling finds this was an issue for a lot of sites several months ago, was fixed with an update but I am running latest version. The plugin is running on another site with no issue. Weird.
Hello,
I've just moved a site to another location and realised that I've got APC enabled which is no longer supported on the new host. I'm unable to activate or reinstall as the database setting remain intact.
Any idea how I can turn off APC from the database / mySQL ?
Thanks,
Nic
That's because your object cache isn't an endless bucket, it has limits and needs to purge old objects occasionally. This is different to the default behaviour because transients stored in wp_options are effectively endless (and long-lived even when they do have an expiration set!)
See this blog post on WPEngine for more information:
https://wpengine.com/2013/02/wordpress-transient-api/
This is why WP e-Commerce, WooCommerce etc. are _doing_it_wrong() when they use transients to store cart sessions; those transients may be dropped at any time to find space to cache more recently accessed objects. Bear this in mind when using transients for storing things that you actually do care if you lose -- transients are, by definition, ephemeral and not a safe place to store information you depend on.
cheers,
Ross
Sorry about the duplicate posts Jan - I tried to edit the original, but it somehow got reposted each time.
Anyways -
I obviously entered something wrong with my first CDN effort, but I wasn't about to try and replicate the deletion trick; it took over 1 hour to re-upload all the files & folders via FTP.
My 2nd attempt:
Exercising a little more care this time; I did get a self hosted CDN running OK on a cookieless subdomain.
I was however disappointed to see negligible improvement in page load time. (I used Firefox for the tests, & I realize results can vary quite a bit between browsers)
Obviously a CDN is supposed to be just that - not a pretend one on the same server.
This is a fairly fast VPS, running DSO with Mod Ruid 2.
With shared hosting, a self-hosted CDN may be more worthwhile.
One thing I did find out:
A self-hosted CDN with 1 subdomain is marginally faster.
A self-hosted CDN with 2 subdomains, is actually SLOWER.
So if anybody is wondering about setting up multiple subdomains for a self-hosted CDN; don't bother (in my experience anyway).
Thanks a lot for the explanation Ross!
In following many of the guides online, I have found that many of them rely upon using 'if' statements to allow/disallow caching of pages.
Example:
set $w3tc_rewrite 1;
if ($query_string != "") {
set $w3tc_rewrite 0;
}
if ($http_cookie ~* "(comment_author|wp\-postpass|w3tc_logged_out|wordpress_logged_in|wptouch_switch_toggle)") {
set $w3tc_rewrite 0;
}According to Nginx this is Evil: http://wiki.nginx.org/IfIsEvil
Is there a way of writing such arguments without using the evil 'if' statement so that we don't have to slow down nginx so much?
It would be awesome if anyone can point us to a good set of rules for w3 that don't use the 'if' statements.
I had a similar problem about 5 months ago. It turned out to be an issue with the theme I was using for the WordPress-based site I maintain. Apparently, one of the theme functions called "is_user_logged_in()" which ended up getting the "wordpress_logged_in[HASH]" cookie to be dropped. As a result, W3 Total Cache and another plugin I use thought a visitor to the site had been logged in. In my case, I simply commented out the call to "is_user_logged_in()" and I never found out what caused that cookie to be dropped.
I submitted a WordPress bug report and working with a developer, I found the "is_user_logged_in()" function, itself, wasn't doing anything wrong so there's something my theme is doing that was causing the issue.
So, if you're using a custom theme, see if the caching issues persist if you temporarily switch to one of the "stock" WordPress themes.
Peace...
New post cannot be seen for non logged in user for long time, since i have a busy site. We post over 50-60 post every day also it keeps matter to display instantly after posting.
Please tell solution
Have you looked at the default cache settings? How long does it take for new posts to appear? Do new comments take a long time to appear as well?
I just conducted a test where a new post and a new comment didn't appear when I first viewed my blog in my test browsers but a refresh of the page caused the new post and new comment to appear just fine.
So, if you have a busy site, you will want to look at your database and browser cache settings, at the very least, to make sure the current settings will work for you and adjust them as necessary.
Peace...
The "if" statement isn't evil. The person coding "if" statements as shown in that Nginx article is evil or inexperienced. :)
Peace...
I am having same problem kited here http://wordpress.org/support/topic/new-post-can-not-be-seen-on-the-homepage?replies=17
Right now i have disabled browser cache to solve this problem, still some time it takes upto 3-4 min to show new post. before it was upto 30 mins for non logged in user
here is my setting
Page cache--> Enable
Page cache method---> basic
Minify- Enable
Minify mode- Basic
Minify cache method- disk
Database cache - not enabled
object cache- enable
object cache method- disk
Browser cache- not enable
OK, modifying
/public_html/wp-content/w3tc-config/master.php
Did the trick
WPML team was notified, and they plan to make it compatible with W3TC minify rewrite in next release
http://wpml.org/forums/topic/rewrite-problem-wpml-w3-total-cache-with-minify-cloudfront/
I set up with Amazon s3 for CDN but have that and most other functions un-enabled. I see my site in FF and Chrome but not IE9 (I went to google and came in on other pages on my site and the page appears until I refresh the page and then I have a white page again.
I cleared the browser cache but no difference in results.
When I run Pingdom.com (W3TC turned on) it measures my site at 353MS and 1 request and returns a blank page. With W3TC deactivated it returns 109 requests and a thumbnail of the page.
I did have photon from Jetpack turned on and I turned that off... in fact I turned off all plugins except askimet and Jetpack and the problem still occured.
I'm not happy with cache in general but being on a shared server and running into my busy season (my site is about fall foliage in New England) So I can't be down playing with this useful if I could getting it working plugin...
In the install window I see this:
# chmod 755 /var/www/vhosts/domain.com/httpdocs/wp-content/
But I looked and so did the tech support people at Bluehost and they say all of my WP-Content folder is 0755 (also what or where is this HTTPdocs folder or directory? My folder above /WP-content is /public_html/wp-content. So color me confused on that message... or is it generic?
My site is jeff-foliage.com but I'm going to go to bed so I'm turning it off since I can't tell if my users are seeing my site with it on...
Contact me and I will turn it back on...
Jeff
Strange. I just tried a test with your settings above and my test post and test comment response both showed up immediately and after one browser refresh. With W3 Total Cache disabled, the fact it takes 3-4 minutes for new posts to show tells me there's another bottleneck in your WordPress environment.
I presume you've tested your blog with no plugins enabled and then with only W3 Total Cache enabled? Also, have you tried the suggestions by Frederick Townes in the thread you reference above?
Peace...
Ah, found the culprit
Was Google Maps Plugin by Daniel Martyn
...I wonder how that happened
In the Minify tab, stick "Enable" only and unstick all other options.
Clear cache and check.
If it's still the same:
Minify tab --> JS, choose "Combine only"
I faced the same problem as you did before and it do work for me.