Hi,
I had a problem with Site Origin Custom CSS. It happened when I publicly launched my site by moving it from a staging subdomain to the primary domain. Everything moved successfully, but afterward my edits to Site Origin Custom CSS stopped being published to my site. The edits were accepted by the editor, and would be retained even if I logged out and back in to wp-admin and re=opened custom CSS. But none of my edits would be published to the site. The old custom CSS file – the last version I made before porting the site from the staging subdomain to the primary domain – continued to be the one that was utilised. All my edits were obviously going into some storage somewhere, but the new version wasn’t being used, the old unedited version was still being published.
Of course this seemed like a cache issue, but after all sorts of cache clearing efforts that changed nothing, I tried instead entering the new CSS rules in the WordPress Customizer Additional CSS page. New rules were published to the site immediately, but I still couldn’t change rules that were set in the SiteOrigin Custom CSS, because my edits to it weren’t published and it was being given priority over WordPress Customizer Additional CSS. Only by moving all my CSS rules from SiteOrigin Custom CSS to WordPress Customizer Additional CSS Page, then disabling SiteOrigin Custom CSS, was I finally able to change the rules I wanted to change.
The only new plugin that might have had something to do with this was Velvet Blues Update URLs, which I used for the URL clean-up after porting from staging to primary.
It’s a nice plug-in so I’d like to be able to use it. Cheers.
Update: I’ve found that another user had this same issue. Thread: Custom CSS not working after migrating to live site
Unfortunately the OP on that thread marked it resolved without explaining how he fixed it. SiteOrigin CSS apparently stores a hard-coded link to its custom CSS file, which doesn’t get changed by Velvet Blues, since that’s what I used.
I tried deleting Custom CSS plugin and re-installing it, but that failed to reinitiate it. The custom CSS edit page looks like it’s empty, but the old CSS rules as I last had them before I migrated are still published.
If I understand right, what we’ve got here is that after migration and Velvet Blues clean-up, Custom CSS has one place where the editor saves its file (on my post-migration site) but its link used for publishing CSS to the web still points to my pre-migration site.
If that’s right, where can I find this link that needs to be updated?
For the future, would it be possible to change the way Custom CSS links to its files so that the file from which Custom CSS publishes to the web is always the same as the file used by the Custom CSS editor? Or if that’s impossible, perhaps you could make the link manually updateable as an option on the Custom CSS page in wp admin?
Cheers.
Hi Warnerta,
That’s odd – we don’t actually store the URL unless you specifically tell us to (via CSS). Do you have a public URL where we can take a look at what’s going on?
Are you using a cache plugin or anything like that? If so, please try clearing them to see if that works.