Viewing 2 posts - 1 through 2 (of 2 total)
The topic ‘New Blocks CSS conflict with default blocks’ is closed to new replies.
Hi Andrew,
I added some new blocks which uses Bootstrap v4 with custom css and included the new css file path in /elements/skeleton.html and published a site using the newly added blocks but sites are not loading as per the design because there is css conflict Professional_skeleton.css uses Bootstrap v3 and my new blocks designed with higher version with custom css.
I would like to know if there is any way to only include custom block css if the site is built using only custom blocks and include Professional_skeleton.css if it is using only default blocks. By this, i can easily solve my issue
I can provide default blocks (Yummy) to the basic user on my packages
And custom blocks to my premium users only
As of now using bloxby package rules, i can assign Yummy for basic users and custom blocks to premium users but the problem is /elements/skeleton.html file requires both the css files.
Request you to please help me resolve this issue.
I would also like to know if your team have written style coded in Professional_skeleton.css or it just uses plugins style files like Bootstrap, fontawesome, Hover etc
Thanks
Replies only viewable for logged in users
The topic ‘New Blocks CSS conflict with default blocks’ is closed to new replies.