Split: Failed to parse because your job is above file limit of 1MB

This thread is resolved. Here is a description of the problem and solution.

Problem:
When attempting to update a translation by making slight changes to the original page and accessing the translation editor, an error occurs. This issue arises when the translation status is 'waiting for review,' preventing the translation job from updating.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
1. Edit the page in the original language.
2. Make a small change and save it.
3. Go to WPML → Translation Management.
4. Find the page and send it for translation, choosing 'translate myself'.
5. Navigate to WPML → Translation and complete the translations from there.
This process should update the translation job for the page.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum for further assistance.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic is split from https://wpml.org/forums/topic/shortcode-translating-fluent-forms/

Tagged: ATE, Exception

This topic contains 20 replies, has 0 voices.

Last updated by Andrey 1 week, 2 days ago.

Assisted by: Andrey.

Author	Posts
March 20, 2025 at 12:48 pm #16840065
Michael	Also when I tried the trick with make a slightly change to the page (in the orig. language) a 2nd and 3rd time and then go to the translation editor, I get this error - see screenshot attached. Is this something on the wpml site itself? As when in the translation editor its a hidden link?.... link and not the website url itself.
March 20, 2025 at 12:57 pm #16840123
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Does the same issue occur if you create a new page, for example, a page that contains the same form you are trying to translate? Our development team is working on similar reports and will probably disable this limit as the new approach is applied. Therefore, this will be improved shortly.
March 21, 2025 at 3:14 pm #16845176
Michael	Hello Andrey, I checked today again and so far it works normal reg. the WTE failing to load (with the 1 MB data limit). Did you guys increase that limit now? Sending you kind wishes, Michael
March 21, 2025 at 3:50 pm #16845406
Michael	Eiei,.... I just did another try for WTE for one page with a shortcode Andrey. And its for this one here: hidden link Same story as 2 days ago - the "file limit is above 1MB" shows up again. Sorry to bother you, nevertheless need to mention it. Best wishes, Michael PS: I did again use the Shortcode description here: https://wpml.org/documentation/support/language-configuration-files/translate-custom-shortcodes-with-wpml/#:~:text=To%20translate%20shortcodes%20from%20compatible,rest%20of%20your%20page%20contents. ...to bring the xml snipet into the WPML - settings - custom XML configuration. But of course this thread here is about the "file limit with the WTE.
March 21, 2025 at 6:00 pm #16846136
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	I’m sorry that you ran into trouble with this. I cannot say for sure if the limit has been raised, but our team is working on similar reports. And its for this one here: hidden link; Is this a new page or an existing one?
March 21, 2025 at 7:11 pm #16846269
Michael	It is an existing page on the same website. So yes - lets wait for your dev team on it... Thanks for your feedback! Cheers, Michael
March 21, 2025 at 8:17 pm #16846390
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you, Michael. I will check this page as soon as I gain access. For now, I have downloaded the original XLIFF file of that page, which is 2.2 MB in size. I've enabled debug information for this support ticket. Please refer to this link for instructions on how to retrieve this information from your site and provide it to us: http://wpml.org/faq/provide-debug-information-faster-support/
March 21, 2025 at 8:35 pm #16846436
Michael	Yepp - is done happily Andrey. With kindness, Michael
March 21, 2025 at 8:57 pm #16846470
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you. I will look into this. Was that page created with Beaver Builder?
March 21, 2025 at 9:32 pm #16846502
Michael	Yes - its using the Astra Pro theme and Beaver Builder as the pagebuilder.
March 24, 2025 at 12:33 pm #16851846
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	I will also set up a private message for this support ticket so you can provide the access details.
March 25, 2025 at 5:35 pm #16859300
Michael	Hey Andrey, getting back to you today. The credentials for WP and for Ftp were sent with the other support thread just 2 minutes ago. You could get it from there, right? Sending you kind regards and have a good day, Michael
March 26, 2025 at 4:23 pm #16864248
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	I found out that the page builder settings were set to Translatable. This is where the issue comes from, as all builder settings were added to the translation, which was unnecessary. This overloaded the translation job with many strings and exceeded this limit. What did I do? 1. Go to WPML → Settings → Custom Fields Translation and set the option " Show "Multilingual Content Setup" meta box on post edit screen". This option allows the custom fields used for a particular page to be seen on the page when editing the original. 3. Go to the Kontakt page, scroll ot the bottom, and click on Show system fields 4. Set the following settings for these custom fields and save: _fl_builder_data Don't translate _fl_builder_data_settings Copy _fl_builder_enabled Copy _fl_builder_draft Don't translate _fl_builder_draft_settings Copy 5. Update the original page with a few changes to update the page translation. So, the new translation job is set to ATE without unneeded strings when you click to translate or maybe send the page from WPML → Translation Management for translation myself. I have uploaded a screenshot for your reference. Those changes for the custom fields are set for the entire site. You might need to update the page translation for existing pages to reflect the changes.
March 27, 2025 at 11:28 am #16867980
Michael	Hi Andrey, oh wow... okay that makes sense. I will try that with some of the pages later. Just saw it for myself onthe contact page. So in case an existing page has issues still with the ATE, I would manually go in that page (with EDIT PAGE) and set these 5 settings _fl_builder_data Don't translate _fl_builder_data_settings Copy _fl_builder_enabled Copy _fl_builder_draft Don't translate _fl_builder_draft_settings Copy as seen above. If I got you right... 🙂 Many thanks to you Andrey! With kindness, Michael
March 27, 2025 at 1:10 pm #16868590
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Hello Michael, So in case an existing page has issues still with the ATE, I would manually go in that page (with EDIT PAGE) and set these 5 settings There is no need to set those custom fields. Those are already globally set. If the existing page still has issues with the ATE, you would need just to update the page translation to ensure the new changes are applied. Thank you for your feedback 🙂 Andrey