This is one of the most hilarious yet annoying issues I encountered recently. In /gdpr-framework/vendor/illuminate/support/helpers.php line 541 ff., a GLOBAL function called “e” is declared. While this is borderline idiotic, it only causes problems if some other plugin author has the same bad idea – as it happens in /product-enquiry-pro/wisdm-forms/libs/functions.php on line 84 (v. 6.3.2, most current as of today). Depending on which plugin is loaded first, you either get a seemingly working setup that just does very funny things because e() in the gdpr-Plugin has absolutely nothing in common with e() in the Woocommerce addon except for its name and its global scope, or (at least) you get a hard error stopping WordPress from enabling the plugin.
Please, please, please, check what 3rd party libs you “composer” into your plugin. Apparently, there is some unlit area in illuminate/support 😉
- The topic ‘GDPR Framework 1.0.28 uses 3rd party code that implements global function e()’ is closed to new replies.