An error of type E_ERROR was caused

  • Resolved ymorin007

    (@ymorin007)


    1 year, 8 months ago

    I get the following error when I upgraded from PHP 7.4 to PHP 8.0

    WordPress version 6.2.2
    Current plugin: Pods – Custom Content Types and Fields (version 2.9.16)
    PHP version 8.0.27

    Error Details
    =============
    An error of type E_ERROR was caused in line 598 of the file /var/www/wp-content/plugins/pods/src/Pods/Wisdom_Tracker.php. Error message: Uncaught TypeError: Cannot access offset of type string on string in /var/www/wp-content/plugins/pods/src/Pods/Wisdom_Tracker.php:598
    Stack trace:
    #0 /var/www/wp-includes/class-wp-hook.php(308): Pods\Wisdom_Tracker->set_notification_time(”)
    #1 /var/www/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
    #2 /var/www/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #3 /var/www/wp-admin/admin-ajax.php(45): do_action(‘admin_init’)
    #4 {main}
      thrown

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    I’ll look into this and see what would be causing this unexpected error here. That issue shouldn’t be happening because the variable that causes it should have always been a string in most cases.

    Thread Starter ymorin007

    (@ymorin007)

    I forgot to say that I only seems to get this error when I visit the plugins page (/wp-admin/plugins.php)

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    I have a fix for this in Pods 2.9.17 which will be released in the next few days.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘An error of type E_ERROR was caused’ is closed to new replies.