acf-qtranslate No fields showing and Duplicate field options showing after updating

I am using wordpress 4.8, ACF Pro 5.6.0, and your plugin (v1.7.22). After updating the ACF pro plugin to v5.6.0 it seems your plugin is no longer compatible, I am experiencing some issues, the fields that I had translatable are no longer showing in the admin eg a text field, and when I go into the ACF field options to see what it says, it says 'unknown' for the field name and when I click edit all of the fields are duplicated, I can't even change the field back to just text unless I de-activate the plugin. Please find a screenshot here: https://www.dropbox.com/s/myuh5o2ru3mjqwd/screenshot1.jpg?dl=0 and https://www.dropbox.com/s/hpqk2o7mnvsc6bi/screenshot2.jpg?dl=0

I have tried re-installing ACF, re-installing ACF qTranslate, deleting the fields I made and re-making them but no luck.

Jul 25 '17 13:07 gab1982

I have same problem

Jul 26 '17 02:07 paulinhoerry

Can anyone help with this, its becoming an issue.

Jul 27 '17 08:07 gab1982

Same problem here...

Jul 27 '17 12:07 gfStudioTesta

This is a major issue, it's due to the new version of ACF.

rolling back to version 5.5.14 of ACF Pro fixes the issue temporarily

Jul 27 '17 13:07 Bones5

Yes rolling back is a solution. Hope to be not forced to migrate to hateful WPML 👎

Jul 27 '17 13:07 gfStudioTesta

How can I rolling back ACF PRO?

Jul 27 '17 13:07 paulinhoerry

Download version 5.5.14 from here https://www.advancedcustomfields.com/my-account/view-downloads/

delete version 5.6 and upload this zip

Jul 27 '17 13:07 Bones5

I'll be pushing out a 5.6 compatible version either tonight or tomorrow.

Jul 27 '17 14:07 funkjedi

Any news ?

Jul 31 '17 06:07 gfStudioTesta

Yes any news on this?

Jul 31 '17 15:07 gab1982

I also have this problem... Client very angry =(

Aug 02 '17 13:08 tomanthoni

Had to roll back to ACF Pro 5.5.14. but can't wait for the fix...

Aug 02 '17 14:08 cyberfly999

Yes, I also rolled back to 5.5.14. Fixed it.

Aug 02 '17 15:08 tomanthoni

I rolled back too however if a client updates it then will become an issue, hoping for a fix soon...

Aug 02 '17 15:08 gab1982

@gab1982 @paulinhoerry @gfStudioTesta @Bones5 @funkjedi Fixed for ACF PRO 5.6.0

https://github.com/Tusko/acf-qtranslate/commit/aefdf4e5645b489be60c57724c10f36ba2319ea7

Aug 03 '17 08:08 Tusko

Thanks!

Aug 03 '17 08:08 tomanthoni

Ty !

Aug 03 '17 08:08 gfStudioTesta

thanks :)

Aug 03 '17 08:08 gab1982

Great, thanks :-)

Aug 03 '17 11:08 cyberfly999

@Tusko So the fix is simply changing the extends to "acf_field" for the 5 file in src/acf_5/fields/ ?

So I guess to keep backward compatibility, a quick (but quite dirty) fix would be something like:

if($acfVersion < 5.6) {
    class acf_qtranslate_acf_5_file_dynamic extends acf_field_file {}
} else {
    class acf_qtranslate_acf_5_file_dynamic extends acf_field {}
}

class acf_qtranslate_acf_5_file extends acf_qtranslate_acf_5_file_dynamic {
 //[...]
}