Home>Support>SiteOrigin custom css won’t work after updating pages

SiteOrigin custom css won’t work after updating pages

By Andrea Szocs, 6 years ago. Last reply by Andrea Szocs, 6 years ago.

Hi,
I have an interesting issue with SiteOrigin custom css. I have installed the plugin, and when I give style for a specific id it will work fine, until I update the page. After updating the page the row’s id name will change, since WordPress will generate a different id each time. So that means I have to re-name each time the id in the custom css, or add custom css only when the page is finished and no more update will be needed, but these are not the right solutions. Also there are no unique ids or classes in most of the case.
So a solution would be to create a template, child theme, but then why nobody is mentioning this in tutorials or support pages. I installed custom css to avoid the creation of templates, therefore I hope that there is a solution for this.
Besid that, for some reason my SiteOrigin css live demo doesn’t work, I hit both bottons but nothign happens

Thank you.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 6 years, 8 months ago Alex S
    Hi, I Work Here

    Hi Andrea,

    We recommend creating custom classes/ids. You can do this by opening the row/widget you wish to alter and heading over to the row/widget styles sidebar. Open the Attributes settings group and set a Row/Widget ID/Class as desired – don’t include the period or the hash.

    Regarding your other issue, that sounds like a plugin conflict. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.

    If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.

    Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.

    If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.

  2. 6 years, 8 months ago Andrea Szocs

    Thank you for your help I will do that.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More