Hi Maxime,

Awesome plugin ! I'd like to disable the translation functionnality on certain options page. Is it possible with the work you've done ? With a filter perhaps ? I haven't seen anything that could allow me to do so.

Thanks for your feedback,

Olivier

Version information

• Plugin version : 1.1.5
• PHP : 7.0.33
• WordPress : 4.9.9
• ACF version : 5.7.9 (pro)
• Polylang version : 2.5.2

Steps to reproduce

1. Créer un menu et l'associer à un emplacement de menu
2. Réaliser l'appel avec la fonction wp_nav_menu();

What happened instead

L'appel de la fonction génère l'erreur PHP suivante :
Catchable fatal error: Object of class WP_Post could not be converted to string in /plugins/acf-options-for-polylang/classes/helpers.php on line 16.

Nous avons tenté de désactiver les autres plugins ainsi que nos fonctions perso, mais rien ne change. Nous avons tenté de rétrograder la version de votre plugin et l'erreur disparaît à la version 1.1.3.

• Plugin version : 1.1.5
• ACF version : 5.7.7
• Polylang version : 2.5.2

Bonjour,

Je tiens d'abord à vous remercier pour ce plugin bien utile !

Je rencontre un problème avec les champs de type "Répéteur".
J'ai deux langues configurées (Anglais et Français). Lorsque je ne renseigne aucune valeur pour mon champ sur ces langues, la valeur de "All languages" n'est pas récupérée.
J'ai pu voir un sujet expliquant ce problème mais il a à priori été corrigé depuis.

Je dois louper quelque chose mais je n'arrive pas à voir quoi.

Hi

After installing the plugin, the frontend of the website displays this:

Fatal error: Uncaught Error: Call to undefined function BEA\ACF_Options_For_Polylang\acf_options_page() in C:\wamp\www\projectname\wp-content\plugins\acf-options-for-polylang\classes\helpers.php on line 75

Backend has no errors but does not work as saving overwrites other language value.

Thanks

Dans le cadre d'une activation sur un site comportant déjà des champs et contenus ACF dans les options, si l'on active en premier Polylang puis ACF-options-for-polylang, on perds les données des options. Il serait bon de garder/copier les données existante dans la langue principale / voir dans les deux langues.

Version information

• Plugin version : 1.1.7 |
• PHP : 7.2
• WordPress : 5.4.1
• ACF version : 5.8.11
• Polylang version : 2.7.2

Steps to reproduce

1. Create new field group and assign it current user role is equal to administrator
2. Go to users >> user >> put some information in english
3. Switch polylang to language other than english

What was expected

Field have empty value in this language. If content is added and saved, it should appear for the selected language

What happened instead

The content from default language stays in

Version information

• Plugin version : 1.1.0
• PHP :5.6
• WordPress : 4.9.4
• ACF version :5.6.8
• Polylang version :2.3.4

Steps to reproduce

1. I activated plugin

What was expected

Effect

What happened instead

No effect. Nothing has changed

For each language (English, French and spanish for example) a specific value is entered in a simple text field located in a option page.
Everything is OK in the WordPress backend.
But when I wanted to display it on frontend by using the "the_field" function nothing is display for the current language

Version information

• PHP : 5.6
• WordPress : 4.9.8
• ACF version : 5.7.7
• Polylang version : 2.3.11
• Theme : Twenty Seventeen child theme just for modifying header.php for this use case.

Steps to reproduce

1. Register an option page
   

2. Create a field group with only one simple text field and located in the option page
   

3. Enter for each language a different value - in my case "simple_text"
   

4. Modify a template of the theme to display this field - <?php the_field('simple_text', 'option') ?>
   

5. See "what happened instead" point
   in english
   

in french

in spanish

6. Enter a value in the simple text field with Polylang language switcher on "Show all languages"
   

7. See that for each language that is this value is displayed on frontend
   in english
   

in french

in spanish

What was expected

Display the correct value for the current language on frontend

What happened instead

Nothing is displayed for the current language

Version information

• Plugin version : dev-master (via Composer)
• PHP : 7.1.26
• WordPress : 5.2.3
• ACF version : 5.6.10
• Polylang version : 2.3.10 (Polylang Pro)

Steps to reproduce

1. composer require wpackagist-plugin/acf-options-for-polylang
2. Activate plugin

Details

• Error: Uncaught Error: Class 'BEA\ACF_Options_For_Polylang\Admin' not found
• Shown because of missing classes/admin.php file when installing via Composer
• During Composer installation, Wordpress.org authentication error given and plugin rather installed from dist (GitHub?)

Failed to download wpackagist-plugin/acf-options-for-polylang from source: Package could not be downloaded,
svn: E170013: Unable to connect to a repository at URL 'https://plugins.svn.wordpress.org/acf-options-for-polylang/trunk'
svn: E230001: Server SSL certificate verification failed: issuer is not trusted

Now trying to download from dist

• If explicit version is given during install (composer require wpackagist-plugin/acf-options-for-polylang 1.1.7) then admin.php is installed and plugin works as expected

Hello.
I have Polylang Pro and ACF Pro. I have two languages english and spanish, in the backend I have some text field which displays correctly for each language but in the frontend spanish texts are shown in english HP. why?

To fix the problem I did like that forcing page ID according to the language:

if(get_locale()=='es_PE'){
$pageID = 6;
}else if(get_locale()=='en_US'){
$pageID = 243;
}

otherwise page ID is always 6 also for 'en_US'.
This is not an elegant way to solve but it works

Thanks

Lorsque j’essaie de récupérer un champs “repeater”, j’ai en retour, le nombre d’éléments qu’il contient et non le contenu.

J'ai encodé les valeurs dans "toutes les langues" et non pas dans chacune d'entre elles.

(J'utilise ACF Pro et Polylang Pro à leurs dernières versions).

Bonjour,
Nous rencontrons un soucis lors de l'utilisation du plugin sur notre environnement de développement. En effet, quelque soit la langue sélectionnée, la valeur est sauvegardée pour toute les langues active.

Version des extensions utilisées :
Wordpress : 4.8.2
ACF Pro : 5.6.4
Polylang : 2.2.3
Polylang's ACF Option page : 1.0.1

J'ai réalisé un test en local avec les même versions des plugins ainsi qu'avec les dernières versions disponibles, et le problème persiste. Avez-vous déjà eu écho d'un problème similaire ?

Merci beaucoup.

see : BeAPI/bea-plugin-boilerplate#14

We have noticed that Options are not properly retrieved in certain languages and I am confident I have narrowed it down to this line:

$_post_id = preg_replace( '/(_[a-z]{2}_[A-Z]{2})/', '', $post_id );
in classes/main.php#61 BEA\ACF_Options_For_Polylang\Main::get_default_reference

Updating the regex to sprintf( '/(_%s)/', pll_current_language( 'locale' ) ) should do the trick. This properly removes the current language, however it also means that the default can only be reached from the current language which might not be ideal...

Version information

• Plugin version : Master
• PHP : 7.1
• WordPress : 4.9.4
• ACF version : 5.6.10
• Polylang version : 2.3.4

Steps to reproduce

1. Translate an option

What was expected

Display the translated value

What happened instead

All language value is displayed.

Reason

Requirements never actually checks requirements on frontend as it's only hooked into admin_init

https://github.com/BeAPI/acf-options-for-polylang/blob/master/classes/requirements.php#L13

Hi there,
Thank you so much for this awesome plugin. One thing though.... I recently added it to an existing site of mine and I came up with an SQL-Script that does two things:

1. It moves all stored data from "All languages" to en_GB
2. It copies existing fields to a new language (de_DE) in my case

I think this can be very useful for other users too, e.g. if add the plugin to an existing site or you add a new language and don't want to start from 0 with your settings.

Also it cleans up the "All languages"-data, which could be a good solution for Issue #37

If you tell me where and how you would like that information in your Readme, I am very happy to make the changes and open an Pull request for it.

The MySQL:

# Rename current options
UPDATE {YOUR_TABLE_PREFIX}options SET option_name = CONCAT('options_en_GB', TRIM(LEADING 'options' FROM option_name)) WHERE option_name LIKE 'options%';
UPDATE {YOUR_TABLE_PREFIX}options SET option_name = CONCAT('_options_en_GB', TRIM(LEADING '_options' FROM option_name)) WHERE option_name LIKE '_options%';

# Duplicate options
CREATE TEMPORARY TABLE tmptable_1 SELECT * FROM {YOUR_TABLE_PREFIX}options WHERE option_name LIKE 'options%' OR option_name LIKE '_options%';
UPDATE tmptable_1 SET option_id = NULL;
UPDATE tmptable_1 SET option_name = CONCAT('options_de_DE', TRIM(Leading 'options_en_GB' FROM option_name)) WHERE option_name LIKE 'options%';
UPDATE tmptable_1 SET option_name = CONCAT('_options_de_DE', TRIM(Leading '_options_en_GB' FROM option_name)) WHERE option_name LIKE '_options%';
INSERT INTO {YOUR_TABLE_PREFIX}options SELECT * FROM tmptable_1;
DROP TEMPORARY TABLE IF EXISTS tmptable_1;

# Show the results
SELECT * FROM {YOUR_TABLE_PREFIX}options WHERE option_name LIKE 'options%' OR option_name LIKE '_options%';

Thanks,
David

im reporting and issue i recently update my acf pro to v5.8.4 and i noticed that if i have a new entry in options specially field image it only return is the attachment id even i assigned it to array or url.

Please help.
Thanks.

Screenshot explaining the result

Hi, first of all, thank you very much for the much needed plugin that allows ACF Options to be linked with Polylang, I am happily using it on several sites already.

My question/feature request: is there a way to retrieve an option in a different language than the one currently being used on the frontend? Say I am browing the English version of the website, but I need to get an option value of a German version. I could naturally do it via WPDB, but I am hoping there is/could be another way, maybe as a param to a method, where the default value would be the currently used language?

Something along the lines if beapi_get_option($name, $language = pll_current_language()) {}

TO BE FINISHED : https://github.com/BeAPI/acf-options-for-polylang/blob/true-plugin/classes/plugin.php#L22
Check on local env.

Use old main file check.

Version information

• Plugin version : 1.1.4
• PHP : 7.2.10
• WordPress :
• ACF version : 5.7.7
• Polylang version : 2.4

Steps to reproduce

1. Add acf field in term
2. do get_field('NAME_OF_FIELD'), WP_Term Term) on page.

What was expected

No error

What happened instead

( ! ) Catchable fatal error: Object of class WP_Term could not be converted to string in /var/www/html/web/wp-content/plugins/acf-options-for-polylang/classes/helpers.php on line 16

My opinion

1. The problem come to
   add_filter( 'acf/validate_post_id', [ $this, 'set_options_id_lang' ], 10, 2 );

Filter is deprecated and dont work with acf term field.

Fatal error: Cannot declare class BEA_ACF_For_Polylang, because the name is already in use in /var/www/...../wp-content/plugins/acf-options-for-polylang-master/acf-options-for-polylang.php on line 15

Would be great to have this plugin in the official wordpress repository or on wpackagist.org. We install plugins with PHP composer, this just works from wpackagist.

Salut Maxime -

Merci pour avoir écrit ce plugin!! Pourtant j'ai du mal a charger les options de la langue défaute.

After installing, I have re-entered the site options in the site's default language, 'en', and also in "Show all languages", where the values in the repeater fields were absent. I have not duplicated my options field group in any other lang yet.

I want to be sure ACF (with the BEA plugin) will return the default lang options if none are present in other langs. However, on other langs the usual template tag does not return any stored value:

get_field( 'field_name', 'options' );

Is there a function to get a stored option in a specific lang? Or am i doing it wrong?

It will become a bit confusing to have the All Languages content also required. Can we not set English to the default, and so when All Languages is chosen it shows the English? Same if we choose English. I dont want to have to tell the customer they have to add all English content in both All Languages AND English.
Thanks

Version information

• Plugin version : 1.1.7
• PHP : 7.4
• WordPress : 5.4
• ACF version : 5.8.11
• Polylang version : 2.7.3

Steps to reproduce

1. create a field "text" and "Google Map" in "All languages"
2. Complete fields in options
3. Try to get fields

What was expected

Get both field for all languages

What happened instead

Only field "text" appear
If I complete "Google Map" field for a specific language, all is working fine

So I think, the plugin don't get "Google Map" field for all languages

Hi,
I would like to try your plugin but it appear to did'nt work with this plugin
https://wordpress.org/plugins/acf-cpt-options-pages/ which creat option pages for archive cpt...

Could you please check it ?

thank you very much

What was expected

My old options page should be added upon plugin activation to the new options page. It's possible to fetch them like so:

get_options('name', 'options'); // for the default language
get_options('name_da', 'options'); // for the translated language

We have some quite huge options pages, so would be sweet if this was supported.

What happened instead

Options page is empty. I have to migrate all data manually.

Hi Maxime,

Managed to get the plugin working but it doesn't seem to work when I make a call to the REST API. It only returns the default language data. I'm using the plugin ACF to REST API which is like your plugin : pretty cool !

Have you had any use of make an API call to an multilingual option panel before ?
Any ideas on how to bypass that ?

Thanks for your feedback,

Olivier

i installed it but i don't see any effects

Version information

• Plugin version : 1.1.7
• PHP : latest
• WordPress : 5.4.1
• ACF version : 5.8.11
• Polylang version : 2.7.3

Steps to reproduce

1. Have an option page with default values, ready to be translated.

What was expected

I don't understand how this plugin is supposed to work. Once activated I go to my options page, but I don't see any way to select another language. There's nothing there. The README mentions: "Once this plugin is activated, you will be able to set a different value for each language, and if none is set, the “All languages” value will be used as default one." I don't see where I'm able to set 'a different value for each language'. What am I missing?

In the screenshot I see that the Publish box has a message that's set by this plugin, but I don't see any way to add another language.

On the README page you also mention this: "Then to set and contribute your option page, simply use the Polylang's language admin flags ui." I really tried to understand what this means, but I just don't. :) What do you mean by 'contribute'? What is the Polylang's language admin flags ui?

What happened instead

The content that was stored in the options page, wasn't shown on the front-end. Didn't matter which language I would select. I would expect that the default values of my options page would be shown, but that didn't happen. Also, since I wasn't able to add any other languages, I didn't see the values for the other languages I would like to add.

The only 'strange' thing about my setup is that I'm using Timber and that I named my options page differently. Don't expect that to have anything to do with it, but I might as well name it.

Version information

• Plugin version : dev-master
• PHP : 7.3.3
• WordPress : 5.2.1
• ACF version : 5.8.0
• Polylang version : 2.5.4

You chose the locale field from Polylang to distinguish option keys (eg. options_fr_FR_my_key, options_en_US_my_key, etc.). The problem is that you can store multiple languages with the same locale whereas you can't with the same slug. Polylang forbids it.

Polylang isn't always used in a multilingual site. It can be used for a multi country site (you could have the same locale for two or more countries and not necessarily use sub locale).

This is of course quite an edge case issue but I think it's worth to be noticed and should be fixed in a future major release because it would introduce a BC issue.

I am a little bit confused, I hope you can help...

We used to use WPML but converted to Polylang. All OK except the Options fields were not showing the other languages in the Admin or on the front end.

So we installed this plugin. The other languages are showing the options fields on the site now, all the values we added when we used WPML.

But in the backend, if I switch to other languages, it shows the English/default for the languages. I tried changing one of them in the German language but this did not change on the german site. It still showed the original german field we entered when using WLML.

Actually I then went to change the default US language and that did not change.

So the front end is showing the correct option fields we added when using WPML. But the backend does not seem to work. It shows original US fields, but changing them does nothing.

Its quite strange!

Quand on est dans un choix de langue (anglais ou français) ça enregistre bien comme il faut
mais quand on est sur "Show all languages" la fonction sauvegarde n'est pas active.
"Toutes langues" les données sont bonnes mais quand on modifie une langue et qu'on sauvegarde, ça sauvegarde les deux

Prérequis :

• Monosite
• ACF 5.3.7
• Polylang gratos 1.9
• WP 4.5.2

We have PHP 5.4 and it seems to be working fine.

Version information

• Plugin version :
• PHP : 7.3.1
• WordPress : 5.0.3
• ACF version : 5.7.12 pro
• Polylang version : 2.5 pro

Hi, I also have a problem with using repeat, it turns out that the plugin takes into account the number of lines added to the repeater and, depending on the number of fields fills all languages with empty values of other fields, here is a video problem : https://cloud.mail.ru/public/J3c7/cQi8FFPxu how to fix???

Version information

• Plugin version : 1.1.3
• PHP : 7.2.1
• WordPress : 4.9.8
• ACF version : 5.7.7
• Polylang version : 2.4

Steps to reproduce

1. Use WP object instead of a string, e.g. get_field('text', $post);

What was expected

It should get the field "text" from the $post provided.

What happened instead

Warning: strpos() expects parameter 1 to be string, object given in /Users/antonfuruholm/sandbox/Frilans/GRAND PUBLIC/Extend/website/wp-content/plugins/acf-options-for-polylang/classes/main.php on line 184

EDIT:
Sorry, for blank input it works. Problem is, that "address" field is array with empty values.
https://github.com/chrisgoddard/acf-address-map-field

EDIT2:

What about some check, if multidimensial array is empty?

	if ( ! is_null( $value ) ) {
		if ( is_array( $value ) ) {

            $empty = true;
            array_walk_recursive( $value, function ( $leaf ) use ( &$empty ) {
                if ( $leaf === [] || $leaf === '' )
                    return;

                $empty = false;
            });

            if ( ! $empty )
            	return $value;

		} else {
			if ( "" !== $value ) {
				// Not an empty string
				return $value;
			}
		}
	}

For me, this code change works great :)

Hi, I have option page with several inputs

address - it is global field in all languages
text_* field, which is unique in different languges

I have two languages :
english - primary
svedish

If I switch to language (not "Show all languages") and save, in database there is empty value

options_en_US_address

on frontend in en_US language address is empty, which is problem.

So, it is possible check, if value is empty string and is not "Show all langues", then dont store to database, .

Workaround is several "options" page for, "global" with address,etc. and another page for text string. But if client switch to another language and save on "global" page with not filled input, there is same problem.

Thanks

Version information

• Plugin version : latest
• PHP :latest
• WordPress : latest
• ACF version : latest
• Polylang version : latest

Steps to reproduce

When calling get_options('name', 'options') from the REST API the old options page is returned, and not the new one. It looks like the filters is not being applied in the REST API

What was expected

New options should be returned

What happened instead

Old options was returned

Hi @MaximeCulea and thanks very much for developing this plugin. Very nice.

Let's say I have:

• A site with two languages: EN and ES.
• One translated ACF field which displays when Options Page is My Options Page

Result seems to be that:

• All Languages version of My Options Page displays both Fields, with data from most recently updated one of them
• ES version of the page shows ES data
• EN shows the EN data
• Front End ignores the All Languages versions of the others are populated, and pulls from the i10n ones.

If this is the expected behavior, I would like to update the README as along the lines of:

HOW?

This plugin creates an additional Options Page field for each field for which there is a translation and displays these fields in the front end instead of the All Languages value for that field. Localized (regional) Options Pages are accessed via the Polylang Admin Flags UI ("Show All Languages") Filter in the WP Admin Bar. The values for the fields will still be stored in the database (as well as displayed in the view of the Options Page), but they will only be displayed in the front end if Localized values are not set.

I think that might be a little clearer than what is there now.

Version information

• Plugin version : 1.1.5
• PHP : 7.1
• WordPress : 5.0.3
• ACF version : 5.7.10
• Polylang version : 2.5.2

Steps to reproduce

1. Install Plugin
2. Activated Plugin
3. Go to languages -> settings

What was expected

Field Groups

What happened instead

Has that something to do with my wordpress version. Cause you write "Tested up to 4.9.4"?
I just follow this steps.

https://polylang.pro/doc/working-with-acf-pro/

Best Regards

In an English / French WordPress install, English being the default language, I have an ACF repeater field on an option page with items (rows) set for All languages and no items for French. On normal page display when I use get_field I get the default All languages items. But when I use get_field during an Ajax request, I get no items.

Looking at the code of acf-options-for-polylang, the get_default_value (in classes/main.php:78) is indeed returning immediately if is_admin() is true, which is the case during an Ajax request. By replacing the first three lines of this function with following code I seem to obtain the needed behavior:

if ( (!acf_is_ajax() && is_admin()) || ! Helpers::is_option_page( $post_id ) ) {
    return $value;
}

It’s only a test. I’m absolutely not implying that this change is the way to do it.

Version information

• Plugin version : 1.1.7
• PHP : 7.4
• WordPress : 5.5.1
• ACF version : 5.9.1
• Polylang version : Polylang Pro 2.8.2

Steps to reproduce

Having an English / French WordPress install with an option page. English being default.

1. Add a repeater field on an option page
2. Add values to that field for All languages and keep it empty for a French.
3. Display field rows on any French page : it’s OK
4. Get field value in an Ajax request from any French page : retrieved value is empty

What was expected

I’m expecting the same value from my field during normal page display and during an Ajax request.

What happened instead

I got French empty value during Ajax request, instead of default All languages value.

At beginning, check if the mode is get "All languages" instead.

At the same time, rename the func, because it's not a setter, but more a getter.

Version information

• Plugin version: 1.1.6 (dev-master)
• PHP: 7.2.13
• WordPress: 5.1.1
• ACF version: 5.7.13
• Polylang version: Polylang Pro 2.5.3

Steps to reproduce

1. Activate addon
2. Go to front page
3. See empty page

What was expected

Front page fields to be visible.

What happened instead

Front page is empty (the styles load up but no content).

This plugin should not affect normal pages, right? My front page fields are set to be displayed if page type is same as front page (that is selected in general settings) and I have only one repeater on front page.

When var_dumping the field, it returns a string (id, perhaps?). How to proceed?

Version information

• Plugin version : 1.1.7
• PHP : 7.4.5
• WordPress : 5.4.1
• ACF version : 5.8.11 (Pro, installed within Theme)
• Polylang version : 2.7.2 (Pro)

Steps to reproduce

1. ACF Pro is installed within my Themes, as none of my Themes work without it. The installation is done like this: https://www.advancedcustomfields.com/resources/including-acf-within-a-plugin-or-theme/
2. Polylang Pro is installed regularly
3. When trying to activate I get the following error: Advanced Custom Fields and Polylang are required plugins.

What was expected

All requirements are be matched, so the plugin should activate without any errors.

What happened instead

Error Advanced Custom Fields and Polylang are required plugins. is thrown in classes/requirements.php
I guess that the requirements are not properly checked.

I will fork this for my own use to solve the issue. Interested in any tipps on how to solve!