critical error when assigning posts page

  • Haomaru

    (@hianghao)


    3 weeks, 1 day ago

    ON neve fse theme I got this error as when assigning the posts page (immediately after pressing save changes) on settings>reading. However, WP automatically reverted the changes so i dont receive any error message/log. I believe this step is compulsory so that i can assign my blog page with the “blog template”. Currently i can only see 2 templates on page editor (no blog template even it existed), so i assume i must assign that page under WP setting as posts page in order to use the blog template.

    There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.

    I tried to bypass the post page setup by creating a page called blogs on a normal page template. Then on that page i added the query block to display the posts. The posts are visible under edit mode. However, in reader/view mode, not post is visible.

    • This topic was modified 3 weeks, 1 day ago by Haomaru.
Viewing 1 replies (of 1 total)
  • rodicaelena

    (@rodicaelena)

    3 weeks ago

    Hi there,

    I am so sorry to hear you’re running into a critical error when trying to assign your posts page. For the moment, we are not able to replicate a similar issue.

    Because Neve FSE relies entirely on the WordPress Block Editor and theme templates, this issue usually stems from a mismatch in templates, an outdated version of a core component, or a temporary conflict with another plugin.

    To help us narrow down the cause and fix this for you, please try the following steps:

    1.Check for an Error Log:

    When WordPress triggers a “critical error”, it usually sends an email to the site administrator with a technical description or a “Recovery Mode” link. If you received that email, please share the error message (specifically any mention of a Fatal Error, file paths, or specific line numbers) with us here.

    2.Update Theme and Plugins:

    Make sure you are running the absolute latest version of Neve FSE and any block helper plugins you use (like Otter Blocks). A recent version mismatch could be causing a PHP fatal error when WordPress tries to map your posts to the FSE template.

    3.Check the FSE Blog Home Template:

    Navigate to Appearance > Editor > Templates and check your Blog Home or Index template. If it’s corrupted or customized incorrectly, it can crash when assigned. Try temporarily resetting the template to its default state if the editor allows you to access it.

    4.Run a Quick Conflict Test:

    If the above doesn’t help, temporarily switch your site’s theme to a default core theme (like Twenty Twenty-Four) and see if you can assign the posts page.

    • If it works on a default theme, the issue points directly to a theme conflict or a template bug.
    • If it still crashes, the problem is likely a plugin conflict or your server’s PHP memory limit being maxed out.

    If you try those steps and the error remains, could you please enable debugging so we can see the exact error code?

    You can do this by adding the following code to your wp-config.php file:

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );
    define( ‘WP_DEBUG_DISPLAY’, false );

    Once added, try to assign the posts page again to trigger the crash. Then, look inside your /wp-content/ folder for a file named debug.log and paste the latest lines here. That will tell us exactly which line of code is breaking.

    Thank you!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.