Home>Support>Hero Image and Full Width Layout not showing

Hero Image and Full Width Layout not showing

By poulomi, 6 years ago. Last reply by poulomi, 6 years ago.
Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

Hello,
I use SiteOrigin North.

My Hero Widget is not showing on any page, and my settings of all the rows are also not showing full width even though they are.

Sometimes if I refresh the original display shows, then when I refresh again, it doesn’t.

I have tried emptying the cache from my W3 plugin, didn’t help. Then I even deactivated the plugin. No difference.

Can you please help?

For a reference, you can see this page: https://weignitegrowth.com/services/contract-based-programs/
Or even the homepage.

I have at least one HERO widget and a few full-width layouts on every page, none of them are being displayed, even in Live Editor.

Thanks a lot
Poulomi

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, 7 months ago Alex S
    Hi, I Work Here

    Hi Poulomi,

    I’ve had a look at your website and this issue appears to be caused due to you deferring the main jQuery library. The jQuery library should ideally not be deferred and should instead load as soon as possible – I would exclude it from your performance plugins. Please note that this issue is affecting any plugin using jQuery on the frontend of your website.

  2. 6 years, 7 months ago poulomi

    Hi Alex,
    Thanks for your response. Actually I didn't so this consciously. Do you think it's being caused by a plugin, which is doing it automatically? How do I know how it's being caused?

    Thanks a lot

  3. 6 years, 7 months ago Alex S
    Hi, I Work Here

    Hi Poulomi

    Unfortunately, I’m not too sure what plugin you’re using is called. I would take a look for a performance plugin (other than W3 as, from memory, it doesn’t have the functionality to do this) in your plugin list – WP Admin > Plugins > Installed Plugins.

    If you’re unable to find one, I would run a plugin conflict test to find it. This is not to suggest this is a plugin conflict, it’s not, only that test is a good method of finding what plugin is doing what. For referene, here’s the typical plugin conflict test we provide/recommend:

    Before proceeding, please disable the W3 Total Cache Page Cache functionality in the settings of the plugin. This must be done because cache plugins are designed to work even when technically disabled.

    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.

  4. 6 years, 7 months ago poulomi

    HI Alex,
    Thanks a lot! I was able to do it :) I found the plugin responsible, and deleted it.

    Thanks a lot for your help!

  5. 6 years, 7 months ago Alex S
    Hi, I Work Here

    Hi Poulomi,

    Great to hear! :)
    Out of interest, can you please clarify what plugin was causing you issues?

    Please be sure to post another thread if you have any other questions.

  6. 6 years, 7 months ago poulomi

    Hi Alex,
    It is called WP deferred JavaScript. A WordPress expert who had helped me with my site a long, long, time ago, had installed it to make my site load faster.

    But I wasn't aware of it, and never paid attention as my site always loaded perfectly. I think the issues were maybe caused by the recent Gutenberg update. Maybe the plugin isn't compatible anymore.

    Hope that clarifies it!

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