Description:
I’ve only been using Cwicly for a few days, so maybe not a bug but a mistake on my part. Let’s hope. Here’s my problem:
I can no longer add a global class. Until this morning it worked, but since I regenerated the various CSS files a few hours ago, it doesn’t work anymore. When I create a global class and configure the styling, in the back-end I see the changes on the element with that class. At the front-end I don’t see the changes and the element doesn’t have the global class. When I go back to the back-end and want to refresh the page, I get an alert that there are unsaved changes. Strange, because I already saved the page and can’t save it again. When I refresh anyway, I no longer see the changes and the newly added class is replaced by the class “.removed”. Am I doing something wrong or is this a bug?
Sorry to hear you’re having trouble with the global classes.
If I understand correctly, you can add global classes to elements, create them and style them, but they don’t save?
This does sound unusual as the global classes entity is now linked to the WordPress save action. If this is a live installation, would it be possible for you to send temporary access details to support@cwicly.com so that we can take a look at what is happening exactly?
The ‘problem’ is solved thanks to Louis.
For other users, who may have the same problem: I thought saving the draft of the page was enough, but you really need to publish the changes.
Just chiming in here.
This is what we were doing up until 1.2.
While we can put it in place, I’m currently uncertain if saving global classes/stylesheets with a post/template save is the way to go.
Definitely something to explore with user feedback.