PHP warning during update

  • Resolved iamjanco

    (@iamjanco)


    8 years ago

    Just tested the latest update (1.3.9) on our WPengine staging area and getting three errors that repeat themselves quite a few number of times, all the same PID. PHP in use is v7.0.x, latest Core, everything else is current:

    PHP Warning: explode() expects parameter 2 to be string, array given in /nas/content/staging/texasfinaldriv/wp-content/plugins/woocommerce-xml-csv-product-import/plugin.php on line 266, referer: http://texasfinaldriv.staging.wpengine.com/wp-admin/plugins.php
    PHP Warning: in_array() expects parameter 2 to be array, null given in /nas/content/staging/texasfinaldriv/wp-content/plugins/woocommerce-xml-csv-product-import/plugin.php on line 267, referer: http://texasfinaldriv.staging.wpengine.com/wp-admin/plugins.php
    PHP Warning: in_array() expects parameter 2 to be array, null given in /nas/content/staging/texasfinaldriv/wp-content/plugins/woocommerce-xml-csv-product-import/plugin.php on line 270, referer: http://texasfinaldriv.staging.wpengine.com/wp-admin/plugins.php

    Any ideas?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WP All Import

    (@wpallimport)

    8 years ago

    Hi @iamjanco

    We’ll need to have a look on your site in order to understand why this PHP warning is happening. Please open a ticket with more details on the issue at http://www.wpallimport.com/support/.

    Thread Starter iamjanco

    (@iamjanco)

    8 years ago

    After performing additional updates that have been released since this ticket was submitted, the PHP compatibility issue appears to be fixed. Fyi, the plugin used to test the PHP was the PHP Compatibility Checker by WPengine.

    Thanks for the response, but no further help is needed at this time.

    • This reply was modified 8 years ago by iamjanco. Reason: spell check, added link
Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘PHP warning during update’ is closed to new replies.

  • 2 replies
  • 2 participants
  • Last reply from: iamjanco
  • Last activity: 8 years ago
  • Status: resolved