• Three of my WordPress sites are reporting critical errors after the automatic update (presumably to 6.4.1). The error is (copied from error_log, but I have replaced the long path with …)

    [08-Nov-2023 10:53:31 UTC] PHP Fatal error: require(): Failed opening required ‘/home/…/wp-includes/html-api/class-wp-html-unsupported-exception.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in /home/…./wp-settings.php on line 242

    The directory home/…/wp-includes/html-api only has the following 4 files; it does not include the “class-wp-html-unsupported-exception.php” file referred to above:

    class-wp-html-attribute-token.php
    class-wp-html-span.php
    class-wp-html-tag-processor.php
    class-wp-html-text-replacement.php

    The wp-settings.php file (updated on 8 Nov 2023) lists many more required files:

    require ABSPATH . WPINC . ‘/html-api/class-wp-html-attribute-token.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-span.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-text-replacement.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-tag-processor.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-unsupported-exception.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-active-formatting-elements.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-open-elements.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-token.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-processor-state.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-processor.php’;

    The Github repository shows these new files under the 6.4.1 tag, including the “class-wp-html-unsupported-exception.php” file that I do not have.

    My only WordPress site that is still working (hbcc.net.nz) has not yet updated (version = 6.2.3, and wp-settings.php has not been updated since April 2023). The hbcc.net.nz wp-settings.php file lists only four files required in this html-api directory (being the only four files I have in the site that is now giving the critical error), being:

    require ABSPATH . WPINC . ‘/html-api/class-wp-html-attribute-token.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-span.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-text-replacement.php’;
    require ABSPATH . WPINC . ‘/html-api/class-wp-html-tag-processor.php’

    I note that the GitHub 6.2.3 tag only shows these same four files, suggesting the extra files are new for 6.4.1.

    I am running all four WordPress sites on GoDaddy under cPanel. I run WordFence, Easy Updates Manager, plus a number of other plugins

    Why have my sites not downloaded what appear to be new files required in the html-api directory?

    Can I just copy the files from the GitHub site under the “6.4.1” tag?

    Thanks,

    Andrew

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hello @amas008,

    The scenario is not listed here, So can you please write how I can generate the same critical bug?

    Also, are you getting an error on restoring older sites?

    Thread Starter amas008

    (@amas008)

    I did nothing to create this error; it was the result of a failed automatic update. I cannot access the site to try to restore it except by FTP; disabling plugins has no effect because the problem is in the core WordPress files.

    Thread Starter amas008

    (@amas008)

    I have now checked the version.php file, and it shows at least one of my “critical error” sites as being version: $wp_version = ‘6.3.2’;

    You have to update the WordPress version. for that follow the following steps

    Please take the backup of your website folder from files manager first before proceeding to the following steps

    1. except for wp-content, .htaccess, and wp-config, delete all files and folders
    2. download lates WordPress version
    3. extract and open the downloaded WordPress. except for wp-content, copy all the files and folders
    4. paste the copied files and folders in you website’s folder.
    5. after that open wp-admin on the browser. instead of login page, they will ask to update the WordPress version. update it. then login to your wp-admin

    Hope that’ll help

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Critical Error: Missing multiple wp-includes/html-api/ files’ is closed to new replies.