Kimberly
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Minify] Slowing site downAre you setting to use “Pretty url” e.g. http://example.com/wp-minify/mycache.jss or are you leaving it so it shows the minify url e.g. http://example.com/wp-minify.php?f=file1.js,file2.js&m=439494 … If its the latter then its possible each time it is checking to recreate the cache file to use…assuming it is having issues trying to write it.
Just checking the QC config and i do notice “Sitemap Auto-Caching”. Notice the field: “List Of Additional URLs, to ‘Auto-Cache'”. From the description it seems to suggest that when the page expires it will do a Loopback Request onto the page resulting in a new page creation on its own. So that should be your solution, assuming you set the expiry time just moments before tweeting the new url.
Just realized you could also set up a chron job (via your Control Panel — or equiv) to delete any individual page(s) and rebuild it immediately at whatever time you want. That is what i do for one of my sites for a special case.
Btw, you could set up a CDN to serve the cached page too so that once it does get cached it is placed on a separate (much faster) server for those concurrent hits.
If you really want to geek out there might be a throttle-like wp plugin out there but if not it wouldnt be too difficult to write: In your header.php file you could run your own special php function that checks and stores the visitor IP. If he returns often at around the same time each day you could then throttle him and monitor the activity of a file count of how many people are accessing the page at the moment. When it drops below a certain amount then you let him proceed (or alternatively, just return back a HTTP 503 status code so he can try again later).
Btw, you mention bots. Are these bots done by you so that you can control when they hit your sites?
I assume they aren’t and so maybe you could just set the cache expiry seconds to a period prior (e.g. 1 hour) and have the plugin do an auto-rebuild of the file (notice it has this feature in its config panel)
That’s very intriguing. I think you’re right that if it is in the process of caching another visitor likely initiates another caching condition, etc.
I do notice that the /cache directory has a “lock” file which may indicate QC checks for the lock file and if it exists it tells the other process to wait. At least that is what i would do. I guess you could test this out by writing your own test code with multi threads and bang the site 10x asycnronously and see what is returned..if the footer shows the same time (down to the miliseconds — not sure if QC shows miliseconds so u may need to add that into the php file) then you know its the same page.
Forum: Plugins
In reply to: [WP Minify] [Plugin: WP Minify] Removing ?m= from the cache urlOh, if all you want is to remove the “?m=” postfix then just change line 625 of the wp-minify.php file from
$cache_url = $this->c->get_plugin_url().'cache/'.md5($url).$type.'?m='.filemtime($cache_file);to
$cache_url = $this->c->get_plugin_url().'cache/'.md5($url).$type;Forum: Plugins
In reply to: [Quick Cache (Speed Without Compromise)] Doesn't work. Nothing in source viewCurious:
1. Do you see a /wp-content/advanced-cache.php file?
2. Is your /cache directory empty? Are you logged out of your site when you visit the pages (logged in users dont get served cached files by default)Could be plugin conflicts. I remember having a similar issue and i had to disable both plugins then enable the other (not quick cache), manually delete the advanced-cache.php file, and enable qc to get it working.
Btw, i assume you arent running another caching tool.
Forum: Plugins
In reply to: [Quick Cache (Speed Without Compromise)] Quick Cache caches partiallyYour problem is very interesting. Curious, does it also have partial output issues when this plugin is turned off? When i look at QC code all it is doing is using a standard php function (ie ob_start() ) that changes the standard output to a callback function (when creating the cache file) which eventually gets output to the user’s browser. And so if it is doing what you are saying (incl. showing the QC footer) it seems to indicate that the problem may not be the plugin but the page itself — that some pages may just not be completing fully even when the plugin is off.
You might want to also use a DB cacher plugin too. That will help speed things up more.
Forum: Plugins
In reply to: [Quick Cache (Speed Without Compromise)] Quick Cache caches partiallyInteresting.
I do notice QC has a timeout of 0.01 for auto caching but i assume your pages are caching partially the normal way (by visiting the page and it caching in real-time). Its real-time cacher (non-auto-cache) doesnt have nor need a timeout setting so its intriguing your problem.
How slow is your site?
Have you tried disabling other plugins to make sure its not some plugin conflicts?
I’m looking over the QC code and right now i do see a situation where the buffer can timeout and it will just dump out what it has (hence: partial). But the situation seems to indicate your server is really bogged down and just giving up part way.
Curious..at the bottom of your “partial” cache file does it show the standard: <!– This Quick Cache file was built for or is it missing?
Btw, check for the error_log file for more info.
You may want to turn on WP_DEBUG in your config file too.Oops…i think i misread your post. From what i am gathering you are showing a page and on that page you are trying to randomize a list ordering each time a user visits that page.
Just to be clear Quick Cache caches an entire page and so to update a portion of a page you will need to refresh the cache of the entire page.
You are free to use javascript coding to randomize the ordering at least that way there would be no need to fiddle with Quick Cache at all (you would let it continue to cache the page for as long as it wants). That is what i would do.
Great! Glad to see my suggestion worked for ya (i checked ur site and noticed it now works in IE due to the fixed header).
You might want to set this thread as “Resolved” to close the question.
Cheers.
By default this plugin doesnt cache GET query urls. If that is the same case with you, you could merely just add a “?” to your url and it wont be cached.
If you are caching Gets then just append this to the url: &qcAC=0 to prevent caching.
Forum: Plugins
In reply to: [Quick Cache (Speed Without Compromise)] Quick Cache caches partiallyNo problem like that for me. I am curious…can you jump into its /cache directory, view the contents of one of the qc-c-* files and see to make sure your full html page code is present?
This way we know the page is truly cached and its only the outputting to screen that is the problem.
Just to add further, because the file that is returned is gzip’ed 3 times (due to the incorrect header) — i checked..it really is — the returned page to IE is confusing that browser since it expects “text/html” inside the gzip and all it finds is another gzip file. Smarter browsers realize to keep un-gzipping but poor IE hasnt a clue.
There might be a config issue with your server, or WP plugin settings conflict that causing the repeated gzips.
I notice your “Content-Encoding” header is all messed up. You have it currently as “,gzip,gzip,gzip” when it should be just “gzip“.
RE: why qc isnt working right now for ya….Could be a conflict with another plugin. Try disabling all your plugins and then enable quick cache.
Also do you see a “advanced-cache.php” file in you /wp-content directory?
Btw, even if u enabled DEBUG that doesnt mean you will see information about a plugin since it is dependent on a plugin actually writing out debug information which most plugins don’t unfortunately.