Hi, when I duplicate/copy, for example, a Div with a .testClass class, the duplicated element gets a unique generated class instead of .testClass - this slows down the workflow a lot. Maybe it would be better to remove the automatic generation of unique classes when duplicating and copying?
Currently, users have to manually rename automatically generated classes one by one in duplicated/copied elements, which is time-consuming
Hello @Robban,
In Cwicly, each block comes with its own unique class. When applying styles to the block directly, it is the block class that you are modifying.
In your case, I believe you want to create and apply global classes instead: Global/Block Classes | Cwicly
When copy/pasting, the global classes you have applied will be kept and will react to any changes you make to the naming/styles.
Hope that helps.
Cheers,
Hello @Louis ! 
Thank you for your quick response
It’s a pity that you can’t disable class autogeneration in the settings. I didn’t understand the advantage of the concept with autogenerated classes - in my opinion it makes the code messy, and I have to delete generated classes all the time, because I don’t need obscure classes with the name, for example, .div-c633e08 - these classes confuse me. Personally, I think that working with classes is best realized in Webflow.
In my opinion, cwicly has a very cool Grid implementation. Cwicly has a handy css designer, but class manager upset me a lot.
It’s actually disabled by default:
Not sure what you are doing here. You can’t delete block classes.
The only option you have is to rename them.
In practice, there is no difference in naming or renaming a class. You have to type them either way.
Block classes only show up in the code when styles are applied via interface, or manually toggle them. There is nothing to worry about, and what you stated isn’t what actually happens.
You might have to elaborate on your actual process.
For example, this is strictly to avoid.
It has its good sides, but it’s limiting.
Cwicly’s system doesn’t force you regularly into workarounds.
It is as flexible as it can be and offers all the freedoms that you won’t find in any other (WP) tool.
Once getting used to it, it makes so much sense and offers plenty of additional value/options.
This is only due to some misconceptions, as it appears to me.
While I don’t have the time to go into detail here, a quick forum search will shed some light on the missing parts.
I thought about what you said, you are right, I should just get used to the Cwicly style manager, the Cwicly style manager is not worse than the Webflow style manager, it’s just different, with its own pros and cons.
If you look at Cwicly in its entirety, it appears to be one of the best page builders on wordpress, which has its own features that I’ve already started to get used to after 1 day of use
Thanks for opening my eyes @Marius
2 Likes