-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Language Switching Buttons missing in ACF options #1233
Comments
What do you mean with Option Pages, which one? How did you configure the Field Group to be active on such pages? As a side note - with ACF 6 there's a brand new UI and I can't find the language buttons for the Field Group Title for example, this seems broken... But it's another problem, better create separate issues. |
I created an Option page for each of my main "Features", and then in ACF set the Rule to Options. I prefer to work this way to simplify he UI for the client. They don't have to go to pages then. See attached screenshots. `if( function_exists('acf_add_options_page') ) { add_action( 'storefront_before_content', 'tsum_before_content_domain_header', 1 );
|
The options page are only available in the PRO version that I don't have 😕 |
Between 3.12.0 and 3.1.22.1 I refactored the ACF structure in #1191 but it was supposed to maintain all the existing functionalities. What is surprising is that you also had issues in 3.12.0. Has this page already worked before? @ChristophJeworutzki do you observe the same problem? Did it work with 3.12.0, and if not, did it work before? |
A regression was introduced in 3.12.1, because the ACF admin was setting its `qtranslate_admin_config` hook too late. That filter must be set before action `qtranslate_init_language` but it can't be done with `plugins_loaded`. This patch restores this hook earlier when the module is loaded, by calling `qtranxf_acf_init` to do the full init at that time. The loading sequence will be revisited for all modules.
@schalkjoubert @ChristophJeworutzki I found the problem with the LSB in ACF options page, it was a regression in 3.12.1 with the init sequence, now fixed in master. I don't know about the problem on the front-end with the tags, I expect it to work normally. Could you test the current version on master? Note there's a known problem with ACF 6 for the field group name but that's another topic, see #1227. |
Strange, why is this working for me? WP 6.1.1 (Twenty Twenty-One) Edge, Firefox |
Strange indeed, but the fix from 7a660fe is needed. |
Many ACF fixes released in 3.13.0. |
Since version 3.12.1, the language Switching buttons are missing, even though that is selected under Editor Mode
Instead the Simple Language Mode is used.
If I revert back to 3.12.0, the buttons show, but then the front en display both language with theur tags, ie.
:en]The family’s philosophy is structured around a simple principle: selecting the best terroir and partners: Sancerre and Provence in France, Stellenbosch in South Africa and Sicily in Italy, relying on local expertise in each of these estates.[:]
This only happens for custom fields on Options Pages.
Standard wordpress Pages and Post do however display the buttons.
Please see screenshots attached,


Thank you
The text was updated successfully, but these errors were encountered: