Home>Support>Custom CSS not working on iKnow Theme

Custom CSS not working on iKnow Theme

For some reason, Custom CSS is previewing the changes I’m making to the main background color of my Word Press site which uses the iKnow theme, but the changes are not taking effect when I view the page in the browser.

Instead, iKnow’s native customization take precedence. The selections are limited.

I’ve tried various remedies, including disabling all plugins except Site Origin CSS. Again– my changes show in Site origin’s preview, but are not taking effect.

What am I missing here?

Glen Gummess

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

  1. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Hi Glen

    Thanks for reaching out.

    If possible, please, send a link to a page concerned and let us know which part of the page to inspect to view a rule that isn’t taking effect.

  2. 2 years, 1 month ago Glen Gummess

    Hello Andrew, I very much appreciate the quick response. The link to the staging site (which is the same as the live site) is https://08f.be3.myftpupload.com/wp-admin/ . I don’t know how that could help you but I threw that in, anyway.

    What I have done is send you a screencast which runs 2 and a half minutes which shows you the dilemma I’m facing. I hope that clarifies things.

    Let me know.

  3. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Thanks for the link.

    Email replies post the forum. Unfortunately, attachments aren’t supported.

    Is SiteOrigin CSS activated? To help, please, let me know one CSS rule you’ve added at AppearanceCustom CSS that you’re expecting to see a change and that change isn’t happening. I’ll inspect the rule and explain what’s happening.

  4. 2 years, 1 month ago Glen Gummess

    Andrew, I’m trying to change the CSS rule below to the hex code of 503412.

    .hero-body {
    background-color: #503412;
    }

    The screenshot in preview looks like this:

    [cid:[email protected]]

    But the live version looks like this:

    [cid:[email protected]]

  5. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Thanks, Glen. The forum doesn’t support attachments. Thread: Custom CSS not working on iKnow Theme

    I’m not seeing SiteOrigin CSS adding a stylesheet to the page. If SiteOrigin CSS is activated, you can try running a plugin conflict test. Temporarily deactivate all plugins except for SiteOrigin CSS and see if the issue resolves.

    A caching or performance plugin might be involved. At the moment, SiteOrigin CSS isn’t present on the page.

  6. 2 years, 1 month ago Glen Gummess

    I will give that a whirl.

  7. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    That sounds like a plan. Chat further when I’m back online tomorrow. Cheers.

  8. 2 years, 1 month ago Glen Gummess

    Yesterday I disabled all the plugins except for Site Origin CSS, and still got a null result. The change I wanted manifested itself in preview, but did not take effect, ultimately.

    My workplace really prefers the iKnow theme, so changing themes is not an option. What is frustrating is that until recently, the changes I made with Site Origin CSS did take effect. There must have been an update that became a gamechanger.

  9. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Thanks for trying. Please, take a screenshot of what you see at AppearanceCustom CSS. You can upload it to any online location like Dropbox or WeTransfer or your Media Library and send the link here. I’m unsure why I’m not seeing the SiteOrigin CSS stylesheet output in your page.

  10. 2 years, 1 month ago Glen Gummess

    I used WeTransfer: There are two screenshots. I am not sure if these are what you need. By the way, GoDaddy just updated WordPress to 6.0.1, but that did not change anything.

    Here is the link: https://we.tl/t-qse69NWj14

  11. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Thanks for the screenshots.

    AppearanceCustom CSS is part of SiteOrigin CSS.
    CustomizeAdditional CSS is the core WordPress field and not part of SiteOrigin CSS.

    Please, could you show us the site with all plugins deactivated except for SiteOrigin CSS.

  12. 2 years, 1 month ago Glen Gummess

    https://08f.be3.myftpupload.com/ with all plug-ins deactivated except for Site Origin CSS.

    This is the staging site—exactly the same as the live site (learnitnow.stfrancis.edu).

  13. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Thanks. All plugins still seem to be activated. Where is the deactivation being done from?

  14. 2 years, 1 month ago Glen Gummess

    Andrew, the de-activation is done from the staging site’s Word Press dashboard. I select installed plug-ins and go down the list. The only one activated is Site Origin CSS.

    Good Monday morning, by the way,

  15. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Hi Glen :)

    Thanks for the update. When I view the site, this is what I see active in the Plugins folder: https://siteorigin.com/wp-content/uploads/2022/08/Learn_It_Now_–_Resources_for_Teaching_and_Learning_with_Technology.jpg

  16. 2 years, 1 month ago Glen Gummess

    I’m at a stalemate on this. When I clicked on the link, https://siteorigin.com/wp-content/uploads/2022/08/Learn_It_Now_, I got “Sorry! That page can’t be found.”

    I have been working on the staging site for “LearnitNow”. The plugins are de-activated on that site except for Site Origin CSS. The staging site’s address is https://08f.be3.myftpupload.com/wp-admin/

    How do we get closer to a solution?

  17. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Here is the screenshot in another location https://imgur.com/a/wrtTMEZ. From a code perspective, it doesn’t appear as though a plugin conflict test is currently being run.

  18. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    I’m unsure why the SiteOrigin CSS stylesheet is being loaded on the site front-end. A plugin conflict test is where I recommend starting the investigation. Alternatively, all rules from AppearanceCustom CSS can be copied to CustomizeAdditional CSS.

    We can log in and assist directly under our SiteOrigin Premium support scope. If you’d ever like us to do that, please, consider a premium license.

  19. 2 years, 1 month ago Glen Gummess

    Andrew, we want to invest in the advanced website security plan for $14.99 a month. Where do we go from here?

  20. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Hi Glen. I don’t think that’s us.

  21. 2 years, 1 month ago Glen Gummess

    For Andrew,

    I received a message from gao-support that closed the ticket but the problem on my end is not resolved. I tried to send the following reply after I received the message that suggested I contact the theme’s developer to resolve our issue with custom CSS.

    Here is what I have sent, and I would like very much to receive a response.

    Clarification request: Contact who, exactly, the developer of the iKnow theme?

    I need a contact with iKnow. I’ve tried contacting them myself and they are opaque to the point of inaccessibility. So, if you or someone have a contact for iKnow, please give it to me: phone number to a live person—not a robot. Email to a live person or office, not robo-email.

  22. 2 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Hi Glen

    Thanks for your reply.

    Previously you mentioned:

    Andrew, we want to invest in the advanced website security plan for $14.99 a month. Where do we go from here?

    Is it possible you’ve confused SiteOrigin with another company? We don’t currently offer a $14.99 a month plan. If you’d like to migrate this support thread off our forum and onto email support where we can assist directly, please, consider a SiteOrigin Premium license.
    Download: SiteOrigin Premium

    Regarding your message today. Have you isolated the issue to the theme? You can do so by temporarily switching to another theme and then checking to see if the issue persists. If the issue persists when another theme is activated, then it’s unlikely the theme is involved in the problem. You could run this test by making a change SiteOrigin CSS with another theme activated and then checking the live site to see if the change reflects.

    We, unfortunately, aren’t familiar with the iKnow theme.

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