Hi guys, i’ve installed ACF v5 PRO and i created around 10 custom fields group, after that i had to set a qTranslate text field and i noticed that i can’t see them anymore on the custom field list, i tried to rollback to v4 and qTranslate fields shows up, the problem is that i can’t rollback to v4 because my fields group were made with v5 and i can’t see them with v4, is there a quick fix to have qTranslate ACF fields with v5 or a way to import the json (exported fields file) from v5 to v4 ?
It is not possible to downgrade the data from ACF PRO to ACF4, however it is possible to use the export to PHP feature as both ACF PRO adn ACF4 use the same code format.
As for the original question, I’m not sure I understand what is going wrong.
What do you mean by
set a qTranslate text field?
I have tested qTranslate with ACF PRO and the ACF fields appeared on both languages. Perhaps you can include steps to replicate the issue?
I’m bumping into a similar problem. I have a page with a Repeater field from ACF. The Repeater field has two subfields, a qTranslate text field, and a qTranslate textarea field. When I try to save the post, it would not save, and shows “Connection Lost” error message.
I’m working with
Yup, ACF V5 PRO and ACF qTranslate wont play nice (at least with qTranslate Plus). Had to go back to ACF v4 so everything works good.
Won’t work: WP 4.1.1 + ACF PRO 126.96.36.199 + Advanced Custom Fields: qTranslate 1.4 + qTranslate Plus 2.7.2 inc. Patches
Works: WP 4.1.1 + ACF 4.4.0 + Advanced Custom Fields: qTranslate 1.4 + qTranslate Plus 2.7.2 inc. Patches
It looks like “ACF5PRO” is not recognising the new fields created by “Advanced Custom Fields: qTranslate 1.4”, so when you assign them and save your custom fields, they appear as regular ones. Then the editor will break apart silently.
Please let me know if this gets fixed, since ACF5PRO was playing great.
I still have a problem saving “file” fields. When “act qtranslate” plugin is active, the field just returns empty after saving. If the plugin is turned off, i can save the “file” field with no problems.
Any way we can solve this?
I would love it if i could choose in the plugin settings what custom fields i want to exclude from qtranslate. That would be an easy fix to my problem because i don’t need a file field translated anyway 🙂
EDIT: I just updated the q-translate-x plugin, and that has solved the problem. Because now you can exclude the act fields and post types you don’t want to translate . Perfect.
I am loving ACF5 and acf-qtranslate plugins thanks all involved.
I am having the same issue where the the repeater and even the flexable content – does not want to update when the post is saved – it renders blank.
I have the following versions and I am working on a local MAMP PRO installation.
Wordpress – (4.2.2)
ACF5 Pro: – (5.2.6)
acf-qtranslate: – (1.7.9)
qTranslate X – (3.3)
PHP – (5.6.7)
Chrome – (43.0.2357.124)
Anything I can try?
Thanks in Advance.
I am also facing the same issue. I was using ACF4. And, issue arises with fields in Repeater and Flexible fields. Then I upgraded to ACF Pro. Still issue was same. So, I changed a field from ACF-Qtranslate to Text, and it works fine.
My current environment:
– WordPress 4.2.2
– Advanced Custom Fields Pro 5.2.7
– qTranslate-X 3.3
– Advanced Custom Fields: qTranslate 1.7.9
Fields are still not saving.
Hello! I have problem with Wysiwyg Editor when I’m using WordPress 4.9.5 + ACF PRO (Version 5.6.10) + qTranslate-X (Version 188.8.131.52) + Advanced Custom Fields: qTranslate (Version 1.7.23).
If I choose tabs Visual $ Text in field settings:
On post/page edit page in Wysiwyg Editor I see the only tabs and not formatted text in text area, and no toolbars.
If I click on any tab, visual or text in Wysiwyg Editor the toolbars become visible.
If I choose single tab Visual OR Text in field settings:
On post/page edit page in Wysiwyg Editor I see the only not formatted text in text area, and no toolbars.
And if I’m trying to click somewhere on Wysiwyg Editor the toolbars are not appear.
I can send screen video 🙂
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
© 2022 Advanced Custom Fields.