Hello thank you for pointing on this. It has already come to my mind that there might be a problem with Themes which are updated.
So one thing I will definitly implement for the next release are custom paths for the stylesheets:
They could also be saved to the wp-content folder, to the upload folder or the folder of a child theme, so I think it is best if you can choose the location yourself.
Would this feature be sufficient for your needs? Or would you like to have different styles an/or stylesheets for each different Child Theme? I also can think of this one, but this second approach would take some time.
Please tell me
Blackbam
I think the theme directory is the right place, as that’s where the theme’s CSS is, but in the case of a child theme they should be in the child theme’s directory.
Ideally it should work like everything else in a child theme. WordPress uses the parent theme directory first, but is overridden by the presence of the same file in the child theme directory.
As child theme creation is a manual process, your plugin just needs to know that a child theme is being used and to look in the child theme directory first. I think it’s fine leaving it up to the user to copy the CSS file to the child to start.
I personally don’t see the need to put them elsewhere, but others might.
Thanks,
Michael
Ok so I will turn this into a feature request and implement it for the next release of the Plugin which will be in a few weeks.
Thanks,
Blackbam
I think it is a good idea to have the css go outside of any theme folder. Child themes can be updated just as can Parent Themes, and this could cause an issue with overwriting custom css.
I think custom path would be the way to go in general.
Hello, I think that user defined paths are the way to go, too (will be one of three options available in the next version of the Plugin).
It just will take me one or two weeks more to implement the current feature requests and release the next version, thank you for your understanding.
