I am trying to: use the options page in another language.
Link to a page where the issue can be seen: hidden link
I expected to see: An options page
Instead, I got: Fatal Error
This is pretty standard stuff. An ACF options page that is set to "Same fields across languages". I can't access the options page and somehow just having set that setting to "Same fields across languages" is now causing a Fatal Error on the front end of the site on all pages and templates in the non-default language.
It appears the problem arises from a conflict with the Flexible Fields on the Options page. Please note that we've encountered a similar issue before, and our development team has identified a solution for it.
Would you please try the workaround suggested in the ticket below?
Make sure to take a backup prior to making any changes. For your information, the option key name might be different in your case. If you're having the issue in German language only, the option name might be "options_de_resources"
Let me know if that helps or if you need further assistance in this matter. I will be happy to help.
I've found rows in the wp_options table de but only deleting all of them made that error go away. I was then able to access the options field group again in de. However, upon saving any field in de the fatal error returns and I can't do anything further. Do you have any other suggestions?
Glad that the solution solves half of the issue. However, If the error that appears while saving the field is the same as the one that you mentioned initially, maybe some invalid/corrupted option is still left in the Database. Would you please check by deleting them as well?
But, if the error is new, kindly share the full error log in the next response. I will check and let you know what to do next.
I have tried by deleting all non-default language rows in the options table but it still will not work when saving any field in the options page. Because it is hindering all progress as I cannot even access any page on the front end in the non-default language I have removed the flexible content fields and rebuild them using repeaters. There are some sites that will require the flexible content field on the options page so I hope a fix is added to future updates. However, for this site right now I have bypassed the issue.
Hello There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Happy to hear that things are now stable after the rebuild with Repeater. As our development team is able to trace the issue, I hope a solution for this issue will be included in the future version of the Advanced Custom Fields Multilingual plugin.
Feel free to let me know if there is anything else if you need help with. I will be happy to assist.
