[ad_1]
So, if you want to replicate this error.
1 – Create a new popup with a CSS class trigger.
2 – Create a page with a page builder, create a button ( or anything with a css class that you will trigger that popup from ) .
Everything should work fine, unless your popup tries to call a CSS class that doesn’t exist anymore, or that has been changed, or has not yet been created.
If the plugin can’t find it, this will absolutely destroy your site and you will get a timeout error on the frontend, the only way you can get out of it is by deactivating the plugin, reactivating it, going back to your admin and deactivate the popup.
This has been by far the most @%FJ3é aggravating experience that I have ever had with any other similar tools.
This has been a real nightmare for the last week.
Please find a fix to manage such errors in a way that doesn’t trigger a resource overuse and f@fk% up people’s websites.
I am not doing any plugin conflict test or whatever, this is the issue and it is what it is.
- This topic was modified 1 hour, 30 minutes ago by .