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].
Normally, this is simple. Publish a page title “blog” and select it in the “reading settings” as the posts page.
This creates an error and the page looks messed up and unformatted.
I’ve read other threads about unselecting the blog as the posts page in the reading settings and using the post loop widget. I get a message saying “your theme doesn’t have any post loops!”
What now?
If I need to edit the PHP file or something I’m gonna need some EXPLICIT instructions!
Thank you in advance,
Christian
Hi Christian
Thanks for reaching out.
If possible, please, could you assign a blog page via SettingsReading and send us a link to the assigned page? We’ll take a look and advise from there.
For reference, the Post Loop Widget looks for templates as follows:
*-content.php
content-*.php
*-loop.php
loop-*.php
Where * can be any string.
Page: Post Loop Widget
Thanks Andrew. I’m not sure how the post loop fit into my situation but I was just trying out what another thread mentioned.
Here’s the blog page that’s not formatting properly:
https://www.houndtherapy.com/blog/
Thanks for the help.
Hi, thanks for the update.
You mentioned that the Post Loop Widget isn’t showing any available templates. My information above is to outline how the Post Loop Widget looks for templates. If it can’t find any it means that, unfortunately, your theme doesn’t have files in the above naming pattern.
There is a PHP error on your blog page which is why it isn’t rendering normally. To resolve the issue, try checking for a working baseline. Temporarily deactivate all plugins. In that state, does your blog page display normally?
So I turned off all of the plugins and there was a “critical error on the website” and it went blank.
I’ve switched all of the plugins on and off and the only ones the site goes blank or has a critical error is the “Advanced custom fields” plugin. Here are the following plugins installed:
Advanced custom fields (forces the critical error)
Advanced custom fields PRO (no update available without license key but when I deactivate it doesn’t change anything)
Advanced Custom Fields: Options Page
Advanced Custom Fields: Repeater Field (This makes stuff disappear)
The plugin is updated (not PRO) so I’m not sure what to do next. Delete and re-install? Will that blow up the entire site?!
Thanks for the update. The issue could be code that’s written for ACF – compatibility code in another plugin or your theme. If possible, consider enabling WordPress debugging and debug logging to find out what the error is specifically. Here is how https://www.wpbeginner.com/wp-tutorials/how-to-find-and-access-wordpress-error-logs-step-by-step/.
Thanks. After some trials here are the error messages that appeared in the log:
Stack trace:
#0 /home/houndthe/public_html/wp-includes/template-loader.php(106): include()
#1 /home/houndthe/public_html/wp-blog-header.php(19): require_once(‘/home/houndthe/…’)
#2 /home/houndthe/public_html/index.php(17): require(‘/home/houndthe/…’)
#3 {main}
thrown in /home/houndthe/public_html/wp-content/themes/houndtherapy/index.php on line 56
[04-Jan-2022 17:04:42 UTC] PHP Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/houndthe/public_html/wp-includes/functions.php on line 5211
[04-Jan-2022 17:04:42 UTC] PHP Notice: Trying to access array offset on value of type bool in /home/houndthe/public_html/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-template.php on line 499
[04-Jan-2022 17:04:42 UTC] PHP Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/houndthe/public_html/wp-includes/functions.php on line 5211
[04-Jan-2022 17:04:42 UTC] PHP Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/houndthe/public_html/wp-includes/functions.php on line 5211
[04-Jan-2022 17:04:42 UTC] PHP Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/houndthe/public_html/wp-includes/functions.php on line 5211
[04-Jan-2022 17:04:42 UTC] PHP Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/houndthe/public_html/wp-includes/functions.php on line 5211
[04-Jan-2022 17:05:00 UTC] PHP Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/houndthe/public_html/wp-includes/functions.php on line 5211
[04-Jan-2022 17:05:00 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_pagenavi() in /home/houndthe/public_html/wp-content/themes/houndtherapy/index.php:56
Stack trace:
#0 /home/houndthe/public_html/wp-includes/template-loader.php(106): include()
What do I do with this info?
It looks like it as ACF pro that was the problem. It’s not updated since it requires a premium membership. Will this fix the issue?
Hi Christian
Your theme is producing a fatal error. Ideally, the theme author would be the best party to contact.
Try installing https://wordpress.org/plugins/wp-pagenavi/.
It worked! Woohoo!!!! I didn’t quite understand the whole explanation of how the plugin worked but it freaking worked!!
Looks like I need to change the banner but what a relief…
THANK YOU ANDREW MISPLON!
You’re a gentleman and a scholar!
Hi Christian
Thanks for the update. I’m happy to hear you’ve made progress. Your theme looks to be calling a function in WP PageNavi without first checking whether the plugin is activated. Usually, before calling a plugin-specific function, the author would first check to see if the function exists in the WordPress installation. It doesn’t appear as though that check has been used in this case. If you remove WP PageNavi, your theme continues to call a WP PageNavi function that no longer exists, causing a fatal error. I can’t say for sure, but it appears this is what happened.
All the best with your site :)