Temporary Solution for Broken Version: 3.8.15 Neve Starter Theme

  • Resolved michael3502

    (@michael3502)


    3 months ago

    I just installed a brand new WordPress site using the starter wizard and chose the Neve minimalist theme and Otter Plugin, and while initially it looked like the demo page, when I used the block editor to make an edit to a block and saved the page, much of the CSS color formatting had disappeared. I switched to and activated the WordPress 2025 theme and the missing CSS color formatting reappeared. I then switched to and reactivated the Neve theme and reloaded the home page and the missing CSS color formatting was visible again.

    So everytime I make and edit in the block editor and save it, I must repeat this reactivation solution of the Neve theme in order for the CSS color formatting to be visible.

    I thought perhaps the Otter plugin was possibly to blame, but deactivating it removed much of the CSS formatting and only by reactivating the Otter plugin was the CSS color formatting restored. Strange! I am not sure if Neve requires the Otter plugin, but whether the CSS color formatting problem is with the Theme or the Otter plugin, I know not. Nor do I know if a previous version of Neve worked any better. Sigh!

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • rodicaelena

    (@rodicaelena)

    Hi there,

    I’m sorry to hear you are experiencing these issues.

    As I’m not able to have access to your site, I can’t know for sure what is causing this, but I think this is probably related to the mixed content errors you have there, which is causing issues with styles from Otter.

    You can have a look here https://www.wpbeginner.com/plugins/how-to-fix-the-mixed-content-error-in-wordpress-step-by-step/ or on any other resources online to learn how to fix those.

    Kind regards,

    Rodica

    Thread Starter michael3502

    (@michael3502)

    Rodica: (Problem-Solved: Thanks to your Help)

    Thank you for taking the time to use your experience and insight to shed light on the problem I was facing which turned out to be the error of trying to load ‘mixed content’ (i.e. both secure and insecure content on the same web page). The problem with disappearing color objects on my home page was solved with a little bit of research that began when you pointed me in the right direction.

    Here is the message that appeared when reloading the home page while using the ‘Inspect’ developer tool console tab in FireFox BEFORE I found a solution. It appears the style sheet was being ?partially? blocked from loading (???)

    Quote: “Blocked loading mixed active content “https://bible-reflections.blog/wp-content/uploads/themeisle-gutenberg/post-v2-5-17 bible-reflections.blog 33251412.css?ver=3.0.8” “

    After I found a way to enforce https://, here is the NEXT message that appeared when reloading the home page while using the ‘Inspect’ developer tool in FireFox which indicated the problem had been solved. (It appears to have been a problem of a theme image which wasn’t loading securely, though I also had a black background in the home page’s ‘About Me’ area which also reappeared correctly after having previously disappeared.)

    Quote: “Mixed Content: Upgrading insecure display request ‘https://bible-reflections.blog/wp-content/uploads/2019/11/neve-minimal-blogger-12.png’ to use ‘https’”

    I am posting this in hopes that perhaps it might be obvious to someone why this default image from the Neve starter blog free theme from WordPress is being loaded as insecure content (i.e. https:// instead of https:// secure content) when Let’s Encrypt was already installed and an https enforce mode already enabled in security settings.

    My solution came from further searching in the various web hosting provider’s help pages about ‘mixed content’ which led me to a ‘Fix Insecure Content’ option that wasn’t yet activated in a plugin called the ‘Speed Optimizer’ plugin installed by default in my web hosting provider’s environment. When I activated that ‘Fix Insecure Content’ button it solved my problem by forcing all insecure content to be sent securely. Clap! Clap!

    Kind regards,

    Michael

    rodicaelena

    (@rodicaelena)

    Thank you for the update, Michael!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.