Conversation
supportSince updating to ACF5.8.3, there is an error on the media page – no media appears. However, it is not an issue with ACF, as disabling ACF QTranslate solves the issue. Here is how I isolated the problem to ACF QTranslate, combined with ACF 5.8.3: – ACF 5.8.3 with ACF QTranslate = error – ACF 5.8.3 without ACF QTranslate = no error – ACF 5.8.2 with ACF QTraslate = no error Unfortunately I’m not getting any errors in console to provide more leads as to the issue. Please let me know if there is a solution, as I now rely on ACF QTranslate for the site, and I would like to be able to continue updating ACF. Thanks in advance
Hi, I had the same problem, there is a bug with acf_qtranslate_acf_5_image. As a work around you can comment the lines 31 and 39 of the file acf-qtranslate/src/acf_5/acf.php: //require_once ACF_QTRANSLATE_PLUGIN_DIR . 'src/acf_5/fields/image.php'; //acf()->fields->register_field_type(new acf_qtranslate_acf_5_image($this->plugin));
Hi, I have the same issue @marciomarim thanks! But it is not good solution)
Hello, Has anyone came up with a solution to this problem? Will there be a fix either within an ACF qtranslate plugin update or an ACF plugin update?? I had to revert back to previous version of ACF for temporary (I hope) fix. Thank you.
acf-qtranslate/src/acf_5/fields/image.php add_filter('wp_prepare_attachment_for_js', array($this, 'wp_prepare_attachment_for_js'), 10, 3); if ( method_exists( $this, 'wp_prepare_attachment_for_js' ) ) { add_filter('wp_prepare_attachment_for_js', array($this, 'wp_prepare_attachment_for_js'), 10, 3); } Until the update
Similarly to @sleepgreen , I’ve decided to delete line 75 that shows as below from wp-content\plugins\acf-qtranslate\src\acf_5\fields\image.php: add_filter('wp_prepare_attachment_for_js', array($this, 'wp_prepare_attachment_for_js'), 10, 3); In Advanced Custom Fields PRO version 5.8.3 they removed the function called wp_prepare_attachment_for_js() from the plugin, which is what’s causing the error. Along with that, the Advanced Custom Fields PRO team also removed the same add_filter('wp_prepare_attachment_for_js.... call that’s in ACF qTranslate. Because of that, I think it’s fine to remove that line entirely given that it’s likely no longer needed. This reply was modified 6 years, 7 months ago by Jonathan Goldford .
@jg-visual it worked for me, thanks alot
@jg-visual Thank YOU!!!
Hi, I had the same problem, there is a bug with acf_qtranslate_acf_5_image. As a work around you can comment the lines 31 and 39 of the file acf-qtranslate/src/acf_5/acf.php: //require_once ACF_QTRANSLATE_PLUGIN_DIR . 'src/acf_5/fields/image.php'; //acf()->fields->register_field_type(new acf_qtranslate_acf_5_image($this->plugin));
Hi, I have the same issue @marciomarim thanks! But it is not good solution)
Hello, Has anyone came up with a solution to this problem? Will there be a fix either within an ACF qtranslate plugin update or an ACF plugin update?? I had to revert back to previous version of ACF for temporary (I hope) fix. Thank you.
acf-qtranslate/src/acf_5/fields/image.php add_filter('wp_prepare_attachment_for_js', array($this, 'wp_prepare_attachment_for_js'), 10, 3); if ( method_exists( $this, 'wp_prepare_attachment_for_js' ) ) { add_filter('wp_prepare_attachment_for_js', array($this, 'wp_prepare_attachment_for_js'), 10, 3); } Until the update
Similarly to @sleepgreen , I’ve decided to delete line 75 that shows as below from wp-content\plugins\acf-qtranslate\src\acf_5\fields\image.php: add_filter('wp_prepare_attachment_for_js', array($this, 'wp_prepare_attachment_for_js'), 10, 3); In Advanced Custom Fields PRO version 5.8.3 they removed the function called wp_prepare_attachment_for_js() from the plugin, which is what’s causing the error. Along with that, the Advanced Custom Fields PRO team also removed the same add_filter('wp_prepare_attachment_for_js.... call that’s in ACF qTranslate. Because of that, I think it’s fine to remove that line entirely given that it’s likely no longer needed. This reply was modified 6 years, 7 months ago by Jonathan Goldford .
@jg-visual it worked for me, thanks alot
@jg-visual Thank YOU!!!