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

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?

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/

Thank you. I will look into this. Was that page created with Beaver Builder?

I will also set up a private message for this support ticket so you can provide the access details.

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.

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