It looks like the banner style is applied to the latest post while the remaining posts display in a more conventional grid. Since the banner style shows the latest post in its own “hero” section, a remedial solution like hiding the banner or hero section doesn’t work because it’ll also hide the latest post. And getting the latest post to be in the normal grid section involves modifying queries, so there is not a simple solution that I can see.
There’s a chance your theme provides a setting to use or not use a hero section. If there is, that is the simplest solution. If you cannot find such a setting, I suggest asking for guidance through your theme’s dedicated support channel.
Because you use a commercial theme, the help we can provide here is extremely limited.
Hi and thank you SO much for that suggestion. After having torn my brain with trying various solutions I had nearly given up. Your HERO removal suggestion did the trick! Thanks a million!!
Best, Eva
Ha! That was a lucky guess 🙂 I’m glad it worked. You’re very welcome.
Thanks again!
In the kerfuffle of trying to work the HERO problem out I must have managed to move something accidentally around. Suddenly I was unable to edit anything on my site and got this disturbing error message.
Any idea what I have done and how I could rectify it? My beautiful block editing has suddenly disappeared as well 🙁
Thanks.
Eva
There has been a critical error on this website. Please check your site admin email inbox for instructions:
Fatal error: Uncaught Error: Class ‘Jetpack_Options’ not found in /home/u309630264/domains/theconferenceofthebirds.net/public_html/wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php:84 Stack trace: #0 /home/u309630264/domains/theconferenceofthebirds.net/public_html/wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php(45): A8C\FSE\WPCOM_Domain_Upsell_Callout->should_not_show_callout() #1 /home/u309630264/domains/theconferenceofthebirds.net/public_html/wp-includes/class-wp-hook.php(307): A8C\FSE\WPCOM_Domain_Upsell_Callout->enqueue_script_and_style(”) #2 /home/u309630264/domains/theconferenceofthebirds.net/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array) #3 /home/u309630264/domains/theconferenceofthebirds.net/public_html/wp-includes/plugin.php(474): WP_Hook->do_action(Array) #4 /home/u309630264/domains/theconferenceofthebirds.net/public_html/wp-includes/class-wp-customize-widgets.php(873) in /home/u309630264/domains/theconferenceofthebirds.net/public_html/wp-content/plugins/full-site-editing/wpcom-domain-upsell-callout/class-wpcom-domain-upsell-callout.php on line 84
No need to panic. It’s unlikely anything is truly lost. More likely inaccessible due to the error. Resolve the error and things should more or less be back to normal. At least the front end is still working. Can you access the back end at all? If so, what did you do to trigger the error?
The paths in the error messages puzzle me. You have a plugin called Full Site Editing (FSE)? But FSE is a built-in feature of WP. What does the plugin do?
Anyway, the WPCOM Upsell Callout module of the FSE plugin is looking for class Jetpack Options and not finding it. Have you been using the JetPack plugin? Is it currently active?
If you cannot access the plugins admin screen to check, lets deactivate all plugins to avoid the error. Using FTP or your hosting file manager, rename the /plugins/ folder. The new name doesn’t matter as long as it’s different. You should be able to access all parts of the back end now, though any functionality related to any plugins of course not be available.
After you’ve gained access to the back end, restore the /plugins/ folder name. All of your plugins will still be inactive, but now you can get to the plugins admin screen and activate plugins. Do so, one at a time, repeating whatever initially caused the error as a test after each activation. When the error is again triggered, the last activated plugin is the cause. Deactivate it again by renaming its specific folder instead of the overall /plugins/ folder.
Continue activating your other plugins until all are active except for the problem plugin. Take up the issue through the dedicated support channel for that plugin where its developers are in the best position to help you.
