Activating the plugin on 5.3 beta3 produces PHP warnings

  • Resolved skaras

    (@skaras)


    5 years, 5 months ago

    I tried the beta3 version of wordpress 5.3 today with the latest coblocks version.
    When coblocks is activated, each admin page produces lots of php warnings in DEBUG mode. The frontend doesn’t seem to be affected. After deactivating the plugin again, everything works.

    Here is a list of the php warnings/errors:
    Warning: array_slice() expects parameter 2 to be integer, string given in xxxx/wp-admin/includes/plugin.php on line 1392

    Warning: array_merge(): Argument #2 is not an array in xxxx/wp-admin/includes/plugin.php on line 1396

    Warning: ksort() expects parameter 1 to be array, null given in xxxx/wp-admin/includes/plugin.php on line 1401

    Warning: Cannot modify header information – headers already sent by (output started at xxxx/wp-admin/includes/plugin.php:1392) in /var/www/mra/wp-includes/functions.php on line 5939

    Warning: Cannot modify header information – headers already sent by (output started at xxxx/wp-admin/includes/plugin.php:1392) in /var/www/mra/wp-admin/includes/misc.php on line 1252

    Warning: Cannot modify header information – headers already sent by (output started at xxxx/wp-admin/includes/plugin.php:1392) in /var/www/mra/wp-admin/admin-header.php on line 9

    I understand that these are only warnings and not real errors. But this makes using the plugin in DEBUG mode (WP_DEBUG true) impossible

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Anthony Ledesma

    (@paranoia1906)

    Hi @skaras,

    Thank you for making this report. I am having trouble replicating the issue. What version of PHP are you running when receiving this error?

    Best,

    Anthony

    Thread Starter skaras

    (@skaras)

    Thanks for responding to this @paranoia1906

    I have to make a correction to my report: the warning appear if PHP display_errors is on, regardless of WP_DEBUG

    I use PHP version 7.2.23 on CentOS (remi packages).
    And the beta version of WordPress 5.3.

    So, if php display_errors is on AND CoBlocks is activated, I get the following warning at the top of the WordPress backend.

    Warning: array_slice() expects parameter 2 to be integer, string given in xxx/wp-admin/includes/plugin.php on line 1392
Warning: array_merge(): Argument #2 is not an array in xxx/wp-admin/includes/plugin.php on line 1396
Warning: ksort() expects parameter 1 to be array, null given in xxx/wp-admin/includes/plugin.php on line 1401

    If I deactivate CoBlocks, the warnings disappear.

    Other plugins I have activated on my installation are

    • Advanced Custom Fields PRO
    • Post Duplicator
    • Post Types Order
    • WordPress Beta Tester
    • WordPress Importer
    Plugin Author Anthony Ledesma

    (@paranoia1906)

    Hi @skaras,

    Thank you for making this support request. I have put in a pull request to the official CoBlocks GitHub which will resolve this issue. You can track our progress here: https://github.com/godaddy/coblocks/pull/985

    Best regards,

    Anthony

    Plugin Author Anthony Ledesma

    (@paranoia1906)

    Hi @skaras,

    I wanted to followup and let you know that this issue is now resolved and we have merged a fix into the official CoBlocks GitHub. We will have this fix released with the next update of CoBlocks. Please let us know if you have any further contributions.

    Best regards,

    Anthony

    Thread Starter skaras

    (@skaras)

    thank you for resolving this so quickly and for the great feedback on this forum post.
    I’ll try it out as soon as the new version is published

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Activating the plugin on 5.3 beta3 produces PHP warnings’ is closed to new replies.

Tags