polylang_mo and 404s, Take 2

  • Resolved ecdltf

    (@ecdltf)


    9 years, 9 months ago

    Hi Chouby,

    a couple of days ago I opened a thread with the same subject. Unfortunately I marked it “resolved” prematurely and added a post afterwards. Apparently you aren’t watching “resolved” threads, so please kindly excuse that I post it here again.

    Quoting my post from 16 June:

    OK, I found out where the 404s come from:

    It’s the cache preloading of WP Super Cache. It goes through the database and tries to pre-build every post with the post_status “publish”. Unfortunately the polylang_mo posts also have the status “publish”.

    I changed the post_status to “private” (line 45, mo.php) and saved the string translations, the 404s are gone and everything seems to work fine, so far.

    However I don’t know, if the “private” status has any negative effects I’m not aware of …

    What do you think?

    So far I only made this little change on my offline test site. It seems to be without negative side effects for the last 3 days. However, before I apply the hack to my online site, I would appreciate to hear from you wether it’s really harmless or I should better leave it as it is.

    Thanks in advance, and sorry again for the double post.

    Tom

    https://www.ads-software.com/plugins/polylang/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Chouby

    (@chouby)

    Hi!

    Apparently you aren’t watching “resolved” threads

    That’s right. Thus you were right to open this new topic.

    Thanks a lot for debugging this. I will include your fix in the next version. No side effect is to be expected.

    Thread Starter ecdltf

    (@ecdltf)

    Thanks for the confirmation, and thanks for including the fix!

    Tom

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘polylang_mo and 404s, Take 2’ is closed to new replies.