Error: not extended

My guess is this error comes from some security software you have installed. Either at server level (like mod_sec), or as a WordPress plugin (like WordFence). It’s not an error that my plugin would throw unless the HTTP request is being examined by some other process.

It’s very unlikely to be directly related to translation files/directories or missing templates. I can’t imagine any script error that would result in a HTTP 510 code. Much more likely to be raised by some intermediary.

Hi. Thanks for help, you were right! My hoster deactivated the security rule “ModSec”. Now you’re plugin works fine. Question: Will the changes I will made over loco translate be overwriten when updating WordPress?

Thanks for the update.

Nobody has ever been able to tell me what the specific security rule is, and why ModSec considers WordPress Ajax unsafe. Any additional info would be appreciated.

Will the changes I will made over loco translate be overwriten when updating WordPress?

Some locations can be overwitten by WordPress during updates. You should choose a safe location for your own custom files whenever possible. See https://localise.biz/wordpress/plugin/manual/msginit

As a rule:

• Never save files inside themes or plugins (“Author” location).
• Never edit existing author-supplied or system-installed translation files.
• Only save your own files in the global languages directory if WordPress translation updates are disabled.
• Always backup all your files before any WordPress update.

• This reply was modified 8 years, 1 month ago by Tim W.

Hi Tim.
Thank you very much for this helpful informations. Create a loco folder for my changes, works fine! Great!
René