Debug logs error

  • Resolved eldorado1970

    (@eldorado1970)


    1 year, 3 months ago

    Hello,

    We are getting tons of PHP notices in the debug.log regarding to Tablepress/table already being registered in function WP_Block_Type_registry.

    We are facing some issues with sitespeed and we want to resolve the issues we are facing in the debug.log.

    What can be the issue there?

    Function WP_Block_Type_Registry::register was called <strong>wrong</strong>. Block type "tablepress/table" is already registered. Read <a href="https://www.ads-software.com/documentation/article/debugging-in-wordpress/">Debugging WordPress</a> for more information. (This entry was added in version 5.0.0.) in /home/675644.cloudwaysapps.com/pdzzxyepye/public_html/wp-includes/functions.php on line 5865
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    thanks for your post, and sorry for the trouble.

    The only instance where I have have received a similar report before was this: https://www.ads-software.com/support/topic/bug-between-tablepress-and-divi-builder-2/
    It looks like Divi Builder and the Relevanssi plugin play a role here. Are you maybe using those?

    Regards,
    Tobias

    Thread Starter eldorado1970

    (@eldorado1970)

    Hello Tobias, first I appreciate your quick reply!

    We only make use of Relevanassi, not the DIVI builder. In the Relevanassi settings I changed in the settings the following from “checked” to “unchecked”:

    Expand Shortcodes?Expand shortcodes when indexing

    Is this the part you meant? I couldn’t find any mentioning of tables within the plugin.

    Thanks!

    Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    Ok, then this is indeed caused by Relevanssi, as in that other thread.

    Unfortunately, I’m not familiar with its settings or config options, so that I don’t know if they actually offer a setting here.

    However, I do remember that they needed to add code specific to TablePress a long while ago. After some changes in WordPress (a year ago or so), those should however no longer be needed. It might therefore be the best to get in touch with the Relevanssi team and ask them to review that.

    Regards,
    Tobias

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Debug logs error’ is closed to new replies.