Hi Pixelstyle,
It works like wp-config-sample.php – you’ll just want to rename custom-sample.css to custom.css and then you’ll be good to go. The reason I don’t include a custom.css is because then every time you update the plugin, your custom CSS would be overwritten 🙂
Hope that helps!
Chris
Won’t renaming the ‘custom-sample.css’ in your plugin folder still be overwritten when an update occurs?
That is true, b-summers. It was written with the Pro version in mind, which would be updated via FTP and overwriting only those files that exist in the default install, so custom.css would remain intact. For now, you would need to manually backup and restore the custom.css file, though I’m working on automating that for when the Pro version includes automatic updates. Thanks for pointing that out though!
Best,
Chris
Thanks Chris,
I assume there is no way to do something like WooCommerce does, where you create a folder in your template files, and just add the CSS in there, to avoid being overwritten?
You could always add a custom stylesheet via your child theme, you’d just also need to enqueue it via your functions.php. There isn’t a specific folder in the child theme that’ll automatically get picked up, but it’s an interesting idea to look into 🙂
Best,
Chris
