[Resolved] Translation of Media Grid (WPBakery)

Hi,

I would eventually also need to request temporary access (WP-Admin and FTP) to your site
– preferably to a test site where the problem has been replicated if possible –
in order to be of better help and check if some configurations might need to be changed

Your next answer will be private which means only you and I have access to it.

❌ Please backup your database and website ❌

✙ I would additionally need your permission to de-activate and re-activate Plugins and the Theme, and to change configurations on the site. This is also a reason the backup is really important.

✙ Please add the Links to the […] Edit Screen, the Page/Post where you insert the […] and the corresponding Front End Page/Screen

Best Regards,
Marcel

The WPBakery module and the images are correctly present in the English backend post (ID 2725). On the English homepage, you can even see the loading circles. However, the widget used there triggers the following JavaScript error:

On the homepage on EN we can even see the loading circles. What is caused on the EN startpage where the widget is used is the following error:

Uncaught Error: Syntax error, unrecognized expression: {"status":"Nothing found"}
    at I.error (jquery.min.js?ver=3.7.1:2:11769)
    at Y (jquery.min.js?ver=3.7.1:2:17234)
    at re (jquery.min.js?ver=3.7.1:2:20008)
    at ce.I (jquery.min.js?ver=3.7.1:2:7520)
    at ce.<anonymous> (jquery-migrate.min.js?ver=3.4.1:2:2898)
    at e.<computed> [as find] (jquery-migrate.min.js?ver=3.4.1:2:1582)
    at ce.find (jquery.min.js?ver=3.7.1:2:21991)
    at e.<computed>.<anonymous> (jquery.min.js?ver=3.7.1:2:22483)
    at e.<computed>.<anonymous> (jquery-migrate.min.js?ver=3.4.1:2:2438)
    at new e.<computed> (jquery-migrate.min.js?ver=3.4.1:2:1582)

Please try updating WPBakery Page Builder to the latest version first to check if this issue has already been resolved in a newer release.

Best regards,
Marcel

Hi,

I didn’t say it’s the theme’s fault. I just asked you to make sure everything is updated first. This helps us confirm that we’re not debugging an issue that might already be fixed in a newer version of WPBakery.

As mentioned, this is a default WPBakery functionality, and it appears correct in the backend. We also haven’t received other reports of this issue, so it’s possible that it only affects your specific site setup.

If the problem persists after updating, I’ll provide you with a sandbox environment where you can install WPBakery and try to reproduce the issue. If it occurs there as well, we can look for a workaround or contact the WPBakery developers if necessary to address it in their codebase.

Please note that this process might take some time and won’t be resolved within the next few hours.

Best regards,
Marcel

I understand your concern and apologize for the inconvenience. The request to test with the latest version was to efficiently verify whether the issue had already been resolved so we could proceed with the next steps promptly.

I’ll now transfer your case to another supporter who will review it further. Thank you for your cooperation.