Support

Account

Register Login

Home › Forums › Search › Search Results for 'WPML'

Search Results for 'WPML'

reply

  • Has this been fixed now as it is something I am going to need to do for a project I have just started work on?

    Are there any other known problems with using WPML and ACF as I am really nervous to use them together, but cant think of any other way I want to do it.

  • Ah-ha! I’ve discovered that this is a problem with WPML – if WPML is enabled, ACF neither reads from JSON, nor offers the ‘Sync Available’ option. @elliot and team, would you like to look at this further, or should I raise it with WPML?

    For anyone else with this problem, you can temporarily disable WPML, do a sync and then re-enable it.

    Cheers,

    Andrew

  • I have the same problem, but with Russian language.
    After half of hour looking i found why is it translating:

    foreach( array('label', 'instructions') as $s ) {
		
		$field[ $s ] = __($field[ $s ]);
		
	}

    in acf_get_valid_field function, wich is called when field is loaded to the metabox or acf form

    Aldought it’s good that field can be translated, but it misses the important parametr – textdomain and less important – context.

    If there could be something like these:

    $field[ $s ] = __($field[ $s ], apply_filters( 'acf/translation/textdomain', 'acf-translation', $field[ $s ], $s ) );

    It would be much more effective and wouldn’t cost so much problems!
    Aldought i’m no shoure that with Code Style Localization or wpml you would be able to find and collect all transatable strings ( becouse they are variables, and variables can’t be writen or readen from gettext ).
    As one of posible solutions threre could be an exit:
    for example add a function wich will check the php file and find the string in it, and if it doasn’t have it, then write new _x( ‘$var’, ‘context’, ‘textdomain’ ); string to it ( that’s the only, known by me, way to achive these ).

  • Thanks for this JoepR! I tried the same approach but didn’t know the right ACF filter.

    I agree with the concerns here. I also have an issue with the new ACF version that Options now have to be translated or else return null. It breaks websites.
    Yes you can add in translated options, but most of the time translation is the same and there’s no way to duplicate. I have sites with many many options, it takes a lot of time to reinsert everything, and the customers don’t understand the logic at all.

    I tried setting the CMS to ‘All Languages’ in the admin bar, inserted all options, but sadly this doesn’t work either.

    The filter workaround works, but it’s ugly. This should have been be though through better before making such a release.

    I’ve been trying to get an answer from support for over a month but the last reply was the I should contact WPML…

  • Same issue for me.

    ACF backend always in frech : even if i switched language in “Profile” section or WPML admin language.

  • Hi,

    I have the same problem with ACF 5.1.5 and WPML 3.1.8.4.
    As pointed out by brian1037, I’d rather avoid to translate in more than 5 languages prices, dates and other numerical data or tables.

    I used Option fields just to fill in these fields only once for the whole website.

    But now I have all these fields empty in languages different from default.
    Hope it could be fixed soon,
    thanks

    Davide

  • Thanks Robby, but I am not using WPML. From my research it looks like it is saving “all” as the taxonomy when none are selected but nothing is returned since it isn’t a real taxonomy.

    I do have some special cases in my setup – specifically I’m using a wrapper field type on some ACF fields – but for me I was able to get around the problem by adding a filter on load_field.

    if ( $field['taxonomy'][0] == 'all' ){
	unset( $field['taxonomy']);
}

  • I must be missing something because I’m still getting the original “not saving” issue. Using ACF Pro 5.1.3, WPML Multilingual CMS 3.1.8.3 and WPML Translation Management 1.9.8

    Tried: “We had to check
    – “Translate” for “Fields Group” and
    – “Do nothing” for “Fields”

    … but still no success.

    Any suggestions?

  • Hi,

    Not sure about Issue #1, but I’m definitely having the same problems with Issue #2 and #3.

    I just cannot get the fields to save the additional languages. Saving the primary English values is fine, but never saves for the extra languages I require.

    Tabs go all funny as described above too.

    I’ve read through the instruction article (http://www.advancedcustomfields.com/resources/multilingual-custom-fields/) too, and still can’t get it to work

    Would love this to be rectified ASAP…

    Using:
    WordPress 4.0.1
    ACF Pro 5.1.3
    WPML Multilingual CMS 3.1.8.3
    WPML Translation Management 1.9.8

  • Hi Jsilver,

    Do you use ACF in combination with WPML for your project? If so, I might be able to help you.

    I found out the problem for me was that I set my WP lang. to nl_NL (Dutch), my default WPML was English and my strings were Dutch.. WPML bugged on that and this gave lots of conflicts. ( fairly new to WPML )

    After doing a complete removal of WPML and re-setting everything, it worked flawlessly.

    Robby

  • On second review, you might be facing a field translation problem.

    Reading material:
    http://support.advancedcustomfields.com/forums/topic/wpml-dont-save-custom-fields/
    http://www.advancedcustomfields.com/resources/multilingual-custom-fields/

  • This topic can be closed, 5.0.8 fixed the problem, except for 1 of my projects. It seems like WPML gave some problems, I cleared my db of WPML tables and reinstalled it.. everything works ok now!

    Robby

  • i updated WPML Multilingual CMS to the Version 3.1.8.2, and the WPML Translation Management to the Version 1.9.7, and the ACF Field Groups where working fine with the translations. i think this means that this issue is resolved.

  • Just finished writing this article:

    http://www.advancedcustomfields.com/resources/multilingual-custom-fields/

    Please let me know if it is helpful or can be improved in any way.

    Thanks for the article, a few questions:

    1. Which (exact) version of WPML did you use?
    2. Is the article valid for ACF 4 and/or for ACF PRO 5?
    3. Do fields still save and is selecting the post type translation still possible after you enable any other plugins or switch themes (doesn’t matter which) after the ACF setup?

  • I been using ACF and WPML and Woocommerce for a long time with very complex ACF and language setup. I Just installed the ACF PRO and this become Changed:

    The “Duplicate” of a ACF is no longer dublicated, it creates a translated independent copy of the original language field setup. Before you could see the WPML box “Make xxx fieldgroup independent” (WPML will no longer sync…)

    Today, if we add changes in the Field group, we must add the “new” fields in that fieldgroup, values, etc etc manually for EACH translated field group. Not fun when using 10 languages.

    On the other hand, To make headlines, titles translated, the field group MUST released as a “duplicate” and become independent. (As before)

    We always keep the fieldgroups as “dublicated” (But now ACF cant do it) as long as possible, and when all testing and the client is happy, we release all translations and finally, translate the labels and titles.

    ALSO:
    REF Elliots article “Multilingual Custom Fields”

    in WPML “Mulitilingual setup — Custom fields translation”, These properties (Custom fields) has to be checked as “Copy from original to translation”:

    -allorany
    -field_1
    -hide_on_screen
    -layout
    -position
    -rule

    Then, everything works fine for us, as for many installs, last 3 years, update after update WPML + ACF.

  • Thanks a HUGE lot for that article. I’m sure this will take away a lot of frustration I’m having with WPML. Thanks!

  • Hey guys.

    I’ve just put together a bit of a guide for WPML. Can you please give it a read and let me know if it helps?

    http://www.advancedcustomfields.com/resources/multilingual-custom-fields/

    Thanks
    E

  • Hi Guys

    It seems like there are 2 things which are causing WPML issues. I will write up a guide in the docs to help future users:

    1. The “Field Groups” must be enabled for translation, and a field group must exist for each language.
    2. When editing a post, make sure all custom fields in the ‘Multilingual Content Setup’ metabox are set to ‘Translate’ and not ‘Copy’, otherwise the values will not be updated.

    Hope his helps,

    All WPML tests seems to be working great on my end.

  • In WPML I set the ‘field groups’ to translate. Then you translate the field group in ACF (just duplicate or copy). You don’t have to change anything, they just need to be translated.

    Which versions of WPML and ACF do you use?

    I can take a look at your settings if you want.

  • It seems to be a problem caused by WPML conflicts again, doing the trick as suggested here: http://support.advancedcustomfields.com/forums/topic/acf-not-playing-nice-with-wpml/
    it seems to fix. When will we see a stable version? 🙂

  • The WPML support said today:

    ACF is not currently compatible.

    And you should “hack” the database to fix it.

    http://wpml.org/forums/topic/wpml-3-1-8-1-field-groups-not-translatable-acf-now-working/#post-498588

    Draw your own conclusions…

    Edit: The technical background is explained here:

    http://wpml.org/forums/topic/broken-acf-languages-after-activate-plugin/page/3/#post-493055

    Summary: WPML 3.1.7+ downloads a remote config from WPML server which currently tells WPML that ACF can not be translated. The update of this remote config is triggered at every after_switch_theme and activated_plugin wordpress action and at custom wpml-actions.

  • I updated WPML Multilingual CMS to the new Version 3.1.8.1, and WPML Translation Management to the new Version 1.9.7. The problem continues.

  • Thanks for the link, that “special” remote config for “acf” in latest WPML is actually very interesting…

  • Question is:
    should “group fields” be translatable in wpml options ?
    If i fix “group fields” not translatble it works but then… how can i translate field labels ?

  • these instructions fixed the problem temporarily.

Viewing 25 results - 276 through 300 (of 495 total)
1 2 3 … 11 12 13 … 18 19 20