You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The add_et_tag() function in this plugin's Divi integration prevents loading of various scripts in the Divi visual builder by adding the et_fb_ignore_iframe class to their script tags:
This breaks some Divi module(s) that depend on these scripts being loaded in the visual builder. Notably, Divi modules that rely on the WordPress script i18n API for translation functions (provided by the wp-i18n script) may crash without this script; however, there are probably also other problems caused by preventing core JavaScript files from loading in the visual builder.
The text was updated successfully, but these errors were encountered:
jonmarkhall
changed the title
Divi integration breaks certain Divi modules in the Divi visual builder
Divi integration breaks certain Divi module(s) in the Divi visual builder
Feb 9, 2024
Thanks for sharing this @jonmarkhall - it was very helpful. I encountered the same issue on one of my modules which relies on wp-i18n. I was able to work around it by capturing the tag prior to Rankmath's modification and restoring it again afterwards, with this code:
It would be nicer, though, if Rankmath either adds 'wp-i18n' to the excluded handles in add_et_tag(), or adds a filter to the exclusions list so that we can add our own.
The
add_et_tag()
function in this plugin's Divi integration prevents loading of various scripts in the Divi visual builder by adding theet_fb_ignore_iframe
class to their script tags:seo-by-rank-math/includes/3rdparty/divi/class-divi.php
Line 280 in 657ebb1
This breaks some Divi module(s) that depend on these scripts being loaded in the visual builder. Notably, Divi modules that rely on the WordPress script i18n API for translation functions (provided by the
wp-i18n
script) may crash without this script; however, there are probably also other problems caused by preventing core JavaScript files from loading in the visual builder.The text was updated successfully, but these errors were encountered: