now this bug
Could be a known issue:
If front end action/element contains non-parsable JS code, this error also fires.
thanks @Jici and @redvivi it was indeed the known bug that has been around since 2022 that is the cause…I wonder at which point it becomes more financially responsible to just fix it rather than leaving the bug in the system.
If you are encountering difficulties publishing your plugin, it could be due to the inability to minify or obfuscate your code. To troubleshoot this, we suggest checking if the issue persists when you do not select the “obfuscate client-facing code” option during the plugin publishing process.
Should the problem persist, we recommend executing the console command window.do_not_minify_plugin = true in the developer console on the plugin editor page before submitting your plugin. This step may help you successfully publish your plugin.
for me only the console command worked
This topic was automatically closed after 14 days. New replies are no longer allowed.
