Could you explain me why you set some css rules in cs.theme.7.6.0 with !important?
It breaks a layout of my first section on one of my websites that needs margin-top: with negative values! Now i couldn’t overwrite it with custom css in the editor as it worked before upgrade to 6.6.0.
There are many more css settings that have an !important attached!
I used integrity stack before, and even with switch to starter pack didn’t help.
It’s been !important since the inception of the The Content element from what I can tell. It probably shouldn’t do that though, I’ll see about removing the !important. Have a great day.
Sorry, I forgot to mention that this happened on the page where I migrated 368 posts from shortcode to HTML. And it happend on the local dev site.
Both the live and the development site are now on version 6.6.0, but this error is currently only occurring on the local development site where I did the HTML migration process. The live site is still using shortcodes.
The following problem have occurred. In the old structure there is another div with cs-content between the .x-the-content .entry-content and my x-section. However, this intermediate div is missing on the local page after the migration.
Live site with working css:
Local development site with missing cs-content container:
So something must have gone wrong during the migration process, because this cs-content div is present in the non-html version on the live site.
Thanks for sending our way. I’ll make sure the cs-content div wraps HTML content like in shortcodes. With that hypothetically in place, the margin important issue doesn’t matter then right? Have a great day.
Yes, if the cs-content div is present again, everything should be as it was before.
I mean, I don’t know what the cs-content was originally intended for, and I think it’s basically good if the DOM doesn’t get too big. But if we remove it, the corresponding css must of course also be removed.
For backwards compatibility it would of course be better if it is included. Because who knows who has already addressed it for the layout style with css. But in the end you have to decide which is better.
Okay we’ll add in cs-content just to match the shortcode output. We can review it’s purpose later, but I think it’ll probably just stick around for now. Have a great weekend.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.