funkjedi / acf-qtranslate Goto Github PK

Since qtranslate doesn't work with WP 3.9 I had to switch to the fork mqtranslate, which does work. But then acf-qtranslate doesn't work anymore... Can it be fixed?
Thanks in advance

Hello again,

When I use "Enable translation for Standard Field Types" and use default ACF WYSIWYG in repeater field everythings works fine. But when I use qtranslate WYSIWYG then "magic" appears: they're always problem with save more than 1 language in one field at once. After that:

• in all languages in admin see all content - sometimes with [:lang1]content1[:lang2]content2[:], sometimes without
• it's saved as we saw it but sometimes it still works in frontend (when we see a [:lang] braces) and sometimes it saved all data for all langage
• sometimes in frontend I see "(myNameOfUsedLanguage)" at start of content of first content item, eg.
  (čeština) content2content3content1

Unfortunatelly as I say previously It'll be nice to use normal and qTranslate text fields in one Wordpress ;)

Wordpres: 4.2.2
ACF: 4.4.1
Repeater: 1.1.1
qTranslate-X: 3.3
ACF: qTranslate: 1.7.9

Hi,

Image fields are not saved (empty on refresh)

Post request seems ok (example using only DE)

fields[field_53fe04c112554][0][field_555de2cdde174][de]:1402
fields[field_53fe04c112554][0][field_555de2cdde174][en]:
fields[field_53fe04c112554][0][field_555de2cdde174][it]:

But values are not saved ( field_555de2cdde174 is not present in *_postmeta table )

ACF 4.4.2
ACF qTranslate: 1.7.9
qTranslate-X: 3.3
Wordpress: 4.2.2

Any idea?

Tnx

I using WP 4.2.4, qTranslate-X 3.4.3, ACF Pro 5.2.8 and ACF qTranslate 1.7.9 and on post/page edit page I get an error on console

TypeError: undefined is not a function (evaluating 'qTranslateConfig.qtx.addContentHooksTinyMCE()')

for acf-qtranslate/assets/acf_5/qtranslatex.js line 77.

Any Idea what causes this error?

Thanks
Thomas

Hi,

this is a great plugin, thank you really much !

However, I still got an issue with qTranslate X, using Repeater fields : translation is just not effective on those fields (and fields within). Any suggestions ?

Notice: Undefined index: qtrans_hook_on_tinyMCE in /wp-content/plugins/acf-qtranslate/acf-qtranslate.php on line 60 Notice: Undefined index: qtrans_hook_on_tinyMCE in /wp-content/plugins/acf-qtranslate/acf-qtranslate.php on line 61

because of this html only mode in tinymce editor.

WP 4.2.2
ACF Pro 5.2.6
ACF Qtranslate 1.7.9
qTranslate-X 3.3

hello. cann't save values on ACF options page (for qtranslate text field & qtranslate wysiwyg), also have problems with saving repeater with the same fields.

Can you help me?

First off - this plugin is absolutely gorgeous - and thank you. But as mentioned on the ACF old.forum, there is the one little bug for the WYSIWYG content. It overwrites anything in the native WP content editor. Just wanted to post it here, as this area seemed more active than over there.

Again - thanks. And let me know where I can find the tip jar.

Hi,

When Editing acf qtranslate editor field of one language with some content and click update then its updating default editor content also.

Please suggest asap.

Thank you!

First thanks for your work on this plugin !

I'm using WP 3.9.2, ACF v5, mqTranslate 2.6.7 (with acf-qtranslate obviously!).

Fields and Text Areas seem to work great, even within repeater loops etc.

However, the WYSIWYG is appears to be unusable. After saving the content the text from each field gets somehow merged to one.

Example:
english: Hello
espanol: Olà

becomes:
english: HelloOlà
espanol: HelloOlà

I'm having a problem where my WYSIWYG editor does not switch languages when using the standard field, and Enable translation for Standard Field Types is enabled.

When using the ACF field, saving or updating the post empties it.

qTransx - 3.3
ACF - 5.2.5
ACF qTranslate - 1.7.9

As a side note, I know it's not easy to stay on top of things all the time, but is it possible to update the readme with the latest known working configurations?

i have an ACF in a taxonomy (or category, the same)
and qtranslate does not apply to that ACF field, it only sves one language,
i am speaking of an ACF data-field_type="wysiwyg"
and i understand it could be because ACF in taxonomies are called later in AJAX
but i don't know how to solve this problem.

please help :) i have complex taxonomies with advanced desctiption in wysiwyg textareas that i need to transalte.

ty

Marco

It made repeater completely useless because everything would get destroyed inside it. Also, can you please add support for disabling translation for the default ACF text field?

I've looked through the threads and seen the fixes for these but none of them seem to be working for me. I'll edit both fields and click the update button and whatever language i left off with is what takes over both languages. One thing i do notice is that every once in awhile of updating the page, I get errors and am wondering if that could be the culprit. Any help is very appreciated. Thank you in advance. here they are:

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Invalid argument supplied for foreach() in /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php on line 14

Warning: Cannot modify header information - headers already sent by (output started at /home/nerd/public_html/campt/wp-content/plugins/qtranslate-x/admin/qtx_admin.php:14) in /home/nerd/public_html/campt/wp-includes/pluggable.php on line 1207

Hi there Funkjedi,

The plugin (very helpfully for the most part) applies the filter before the value is returned to the template using get_field(). Indeed, this is the core of the plugin!

However, in certain circumstances, I'd like to be able to control how the field is returned to the template. For instance, qTranslate-x provides the following functions to control how a given request is handled if the requested language isn't found:

qtranxf_useCurrentLanguageIfNotFoundShowEmpty() qtranxf_useCurrentLanguageIfNotFoundShowAvailable() qtranxf_useCurrentLanguageIfNotFoundUseDefaultLanguage()

However, the plugin always bakes in qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage().

I'd like to be able to either set my return preferences for the field, or better yet, have the option to return the raw field content – which would then allow the developer to pass the returned raw content through the qtranxf_useCurrentLanguageIfNotFound function of his/her choosing.

Any thoughts on how to do this?

Cheers,

Andrew

Hello,

Thanks for this plugin. It's exactly what we need!

On Wordpress 3.8.1, the labels & language selection tabs on textareas overlap the textarea content. I am not sure if this happens on any previous version of Wordpress. I added the following CSS overrides to accommodate this problem,

.multi-language-field { 
  margin-top: 0px;
}
.repeater .multi-language-field { 
  margin-top: 32px;
}
.multi-language-field .wp-switch-editor {
    top: -32px;
}

I'm not submitting a pull request because I'm not familiar with how this would affect other versions of Wordpress. I trust Mr. funkjedi will know what is best.

When I add items to other language in ACF, when I use Custom Post UI, and update the post, only English shows up in the posts table language column. I would like other languages to show up there too if possible.

i use the following relevant plugins:
Advanced Custom Fields (4.4.1)
Advanced Custom Fields: qTranslate (1.7.6)
qTranslate-X (3.2.9)

i have a custom post type called films with custom fields for two languages english and german. the custom fields are using the qTranslate field type.

i have a problem when editing one language of a field and then updating it. for instance i have the field Titel. initially for english it contains AlmaEN (http://i.imgur.com/UzlSB8U.png) and for german it contains AlmaDE (see: http://i.imgur.com/bk5joTi.png). if i edit the english version to AlmaEN2 and hit update, a strange thing happens: the german-version of the field gets appended the old value of the english field, i.e., AlmaEN. the english version updates as expected. see this screenshot for the resulting values of both fields. the deutsch/german version contains the strange value: http://i.imgur.com/bVCgquN.png

i dont know much about the internals of these plugins, so i have no idea why/where this happens.

i would love to have this fixed, because it makes editing the multilanguage custom fields really tedious...

please note that i also made this change: https://wordpress.org/support/topic/language-switcher-for-custom-fields?replies=3

thanks!

The WYSIWYG field for ACF 4 loads all languages values when editing in the admin area, because it sends the whole field value (without using the value for each language). Here is the area of the code with the problem ($field['value'] contains the string with all languages, $value contains the string with the value for the language on the loop, please check the value inside of the text area):

And here is the fix:

I use the following plugins:
Advanced Custom Fields (4.4.1)
Advanced Custom Fields: qTranslate (1.7.6)
qTranslate-X (3.2.9)

Some buttons are missing in acf wysiwyg. There is no link button and some others are missing too.

thanks!

It's showing "Uncaught SyntaxError: Unexpected token <" when I put my site on my nginx server ( but normal in my local Apache server ).

When I changed this code block:

<script>
var acf_qtranslate_translate_standard_field_types = <?= json_encode($translate_standard_field_types) ?>;
</script>

to:

<script>
var acf_qtranslate_translate_standard_field_types = "1";
</script>

it seem worked, but I do not know where is the problem. Would you help me? thanks.

Advanced Custom Fields : Version 4.4.2
Advanced Custom Fields: qTranslate : Version 1.7.9
qTranslate-X : Version 3.3.1

RATIONALE:

It checks for ACF presence in response to 'plugins_loaded' action..
that check get executed before the theme (and subsequently ACF) get loaded

A SOLUTION PROPOSAL:

Could be to make your plugin embeddable in theme too but:

• requires the main initialization routine to be called later than 'plugins loaded'
• requires to update all 'wp_enqueue_script' occurrences that now are making use of 'plugins_url' API
• cannot be updated anymore
• is allowed to include your plugin in a theme?

Thanks for your attention

Unfortunately these fields aren't saving for me, the field is empty upon updating/saving.

I've tried:

Standard ACF text, textarea - only shows one language, does not switch. This saves the one language.
ACF qTranslate text, textarea - switches languages, does not save, empty on save/publish.

Can't seem to see any errors in js console in either case.

Using Wordpress 4.2.2, ACF 5 Pro 5.2.5, qTranslate-x 3.3, ACF qTranslate 1.7.9

Hi again

When i'm creating an Advanced Custom field group i'm easily able to give a group name in every language i'm supporting... but I can't find a way to give different labels and instructions to the fields themselves... When en switch between flags/languages, only the field group name is getting internationalised, everything else stays the same.

I want to create a field with a label "Case study type" inside a "Case Study" field group. Then I want to change that label according to the user language, for example "Estudo de caso" in Portuguese. I want to do this with all the other stuff like Field Instructions and Options (if the field type is a select box).

Is this already possible? Can someone help me?

I've been using qtranxf_getLanguage() to get the current language within ajax calls for some time and it's been working fine.

The client updated the wordpress core to 4.2.2 and now that function isn't working within ajax calls although it is functioning normally otherwise.

I've tried versions from 2.9.6 - 3.3 of qtranslatex with the same problem.

Has anyone experienced this and/or know of a fix?

Cheers

I updated to the latest version of acf-qtranslate but i got an issue, i have all the content from both languages {FR,EN} in the same area in both langauges tab (duplicated content second languages area clone text from the first language )

Any fix...please

Will there be an update for the new ACF Version 5?

Thanks
Thomas

Hi,

Please do help to fix the ACF qtranslate for WP 4.3.1, since I upgrade to WP 4.3.1, I could not publish the post, only can save draft, and when activate the acf qtranslate, my homepage cannot load properly.

Thanks

The new release is much improved, thank you so much for your work!

I report some bugs:

1. In the post editing screen (post, page and every custom post type) there is this notice:
   Notice</b>: Undefined variable: args in <b>/Applications/MAMP/htdocs/wp/wp-content/plugins/acf-qtranslate/src/acf_5/acf.php</b> on line <b>113

In the offending line perhaps we need to change acf_get_field_groups ($ args) to acf_get_field_groups ($ filter)
so the ACF fields used in the screen are correctly filtered.

2. In addition, on the first loading of the edit page, the (hidden) switch-editor of acf-qtranslate fields is set to the wrong language, if the current language (stored in the administrator session) is different from the default.

3. Inside Flexible Content or Repeater, the wysiwyg editor does not save the content in any language, however the text and plain textarea field work properly

Wordpress 4.1.1
Qtranslate-X 3.2
ACF Pro 5.1.9.1
ACF qTranslate 1.7.1

I'm having a somewhat mind boggling problem with my WYSIWYG editor, in combination with qtranslateX.

I'm not sure where the issue lies as:

ACF WYSIWYG field is fine with qtranslate-x disabled
Normal 'Content Editor' WYSIWYG field is fine with q-translate-x enabled

With qtranslate-x enabled, any ACF WYSIWYG fields are always adding a:

<p>
&nbsp;
<br/>
</p>

At the top of a post if the first element is a block element such as a header (h1, h2 etc...)

Screencast: http://d.pr/v/1eugP/5VFFUkQ3

I don't know where to begin, I've tried so many combinations of the three plugins (ACF Pro, ACF qTranslate, qtranslate-x), every combination yields some broken functionality, and so far the current combination I've found is the only one that even works in the basic respect of saving and updating data.

qTranslate-x 3.3
ACF 5.2.3 (translation broken unless using this version)
acf-qtranslate 1.7.6 (translation broken unless using this version)
Wordpress 4.2.2

Links to respective issues:

qtranslate-x: qTranslate-Team/qtranslate-x#167
ACF: http://support.advancedcustomfields.com/forums/topic/paragraph-inserted-at-top-of-wysiwyg-fields-if-first-element-is-block/edit/

It works everywhere except inside the repeater field.

Hello, I can't use ACF PRO with qTranslate-X.

I have this plugin installed:
ACF PRO version 5.2.3
qTranslate-X version 3.3
ACF qTranslate version 1.7.6

The problem incurred when using a repeater. When save post with a repeater field page returns follow error.
If I use ACF normal, not PRO, with the same other plugins, all work properly.

Anyone can help me?

Warning: Illegal string offset 'field_5548b2b971eab' in /Users/cr/wp-content/plugins/qtranslate-x/admin/qtx_configuration.php on line 37

Warning: Illegal string offset 'en' in /Users/rocco/Dropbox/cr/wp-content/plugins/qtranslate-x/admin/qtx_configuration.php on line 37

Warning: Illegal string offset 'it' in /Users/cr/wp-content/plugins/qtranslate-x/admin/qtx_configuration.php on line 37

Warning: Cannot modify header information - headers already sent by (output started at /Users/rocco/Dropbox/localhost/cinemaritrovato/wp-content/plugins/qtranslate-x/admin/qtx_configuration.php:37) in /Users/cr/wp-includes/pluggable.php on line 1196.

Hi,

I'm working with the plugin on a theme which uses ACF to make it bilingual. It seems to work in most cases but just some times it doesn't display content or it seems to be blocked.

German is the first language. everything works fine: http://movanext.com/de/
English the second; Home seems blocked by a big white space? (http://movanext.com/en) and the columns show up smaller than selected in the backend; (http://movanext.com/en/movanext-lux-plus/)

What can I do to resolve this problem?

Rens.

I ran into a pretty obscure issue with this combined with qtranslate. Attempting to get the text aligned right to left instead of left to right. When it comes to the textareas and input fields this is a simple CSS fix, but when it comes to the WYSIWYG editors, they are switched back and forth by (if i understand correctly) replacing an iframe and its content. I was running into some issues accesing that content to edit it so i had to change your plugin a bit. My changes are below, hopefully they make sense:

jQuery(function($) {


    $('body').on('click', '.wp-switch-editor[data-language]', function() {
        var parent = $(this).parent('.multi-language-field'), language = $(this).data('language');
        // start of changes
        if(language == 'ar'){
            var $iframe = parent.find('iframe').contents();
            $iframe.find('p').css({'direction': 'rtl'});
            parent.find('iframe').contents($iframe.html());
        } else {
            var $iframe = parent.find('iframe').contents();
            $iframe.find('p').css({'direction': 'ltr'});
            parent.find('iframe').contents($iframe.html());
        }
        // end of changes
        parent.find('.current-language').removeClass('current-language');
        parent.find('[data-language="' + language + '"]').addClass('current-language');
        parent.find('input[data-language="' + language + '"], textarea[data-language="' + language + '"]').focus();
    });

    $('body').on('focusin', '.multi-language-field input, .multi-language-field textarea', function() {
        $(this).parent('.multi-language-field').addClass('focused');
    });

    $('body').on('focusout', '.multi-language-field input, .multi-language-field textarea', function() {
        $(this).parent('.multi-language-field').removeClass('focused');
    });


});

Is there a workaround for this? I can't get any fields, even the acf qtranslate fields to input multiple languages in ACF's theme options

Hi all,

I'm facing the issue on WYSIWYG content field on switching after saved the post. It's ok to switch and save the post, but after reload/edit, it just show the content from the first active tab.

I Found that it saved the content correctly, but just not showing right. (Attached image)

I'm using :

W.P 4.2.2
qTranslate-X 3.3
ACF Pro 5.2.7
ACF qTranslate 1.7.9

When i disabled the ACF qTranslate, that fields already working fine which the translation (maybe because of the qTranslate-X or ACF 5 updated). But i still need to use ACF qTranslate for other purpose, so i tried to fix it by: comment out the line 42 of the file /assets/acf_5/qtranslatex.js: qTranslateConfig.qtx.removeContentHook(this);

It's working fine for now but i dont know if it will affect other functions?

Regards,
Spirit.

I run both plugins and my Media page is empty even if Im still able to upload images (from both the page itself and posts and pages) and the images I had uploaded earlier still work.

Do you have any idea?

If I disable one of the 2 plugins the problem is solved

Hi there!

Everything seems to work fine ( textfields ) but the ACF WYSIWIG field doesn't. It is the same content for English, German and Chinese for example. Is it something you guys are still working on or should I update to ACF5?

Looking forward hearing from you and keep up the good work!
Yordi

Hi,

I discovered your plugin for translating the ACF fields with qTranslateX, and tried to used it on a website I'm working on right now.

The problem I have is that instead of displaying each version of the fields in tabs for each language, they're displayed one below the other, and if I save, all the content for all languages is displayed together on the page.

I'm not seeing any javascript or warning/notice, so I can't really give your directions. I'm using ACF 4.4 and WP 4.1.

Greetings!

I am using the following:
acf-qtranslate v1.7.9
advanced-custom-fields v 4.4.1
qtranslate-x v3.3

Most fields seem to work fine. My main problem is the wysiwyg field.

If I use the "standard" field translation, the WYSIWYG field is loaded with the content from the current language, but no others. Switching the language works, but all languages are defaulted to whatever the language is when I load the page. Example: If I load the page in English, the english field value is used for all languages. If I load in chinese, chinese field value is used for all languages.

If I don't use the "standard" field translation and add the language tabs, I get all languages displayed in the wysiwyg field. If I add the content and switch the language tab, it transfers the new content correctly. However, existing content for all languages is loaded in every languages box.

Have you seen an issue like this or any ideas on where I should debug first? If it helps, I semi-recently migrated from mqtranslate to qtranslate-x, so these fields are currently stored with <!--:--> tags instead of the new [:].

Thanks!

This is less of an issue and more of an FYI - the .php file still has the version listed as 1.2.0, so WordPress always complains that it needs updating.

Hello,

First of all thanks for the great work in building this plugin. It has been extremely useful and I couldn't do without it.

I recently switched for qtranslate to mqtranslate for compatibility with Wordpress 3.9.1. I have WP_DEBUG enabled for testing purposes and noticed the following lines in the admin panel after making the switch:

Notice: Undefined index: js in /home2/mathlabt/public_html/wp-content/plugins/acf-qtranslate/acf-qtranslate.php on line 54

Notice: Undefined index: qtrans_hook_on_tinyMCE in /home2/mathlabt/public_html/wp-content/plugins/acf-qtranslate/acf-qtranslate.php on line 60

Everything seems to work fine nonetheless.. but the warnings are pushing the overall UI down and distorts the page, just wondering if it could be an easy fix?

Thanks again for the great job!

Best,
Allen

Hi!

I'm having some issues with this plugin and Custom Post Type when Wordpress debug mode is active. I'm getting this error when accessing any of the CPT menus on Wordpress:
"Trying to get property of non-object in /Applications/MAMP/htdocs/wp_tourism360/wp-content/plugins/acf-qtranslate/src/acf_4/acf.php on line 152"

Am I the only one? Can anyone help me?

Best regards,
Bruno Garcia

I've tested a few of the ACF fields and the WYSIWYG is not possible to translate!

If I have acf qTranslate (ver 1.7.6, also tested 1.7.9) plugin activated and iOS9 Safari/Chrome won't load the page. Whenever I deactivate the plugin, the site will load but the translations won't work.

Instead will give this error: https://www.dropbox.com/s/ulqq8zw0x43zjgb/IMG_0006.PNG?dl=0

Solution?

Hi funkjedi,
first of all thanks for a great plugin works really well for me....
But there is one issue, I can't get the function "Enable user-level language protection" (mqtranslate) to work with ACF fields? Any ideas how to get this working, works fine when acf-qtranslate is turned off!?

e.g. I want to make so german editor ...only can edit the german language etc.
Maybe you can help me out?
Best regards

Hi,

I am seeing this strange issue with ACF Option pages (Even with new install). When I create a qTranslatex field, the tabs look weird and the title gets cut off (CSS), but if I add another field (specially IMAGE), everything looks good.

Thanks.

WP: 4.4
Total Plugins:
ACFPRO: 5.3.2.2
ACFQTranslate: 1.7.9
QTranslateX: 3.4.6.4

In edit screen, some custom fields have their labels and language-switch buttons misplaced (within the field, over the content). This only happens on Firefox. Works fine on Chrome.