Home>Support>I am testing SiteOrigin CSS (with Divi Theme from Elegant Themes)

I am testing SiteOrigin CSS (with Divi Theme from Elegant Themes)

I am testing SiteOrigin CSS (with Divi Theme from Elegant Themes) and not seeing information when I hover over elements.

Not sure what the problem might be, but I’m hoping you can assist.

Thanks,
Gary

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

  1. 7 years, 1 month ago Greg Priday Hi, I Work Here

    Hi Gary

    This sounds like it could be a plugin conflict issue. 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. 7 years, 1 month ago garymgordon

    Thanks!

    The conflict is caused by

    *CUSTOM POST WIDGET*
    http://www.vanderwijk.com/wordpress/wordpress-custom-post-widget/
    https://wordpress.org/plugins/custom-post-widget/

    Please let me know what you suggest.

  3. 7 years, 1 month ago garymgordon

    Any thoughts?
    Gary

  4. 7 years, 1 month ago Greg Priday Hi, I Work Here

    Hi Gary

    Unfortunately I don’t know of any good alternatives to this plugin, but I’ll let you know if I come across any. For now, would it be possible to ask its developer to look into the issue?

  5. 7 years, 1 month ago garymgordon

    Do you know or have any idea as to what could be causing the conflict in their plugin?

  6. 7 years, 1 month ago Greg Priday Hi, I Work Here

    Unfortunately I haven’t had the chance to check it out. It’s probably just some sort of Javascript conflict on the frontend.

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