Plugin conflict

  • Hi,

    Plugin conflict with Simple WordPress Membership (when bulk protecting pages WP Membership > Membership Levels > Tab Post Pages protection)

    Error Details

    An error of type E_ERROR was caused in line 197 of the file /var/www/vhosts/XXXX/wp-content/plugins/google-calendar-events/includes/admin/bulk-actions.php. Error message: Uncaught TypeError: explode(): Argument #2 ($string) must be of type string, array given in /var/www/vhosts/XXXX/wp-content/plugins/google-calendar-events/includes/admin/bulk-actions.php:197
    Stack trace:

    0 /var/www/vhosts/XXXX/wp-content/plugins/google-calendar-events/includes/admin/bulk-actions.php(197): explode()

    1 /var/www/vhosts/XXXX/wp-includes/class-wp-hook.php(308): SimpleCalendar\Admin\Bulk_Actions->custom_bulk_admin_notices()

    2 /var/www/vhosts/XXXX/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()

    3 /var/www/vhosts/XXXX/wp-includes/plugin.php(517): WP_Hook->do_action()

    4 /var/www/vhosts/XXXX/wp-admin/admin-header.php(303): do_action()

    5 /var/www/vhosts/XXXX/wp-admin/admin.php(239): require_once(‘…’)

    6 {main}

    thrown

    • This topic was modified 1 year, 5 months ago by gopa4.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter gopa4

    (@gopa4)

    PS: When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.2.2
    Active theme: Avada (version 7.11.0)
    Current plugin: Simple Calendar (version 3.1.43)
    PHP version 8.0.29

    Plugin Support john

    (@johnweru)

    Hi there,

    Thanks for reaching out to us.

    In regards to the issue here, please carry out the following:

    1. Navigate to the bulk-actions.php file within the wp-content/plugins/google-calendar-events/includes/admin/ directory path

    2. Alter line 197 to:

    $post_ids = $_REQUEST['ids'];

    3. Save your changes.

    Let us know if this gets to help.

    Kind Regards,

    John

    Thread Starter gopa4

    (@gopa4)

    Hello John,

    Thank you for your reply. Will it be added to the next update of the plugin? Or do I need to change it after every update?

    Plugin Support john

    (@johnweru)

    Hi there,

    Thanks for keeping in touch with us.

    In this case, I have added this issue here so that it is fixed. Unfortunately I may not be in a position to guarantee addition if this in the next update.

    Should you have any questions, please do let us know.

    Kind Regards,

    John

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