Error: 413 Request Entity Too Large loco translate

I cannot offer help with server problems. It’s a requirement of using the plugin that your server can receive posted data the size of your PO files.

My FAQ on the topic may offer some useful hints:
https://localise.biz/wordpress/plugin/faqs/postdata-limit

Can a po file be more than 128 mb?

and …is there another way to solve?

thanks

Can a po file be more than 128 mb?

Very unlikely.

and …is there another way to solve?

Other than what?

Other than:

– set post_max_size to 128mb
– add in .htaccess “LimitRequestBody 0”
– add in htaccess
<FilesMatch “admin\-ajax\.php$”>
SecFilterEngine Off
</FilesMatch>

Is there something else to do to solve my problem?

All the suggestions I have are in the link above. If there was something else I could suggest I would have added it to the FAQ.

As I’ve already said, I don’t offer support for server problems. Please ask your hosting provider for help if you can’t solve this on your own.

Hi This helped me:

# Fix for Loco Translate and any other plugin sending long strings to wp-admin/admin-ajax.php
<IfModule mod_security.c>
<FilesMatch “admin-ajax.php$”>
SecFilterScanPOST Off
</FilesMatch>
</IfModule>

in htaccess..

@stevek28 Thank you for this. You are the first person to mention the specific cause is “long strings”. Do you think the situation could be avoided by posting as multipart? i.e. making it look like a file upload.

Hi Tim @timwhitlock,
for me this sounds well worth trying! Sorry, I got no deeper insight on this issue – got the fix from siteground support..

Greetings and thank you for this brilliant plugin!
stefan

• This reply was modified 6 years, 2 months ago by stevek28.

below the console error message

Provide the following text when reporting a problem:
----
Status 413 "Request Entity Too Large" (text/html; charset=iso-8859-1 352 bytes)
413 Request Entity Too Large
Request Entity Too Large
The requested resource/wp-admin/admin-ajax.php
does not allow request data with POST requests, or the amount of data provided in
the request exceeds the capacity limit.
====

Hi Stevek28,
I added the following settings in .htaccess, but the same error message still appear.

<IfModule mod_security.c>
<FilesMatch “admin-ajax.php$”>
SecFilterScanPOST Off
</FilesMatch>
</IfModule>

Stonez

I have increased post max and file upload size. It doens’t help. I have same issue. Are you able to fix it? bro. I’m stuck for 2 weeks. Thanks a lot.

@timwhitlock I have the same issue with large .po-files like Woocommerce’s, and my hosting provider says that they have a security setting that stops large Reguests. Apparently the plugin sends the entire file in the request, and the solution to this would probably be (as has been suggested above) to instead post it with multipart. Any chance you are looking in that direction to solve this?

i just updated to Version: 2.2.2 and i now got the same problem, never had any problem earlier.

i checked the file size of the .po file that i’m trying to change, it is 952.5 KB so i’m guessing it’s some other problem than file size.

@redingeservice A nearly 1MB PO file sounds exactly like it’s a file size issue. It’s more likely that your hosting provider changed their security settings than it’s anything to do with 2.2.2.

@webbverkstaden As the pinned post says, multipart uploads are on the TODO list, but I don’t have time to investigate this right now and I can’t make promises as to when it will be implemented.

The current state of the plugin is that sending full PO files to your server as a POST field is a requirement. If you can’t post 900KB+ of data, then you simply can’t use the plugin. However, the issue is fixable by altering security rules.

This issue may have been a huge oversight on my part, but I never imagined four years ago that anyone would have a 1MB translation file. (Your server will be parsing that on every page view!)

I don’t have any other way to answer this question, so – any new posters who want to add their “me too”, please deal with this via your host, or use a different editor.