• Sometimes getting the following PHP error while working in the wordpress admin panel:

    Uncaught TypeError: explode(): Argument #2 ($string) must be of type string, array given in wp-content/plugins/google-calendar-events/includes/admin/bulk-actions.php(204): explode(',', Array)

    It seems to come from function custom_bulk_admin_notices (line 204).

    Plugin version: 4.0.3

    • This topic was modified 2 days, 10 hours ago by tmumaster.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support john

    (@johnweru)

    Hi there,

    Thank you for bringing this to our attention.

    In this regard, I have tried to reproduce the issue on my end using the latest version of the plugin and PHP 8.5, but so far I haven’t been able to trigger the error.

    For testing purposes upon fixing the issue, could you please provide us with the following information:

    • Your PHP version
    • The exact steps you are taking when the error occurs, or a screencast demonstrating this

    In the meantime, I will notify the development team about it so that it is fixed.

    Kind Regards

    Thread Starter tmumaster

    (@tmumaster)

    Thank you for looking into this!

    Environment:
    WordPress: 7.0
    PHP: 8.3.31
    Theme: Academica 2.1.3

    The error started happening when working with the settings of an unrelated plugin: “Simple Membership Plugin” (simple_wp_membership). Any changes under “Category Protection” triggers the WP error “Your site hit a critical error. Suspected plugin: Simple Calendar 4.0.3” and the “Uncaught TypeError: explode()” error in wp-content/plugins/google-calendar-events/includes/admin/bulk-actions.php(204) as described in the original post.

    Looking at the Simple Calendar code:

    https://plugins.trac.wordpress.org/browser/google-calendar-events/trunk/includes/admin/bulk-actions.php

    it seems the function custom_bulk_admin_notices() is triggered as a add_action(admin_notices) hook. Perhaps in this case the variable “ids” is an array instead of a string as expected by the explode() function.

    Plugin Support john

    (@johnweru)

    Hi there,

    Thanks for sharing this information.

    In this case, I was in a position to replicate the issue. I have hence gone ahead and notified the development team about this.

    We will keep you posted as soon as a fix is ready.

    Kindly bear with us in the meantime.

    Regards

    • This reply was modified 1 day, 3 hours ago by john.
Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.