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

 

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.