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
Hi, I had a problem with additional CSS classes not saving then came across this old thread with the workaround.
I’ve disabled the plugin to solve the issue as having to hit enter on each change is counter-intuitive given that all other fields update on change.
I see I can disable that feature, but if this plugin contains features that break Gutenberg, I’d rather be safe and disable it while I don’t need the features I use. Anything that causes me to start hunting for bugs in my work is just adding chaos to chaos.
I’m wondering why this is being maintained as a ‘feature’, or maybe I misunderstood that thread?
Support
Hi, I had a problem with additional CSS classes not saving then came across this old thread with the workaround.
I’ve disabled the plugin to solve the issue as having to hit enter on each change is counter-intuitive given that all other fields update on change.
I see I can disable that feature, but if this plugin contains features that break Gutenberg, I’d rather be safe and disable it while I don’t need the features I use. Anything that causes me to start hunting for bugs in my work is just adding chaos to chaos.
I’m wondering why this is being maintained as a ‘feature’, or maybe I misunderstood that thread?
Details
Note: This support issue is created automatically via GitHub action.
The text was updated successfully, but these errors were encountered: