Accepted answer

From what you have said, this is probably NOT your problem, but just in case I will share this advice - because I ran into this recently. 

If you save any color changes in the theme settings (using color module). Your theme will create new temporary css files. These files will override the main css files until you regenerate them by re-saving the color settings in your theme. 

If you have not saved any color changes through the theme user interface, then this is probably not your problem, but it's still worth being aware of. We're trying to find a way to fix this. 
https://github.com/backdrop/backdrop-issues/issues/4295

 

Most helpful answers

@zilvervos - I don't have time right now to try and figure out exactly what is happening, but I can recommend a blog post that I wrote about how the color module works. 

https://www.triplo.co/blog/color-module-backdrop-cms

This might help you understand the source of your problem (but it might not). 

Comments

Hello @willowf ; thanks for reporting.

Sounds like a cache issue to me. As a sanity check can you try clearing cache from the admin bar on your production site?

willowf's picture

Hello, if I already did it, it does not recognize the css or changes in the .tpl of the Subtheme.
When analyzing the code, it links to the main theme css.
Locally it works.

Maybe the problem is permissions, what permissions should I put to the folders and files of the new Subtheme?

maybe temporarily disable cacheing and aggregation on `/admin/config/development/performance`

save

clear cache

 

see if your changes take effect.

willowf's picture

It doesn't work ... but I just modified Basis and the Subtheme applies those changes.

It means skipping overrides

stylesheets [all] [] = css / component / header.css

stylesheets [all] [] = css / skin.css

From what you have said, this is probably NOT your problem, but just in case I will share this advice - because I ran into this recently. 

If you save any color changes in the theme settings (using color module). Your theme will create new temporary css files. These files will override the main css files until you regenerate them by re-saving the color settings in your theme. 

If you have not saved any color changes through the theme user interface, then this is probably not your problem, but it's still worth being aware of. We're trying to find a way to fix this. 
https://github.com/backdrop/backdrop-issues/issues/4295

 

willowf's picture

He tried everything that was recommended to me, it still doesn't work, maybe the option Disable CSS / JS aggregation is not working.

Where can I manually activate to test it? 

willowf's picture

 

solved, I had a module that made a conflict colorbox ... Thank You 

Can you share which module has this conflict?

willowf's picture

 

Hi, he dismissed these two modules.

I was trying to follow the instructions on how to create a subtheme (https://docs.backdropcms.org/documentation/creating-sub-themes and https://backdropcms.org/news/build-a-sub-theme-of-basis-the-default-fron...) but ran into the same issues as described above. None of the changes I made in skin.css in my subtheme folder had any effect on my website. But when I switched off the color module, both color changes in skin.css as well as font changes (from sans-serif to serif) were suddenly reflected on my website after I flushed caches. I would say this is a quite serious issue: it means subthemes don't work when color module is switched on.

@zilvervos - I don't have time right now to try and figure out exactly what is happening, but I can recommend a blog post that I wrote about how the color module works. 

https://www.triplo.co/blog/color-module-backdrop-cms

This might help you understand the source of your problem (but it might not). 

@stpaultim That was very helpful. When I switched on the color module again, the style changes that I made in skin.css were undone again. But when I clicked "Save theme settings" on [site-url]/admin/appearance/settings/eriks_basis the style changes reappeared. I understand why this happens and I now know what I have to do to

Still, for new users this is quite unexpected and counter-intuitive behavior of the BackdropCMS software. Ideally this issue (and its solution) should be covered in the two posts with instructions how to create a sub-theme that I referred to in my previous post.