Plugin Author
Chouby
(@chouby)
Hi!
I don’t know where these http requests come from. ‘polylang_mo’ is a custom post type used by Polylang to store the strings translations. This post type is for internal use only and is not accessible. That’s why if someone attempts to access it, you get a 404.
Thread Starter
ecdltf
(@ecdltf)
Thanks for the swift reply.
Yes, the 404-producing requests are “internal” requests (no external IP).
But my string translations are all OK, so Polylang apparently does find the polylang_mo posts.
I have 2 similarly mysterious internal requests that are repeatedly producing 404s (‘/auto-draft/’ and ‘/main/’), so I think now that these and the polylang_mo 404s have a common reason.
Just to find out what it is … 😉
Thanks.
Tom
Thread Starter
ecdltf
(@ecdltf)
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?