• Resolved amslps

    (@amslps)


    Hi,

    Your plugin caused the fatal error again as your php bugs, could you fix it ASAP?

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.1.3
    Active theme: Astra Child Theme (version 1.0)
    Current plugin: Parcel Panel Order Tracking for WooCommerce (version 3.0.11)
    PHP version 8.1.19

    Error Details
    =============
    An error of type E_ERROR was caused in line 155 of the file /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Api/Configs.php. Error message: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, WP_Error given in /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Api/Configs.php:155
    Stack trace:
    #0 /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Api/Configs.php(155): json_decode()
    #1 /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Libs/Notice.php(33): ParcelPanel\Api\Configs::get_pp_notice_config()
    #2 /usr/share/nginx/wordpress/wp-includes/class-wp-hook.php(308): ParcelPanel\Libs\Notice::init()
    #3 /usr/share/nginx/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
    #4 /usr/share/nginx/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
    #5 /usr/share/nginx/wordpress/wp-admin/admin-header.php(303): do_action()
    #6 /usr/share/nginx/wordpress/wp-admin/edit-form-advanced.php(425): require_once(‘…’)
    #7 /usr/share/nginx/wordpress/wp-admin/post.php(206): require(‘…’)
    #8 {main}
     thrown

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter amslps

    (@amslps)

    But anyway, please let your CHN tech guys to check it again. Your plugin is generally good, but I don’t want to the OFTEN happened bugs to crash your plugin and your credibility!

    Thread Starter amslps

    (@amslps)

    Why there are so many bugs in your plugin?????

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.1.3
    Active theme: Astra Child Theme (version 1.0)
    Current plugin: Parcel Panel Order Tracking for WooCommerce (version 3.1.1)
    PHP version 8.1.19

    Error Details
    =============
    An error of type E_ERROR was caused in line 148 of the file /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Api/Configs.php. Error message: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, WP_Error given in /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Api/Configs.php:148
    Stack trace:
    #0 /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Api/Configs.php(148): json_decode()
    #1 /usr/share/nginx/wordpress/wp-content/plugins/parcelpanel/includes/Libs/Notice.php(34): ParcelPanel\Api\Configs::get_pp_notice_config()
    #2 /usr/share/nginx/wordpress/wp-includes/class-wp-hook.php(308): ParcelPanel\Libs\Notice::init()
    #3 /usr/share/nginx/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
    #4 /usr/share/nginx/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
    #5 /usr/share/nginx/wordpress/wp-admin/admin-header.php(303): do_action()
    #6 /usr/share/nginx/wordpress/wp-admin/edit-form-advanced.php(425): require_once(‘…’)
    #7 /usr/share/nginx/wordpress/wp-admin/post.php(206): require(‘…’)
    #8 {main}
     thrown

    Plugin Support Jessie

    (@ppjessie)

    Hi there,

    Sincerely apologize for the inconvenience caused to you.

    We will assist solve this issue through live chat, please kindly have a check in time. Much appreciated your patience and understanding!

    Kind regards, Parcel Panel

    Plugin Support Jessie

    (@ppjessie)

    Hi there,

    This issue has been solved successfully, please kindly update your version to the latest one–3.1.3.

    Sincerely apologize for the inconvenience caused to you. Any further questions please feel free to contact.

    Kind regards, Parcel Panel

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘fatal error again’ is closed to new replies.