Quibbler
Forum Replies Created
-
Thanks for your detailed reply.
The reason I asked about completeness is that I have noticed extra whitespace in the minified versions of static pages. In fact a view source of a minified page shows that not only is there whitespace (0x20 space) in the file, there are sequences of several blanks in a row. All of those spaces can be compressed out.
The instances I have noticed are within links, typically between the attribute fields.
For example
<a title="explain" href="link">
. There are two spaces right before the href= that are not necessary AFAICT.Do you need a dump of such a page source?
Forum: Fixing WordPress
In reply to: Need Widget Documentation (RSS subscription)Thank you for your prompt response. Can you give me a hint where to look for the relevant code? Like what source file?
Forum: Plugins
In reply to: [WP Super Cache] [Plugin: WP Super Cache] Preload failures> You’re right about garbage collection. It’s an
> “expression of the owner’s willingness to serve
> up stale info for some period”.OK, now I am confused. As I understand them GC and expiration are separate concepts. Expiration happens in the cache index. It indicates that the cache contents should not be use. GC happens in the file system. It cleans up expired file so they do not accumulate.
> Updating posts or leaving comments will update
> those particular posts but not others therefore
> sidebar widgets may show stale info. Some people
> don’t care and they set a really long expiry time.
> I’m pretty sure the documentation mentions something
> like this.It may, but i read everything I could find but did not see it. Is there some other place I should be looking for doc?
> You can set the GC to be longer than 1799 minutes too.
Not according to the settings labels which state that
GC_interval = (expiration>1800) ? 600 : (expiration+10)
which cannot be larger than 1810 seconds. (1809 if you distrust the interpretation of “>” as really being “>=”).So how can I set GC to be larger than 1810?
Again we have to be careful about separating expiration and GC. For example, on one of my sites I might want to avoid staleness so I set expiration at 300 seconds, but I am not worried about old cache files hanging around so I want to set GC to 2,500,000 seconds (about a month). Definitely no more frequently than daily and then only at my off-peak time of day.
So how would I accomplish that (fast expiration, slow GC) with the existing UI?
Forum: Plugins
In reply to: [WP Super Cache] [Plugin: WP Super Cache] Preload failuresBug response: Found the problem. The check box “WP SuperCache Settings”/Advanced/Advanced/Clear-all-on-post/page is definitely unchecked. Similarly the clear-on-error is also unset. But 350 MB of debug logs later, I found the cache being cleared after post/page (in my case page) updates. So the check box is definitely broken.
Feature-wise, even if the cache gets cleared preload mode should dictate that the cache be re-preloaded immediately following the clearing.