Sorry for the confusion and display issues. It was never our intention to force ActiveCampaign CSS for all forms. A Hotfix release 8.1.3 was deployed this morning.
We initially didn’t support block/shortcode level CSS options, we added support for css=0/1 in v8.1.0
The plugin settings CSS options and caching were deemed confusing internally, so we intended to deprecate that. We did this last release, but failed to properly account for the fact that even though the plugin updated, the existing blocks/shortcodes did not.
Existing blocks, despite being on the newest plugin version, hadn’t actually updated their code/logic. Instead of using the existing global setting as a fallback we erroneously used css=1.
Despite being hidden in the plugin settings, shortcodes and blocks without an opinionated css=0/1 will use the legacy routine of rendering based on the plugin settings. All new blocks will force an opinionated setting for the CSS to avoid these sorts of issues in the future.
As mentioned above, an explicit value for css=”” is the direction we’d like to move.
Very sorry for the inconvenience. I’ll be monitoring the thread if you have continued issues or questions.
-
This reply was modified 3 years, 10 months ago by
acjhorton.