Installed the Siteorigins CSS plugin, which is doing what it should. Where are the css files being saved. Have a child theme and it is not being saved there. Inherited this page from someone who wanted it updated but has no information about how to log in to the web host.
Storage of custom CSS files
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Joe
All that code is actually stored in the database and then just added to the header on page load. We have considered the idea of giving users the option to store their custom CSS in a file, which would probably be stored in the wp-content/uploads folder. Is this the kind of feature you’d want?
I think it would be nice to have is stored on an identifiable file you could pull out and work with, like a child theme css file. My specific issue was that I am modifying a page without access to the files themselves because I have no access to the the files.
What would the order of precedence be for the three main css files, original theme, child theme and siteorigin css? Will the siteorigin files overwrite anything I put into the child theme?
I agree with Joe. I think the ideal solution would be that the plugin directly edit the child theme css file. That would be consistent with the editing method we’re used to.
Prospective plugin users whose theme css files are already heavily edited will resist adding a new plugin that forces them to rework their existing stylesheet.
This solution would also allow users to change themes without styling conflicts. (I know that some people change themes seasonally.)
Of course, I have no idea how difficult that solution would be to implement.
Thanks for your hard work.