ecdltf

Thanks for this very speedy reply ??

The thing with the placeholder %s is great. Formerly (with the number at the end) it didn’t really fit with German syntax.

BTW: The correct translation is “Zahl” (not “Nummer”). That is, for a proper German string you should do something like this: [contact label_captcha="Bitte die Zahl ?%s“ eingeben"] or simply [contact label_captcha="Bitte ?%s“ eingeben"]

The captcha label is not translated to German. Customization via shortcut [label_captcha="xxx] doesn’t work anymore. (String is fine but captcha number is not displayed.)

Thanks. I always thought this should have been already the case, since once I found some lines in AO’s php related to Hyper Cache (and other caching plugins). But I also noticed that it didn’t work.

What exactly has been improved?

+1 from me, too, of course.

In addition to this, some other – ugly – workarounds came to my mind:

• In a desperate attempt to express to my visitors that the language switcher won’t give them a 1:1 translated mirror of the other language, I posted a small text just beneath Polylang’s language switcher like this: “Some posts are not translated and only available on the German pages. Feel free to use the language switcher!” (You can see it if you click on my user name.) But I doubt that many folks will read texts in the side bar…
• I’ve not yet done it, but probably will try it in the next weeks: For each not translated post creating a ‘stub’ post in the other language(s). This stub should have the same title as the original post, and the text – and the excerpt – should be something like: “Unfortunately this post is untranslated. To see the original post (German) just click <here> or use the language switcher in the side bar.” To avoid any Google penalties a <meta name="robots" content="noindex,nofollow" /> tag should be added. (This can easily be done with plugins like Add Meta Tags.)

You can also use the following plugin Autoptimize to minify all your css and js files in combination with Hyper Cache ??

+1

I’m using the same combo.

We tested this cache out thoroughly […] but Google-ranking load-up times are identical to not installing […]

Do you mean the thorough testing consisted just of “Google-ranking load-up times” (probably “PageSpeed Insights”?)

Google is just one thing. At least try something like Webpagetest. This will give you lots of additional information that can really help you to set up caching (and other things) properly.

Now a couple of weeks has passed, I’m still using your plugin with my hack (see above) and still everything is working fine. Checkboxes work as expected, in QuickEdit as in normal mode.

Any chances that you’ll implement it (or something equivalent) to your nice plugin?

After a test I always send the results as mail to myself (there’s a button for that). That mail contains the full, detailed report in plain text form, which indeed is better readable than the charts. Also for non-colorblinds.

it’s also blocking the google share,when the plugin enable no one can share a post to goole+

I would consider this a good thing ??

Yes, you are right.

With 404-caching enabled, only 404s stemming from bots get logged. In order to log all 404s, the do-not-cache-404 option definitely must be turned on.

I didn’t see the difference because 98% of my 404s come from bots…

Thanks.

Tom

Thanks.

Note that there is a setting in Hyper Cache that controls whether or not it caches 404 results – this setting must be turned off in order for the errors to be logged.

Are you sure? As mentioned above, I observed it for a while with 404 caching On and Off, and couldn’t tell a difference (concerning the number of logged 404s).

For example, at the moment 404 caching is turned on – and there is definitely a 404.html and 404.html.gz in the cache directory – and Error Logger is happily logging as always (134 entries).

The footnotes appear on the page of the post, but it doesn’t appear for the post when it is on the front page. How do you add the bottom footnotes to the front page?

You mean for example a sticky page, right?

I consider this rather a feature than an inconvenience, because the tooltip always displays nicely and if you click on a footnote number you’ll be taken to the post’s page.

You can make them appear with a change in line 103 in easy-footnotes.php. Change…

if (is_singular() && is_main_query()) {

to…

if (is_main_query()) {

The ugly side effect is that they appear now also below the posts where only the first few lines (until the <!--more--> tag) are displayed. I didn’t test if there are other side effects, too. No guarantees. Maybe the plugin author knows a better solution.

Is there a way in the plugin core files to change the tag [note] to say [r]?

That’s in line 42:

add_shortcode( 'note', array($this, 'easy_footnote_shortcode') );

Change the'note' to something else.

Tom

Did you see this post from the WPSC author? Amongst other things he says:

“WP Super Cache will complain about mod_rewrite missing, and you should disable mobile support.” So this seems to be normal if I understand it correctly.

Some more posts on the subject:

• nginx + php-fpm + PHP APC + WordPress multisite (subdirectory) + WP Super Cache
• WordPress Super Cache rewrite rules for Nginx
• WP-SUPER-CACHE 1.2 WITH NGINX

https://gist.github.com/kurtpayne/4120936

With that plugin you just insert a plain text url-list of your website. That list then will be done by Auto Scan.

Thanks a lot for the hint. This works nicely ??

Now I’m just looking for a tool that provides me with such a plain text url list of my website.

Just export the ‘posts’ table from your database as CSV, open it in Excel or whatever, sort it, and copy the desired URLs from the ‘guid’ column (or a whole block of that column).

Tom