Fatal error after upgrading to version 1.08

  • Resolved jockev

    (@jockev)


    9 months, 1 week ago

    Hi!

    We recently tried to upgrade daext-helpful to version 1.0.8 but the new method modify_post_type_args() added in 1.0.8 returns an uncaught error expecting an array instead of an string.

    Are you aware of any compatibility issues or edge cases that could cause this?

    Best regards,
    Jocke

    Fatal error: Uncaught Error: in_array(): Argument #2 ($haystack) must be of type array, string given
in /var/www/html/web/app/plugins/daext-helpful/public/class-daexthefu-public.php on line 272

Call stack:

    in_array()
    app/plugins/daext-helpful/public/class-daexthefu-public.php:272
    daexthefu_Public::modify_post_type_args()
    wp-includes/class-wp-hook.php:310
    WP_Hook::apply_filters()
    wp-includes/plugin.php:205
    apply_filters()
    wp-includes/class-wp-post-type.php:443
    WP_Post_Type::set_props()
    wp-includes/class-wp-post-type.php:419
    WP_Post_Type::__construct()
    wp-includes/post.php:1716
    register_post_type()
    app/mu-plugins/advanced-custom-fields-pro/includes/post-types/class-acf-taxonomy.php:90
    ACF_Taxonomy::register_post_type()
    app/mu-plugins/advanced-custom-fields-pro/includes/post-types/class-acf-taxonomy.php:63
    ACF_Taxonomy::__construct()
    app/mu-plugins/advanced-custom-fields-pro/includes/acf-utility-functions.php:23
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author DAEXT

    (@daext)

    Hello jockev,

    thank you for all the details. I’ll get back to you in a couple of days.

    • This reply was modified 9 months, 1 week ago by DAEXT.
    Plugin Author DAEXT

    (@daext)

    Hello jockev,

    this error is generated when the Options -> Advanced -> Post Types option of the plugin has no post types specified. Please set at least one post types to solve.

    If you can’t access the plugin options you can manually set the daexthefu_post_types option to its default value using phpMyAdmin or similar tools.

    Default value:

    a:2:{i:0;s:4:"post";i:1;s:4:"page";}

    A check will be added in the next release to avoid generating a PHP error when this option has no post types specified.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal error after upgrading to version 1.08’ is closed to new replies.