I am trying to:
Translate ACF fields. I have fields that need to be translated inside of a flexible content layout inside a nested repeater inside a parent flexible content layout. Although the appropriate "Copy"/"Translate" selections have been made, the fields are not included in my XLIFF export. I created a new, simplified ACF group, and this functionality worked. However, when I try with my actual data, it does not. I believe this is because the field names of my actual data are very long. Is there a limit on the field name?
Link to a page where the issue can be seen:
NA
I expected to see:
All ACF fields that have been identified as "Translate" to be included on the XLIFF export.
Instead, I got:
Fields with long names (e.g., layout_modules_2_module_comp_content_section_content_rows_0_module_comp_content_section_content_rows_columns_0_module_comp_content_section_content_rows_columns_content_1_module_content_content) are not included on the export.
The issue might be due to limited PHP Max Input vars, Please increase the value to 5000. If you can handle this you can follow the link as a reference on how to increase the PHP max input vars hidden link. If not you can request your hosting provider to help you in this case.
I have a separate staged instance of this site on a different server with max_input_vars set to 10000, and I still have the same issue.
When I outlined the issue above, the field_name is exceptionally long due to nested repeaters and flexible content. To test whether the issue is due to nesting or field length, I went ahead and made a new, unnested ACF text field with a very long field_name. The result is that the text field doesn't work either. My assumption is that the error I am encountering is due to a limit on field_name within the WPML or ACFML plugins. Can you provide any insight on character limits?
In this case, the errors will be saved to a debug.log log file inside the /wp-content/ directory.
If you can paste your debug.log to pastebin.com and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess in the discussion).
I have requested our second tier supporters for their advice, I am able to reproduce on the sandbox installation. I will let you know as soon as I hear from them.
Thank you for the update, Raja. I look forward to hearing back from your team.
Unrelated -- is it possible to remove the unformatted code from my first message? I resent the code snippets with proper formatting in the second message.
Thank you for the update. Can you provide any additional information on when I can expect a fix? I need to be able to adjust project timelines on my end.
Raja currently has a few days off, He will be back on coming Monday.
Just for the update, I will like to let you know that our 2nd tier supporters are working on this issue, we don't have any ETA for the fix to be released.
Thanks for your patience, I have an update from the developer that the recommended field length is 130 character. However, we are still discussing the issue to accommodate the fields with a lengthy character name.
Unfortunately, this does not resolve my current situation. Individually, my field names are far less than 130 characters. Rather, the issue is the result of field names concatenating when fields are nested within flexible content and repeater fields.
Please let me know when the fix will be available. Thanks, Raja!
I will update the developer with your inputs, Unfortunately, it's unsure how soon the fix will be released, I will try my best to get some workaround or a possible solution, Based on the priority and intensity of the issue our developers work on the tickets,
