Home>Support>Empty custom home page on all top level pages

Empty custom home page on all top level pages

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].

Hi there, we are using SiteOrigin Panels on https://www.hanfparade.de/ but we are not using the custom home page function.

And we have a huge problem. Instead of all top level pages on our website, the site origin “custom home page” will appear, which is empty, because it is neither activated nor edited. When logged in, the “edit page” link in the top bar will be “edit home page” and link to https://www.hanfparade.de/wp-admin/themes.php?page=so_panels_home_page

Caching is turned of. Also switching “custom home page” on and off again does not help. What might be the reason?

All top level pages are not working, e.g. https://www.hanfparade.de/programm-route/ – https://www.hanfparade.de/kontakt-mitmachen/ – etc.

Though they do exist as regular wordpress pages. Even why trying to access the page “programm-route” by its number at https://www.hanfparade.de/?p=415 the empty custom home page will show.

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

    Hi Gregor,

    We’re not too sure why this is happening. Would it be possible for you to create a temporary admin account for us so we can log in and take a look?

  2. 7 years, 12 days ago Private Message - Alex S Hi, I Work Here

    This is a private message.

  3. 7 years, 12 days ago Alex S
    Hi, I Work Here

    Hi Gregor,

    Actually, before creating an account (if that’s something you’re okay with), 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.

  4. 7 years, 10 days ago Gregor W. Sky

    Thanks Alex!

    Well yes, checking for plugin conflicts is the first step for debugging… I was hoping this might be a known problem. :)

    By looking at all plugins that we have, my first idea of a “conflict candidate” was PolyLang because it has the most impact on the site, technically.

    I deactivated PolyLang and the problem was gone.

    Then I reactivated PolyLang, and the problem is still gone! Everything working fine now. Just a question remains, for how long – the problem had appeared out of a sudden, and I guess this might happen again.

  5. 7 years, 10 days ago Alex S
    Hi, I Work Here

    Hi Gregor,

    Preface: No, this isn’t a known problem.

    Great to hear it’s working again. Not too sure why this issue occurred as a result of Polylang. That definitely means it could happen again. The next time you adjust any settings related to Polylang or anything like that, please make a note.

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