skunkworks

Strange. Didn’t work at all for us when tested.

I think the way it would work is:

1. WP Super Cache would flatten the php (English) to HTML…
2. Then the Transifex Javascript would take care of overlaying the translations on top of the flattened (English) html files
3. Prerenderer would then flatten them again into separate language versions.
4. Visitors will get either the WP Super Cache version of the page (English) or a Prerenderer version (Other languages)

Can anyone confirm?

Seeing this as well. Often with a string in front of the password attempted like “snoppyFailedLoginFooter” or “megadeath666FailedLoginFooter”

Someone’s Bot is broken X-D

Someone already built this.
https://www.ads-software.com/plugins/google-authenticator-per-user-prompt/

It sounds like WP Super Cache isn’t detecting the change and regenerating the cached files. How is the visibility changed by the plugin?
A CSS change? (display:none;” / display:block;)?

Have a peek at this. This may answer questions. It includes expires.

Following post.

Can anyone tell me why it wouldn’t have worked?

Thinking more of a…

It must have something to do with modified roles/permissions for the site in question.
I’ll look a little closer on my end before emailing you. Thanks

Yup.

In our plugins folder we have a custom plugin

wp-content/
|-plugins/
  |-custom-pack/
    |-custom-pack.php
    |-plugin-1/
    |-plugin-2/
    |-wk-google-analytics/

custom-pack.php is:

<?php
/*
Plugin Name: My Plugin Package
Description: Contains multiple sub-plugins including: plugin-1, plugin-2, & wk-google-analytics
*/

include dirname(__FILE__) . '/plugin-1/plugin-1.php';
include dirname(__FILE__) . '/plugin-2/plugin-2.php';
include dirname(__FILE__) . '/wk-google-analytics/wk-ga.php';

?>

• This reply was modified 8 years, 4 months ago by skunkworks. Reason: formatting

1. You mean the define('WP_SITEURL', SP_REQUEST_URL); & define('WP_HOME', SP_REQUEST_URL); ?
2. Done. (Had forgotten to do that actually. Thanks)
3. Did that.

The problem appears to be resolved after I tried a few things. But it may have been a Reverse DNS record issue. DigitalOcean also stated via support ticket:

We’ve actually removed that previously owned DNS zone from our platform. Can you tell us if you are still seeing this?

So in the end I’m still not certain what caused it, but the problem is resolved now.

Awesome. If you would like help in recreating my setup, let me know.

Same issue.
Subscribing for notifications.

Thanks. Found it. Disabled the javascript.
It appears to still function the same though.
Should I notice any difference?