zaewin

We have the same issue. This seems to happen when plugins are updated or when the database has changed, for example importing a new version from a staging server.

Updating permalinks IN polylang usually fixes the issue but it’s extremely problematic that it happens at all.

Any pointers or fix would be greatly appreciated.

Got the update and it seems to have solved the issue. Great work and thanks! ??

Created a test file here: https://bitbucket.org/magnusgronberg/polylang-test/src/master/ (should be public)

This is the output I get when I print_r($matches[1]) in the file_scanner function:

Array
(
    [0] => E-post
    [1] => E-post
    [2] => L?senord
    [3] => L?senord
    [4] => Logga in
)

As you can see, the two last strings are missing from the matches.

Hey

That’s really strange!
I’m using 3.1.0 of the plugin. Is there a way to “force” it to scan for strings again or is it done automatically?

Hi again!

Did find some php notices on SOME pages. I’ve fixed them and checked and re-checked the error logs and nothing is reported by php.

Still, caching does not work and the only difference between the development platform where caching works and the production platform is the HTTPS.

The HTTPS checkbox you mentioned is checked. Should it not be?

Hi and thanks for the answer! We did get it to work in development as I described in my follow-up post. However, on our production server with https, the cache does not work.

When I try to debug the functions in the plugin, they all seem to return true but nothing is cached. I’m still looking into it but maybe you could point me in the right direction in regards of the https vs. http problem?

Updating this issue. I found the reason the cache didn’t cache pages on our development platform. It was due to the plugin Widget Logic. I disabled that and things started working both with Twenty Seventeen and our custom theme.

However, doing the same things on our production platform did not solve the issue. On the production platform, we’re using https. Might that be an issue?
The cache did not work with Twenty Seventeen or our custom theme.

Is this true even for silent php errors? Our server does not have error reporting enabled but the plugin does not create any cache files.