• Hi,
    If you had this problem (after wordpress automatically updated to version 6.2.6), try this: delete the lines from 600 to 604 (on my site, look for the lines to delete in yours) from the file wp-includes/default-filters. php and everything works again!

    these are the lines to delete:

    // Footnotes Block.

    add_action( ‘init’, ‘_wp_footnotes_kses_init’ );

    add_action( ‘set_current_user’, ‘_wp_footnotes_kses_init’ );

    add_filter( ‘force_filtered_html_on_import’, ‘_wp_footnotes_force_filtered_html_on_import_filter’, 999 );

Viewing 3 replies - 1 through 3 (of 3 total)
  • I would recommend not following this advice. For 2 reasons:

    • You should NEVER customize WordPress core files.
    • The cause of the problem was recognized a long time ago. It is not in WordPress but is caused by the Patchman software. Details here in the ticket: https://core.trac.www.ads-software.com/ticket/61489 – updating to the latest version of Patchman BEFORE the update should already help to avoid running into this error.
    Thread Starter Marcella

    (@marcisigno)

    @threadi

    but the problem arose with the automatic update of wordpress: two of the sites I had created had the critical error and there was no other solution than to downgrade to the previous version of wordpress. By deleting the lines of the footnote block, however, I managed to have the site accessible again, both in the frontend and in the backend, in a few minutes. Without having other problems later

    Please read through the above ticket. A Patchman employee describes the background of the problem there.

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