Support » Plugin: Widget Settings Importer/Exporter » Error after import "504 Gateway Time-out"

  • Resolved Alejandro Perez

    (@aleperez92)


    Here is the server log:

    [Tue Aug 30 11:59:48 2016] [warn] [client IP_ADDRESS] mod_fcgid: stderr: PHP Warning:  array_merge(): Argument #2 is not an array in /var/www/vhosts/MYDOMAIN.com/httpdocs/wp-content/plugins/widget-settings-importexport/class-widget-data.php on line 27, referer: https://MYDOMAIN.com/wp-admin/tools.php?page=widget-settings-import
    [Tue Aug 30 11:59:48 2016] [warn] [client IP_ADDRESS] mod_fcgid: stderr: PHP Warning:  array_merge(): Argument #1 is not an array in /var/www/vhosts/MYDOMAIN.com/httpdocs/wp-content/plugins/widget-settings-importexport/class-widget-data.php on line 27, referer: https://MYDOMAIN.com/wp-admin/tools.php?page=widget-settings-import
    [Tue Aug 30 11:59:48 2016] [warn] [client IP_ADDRESS] mod_fcgid: stderr: PHP Warning:  array_merge(): Argument #1 is not an array in /var/www/vhosts/MYDOMAIN.com/httpdocs/wp-content/plugins/widget-settings-importexport/class-widget-data.php on line 27, referer: https://MYDOMAIN.com/wp-admin/tools.php?page=widget-settings-import

    After importing widgets I got a “504 Gateway Time-out” error.

    Thanks!

    https://wordpress.org/plugins/widget-settings-importexport/

Viewing 3 replies - 1 through 3 (of 3 total)
  • So, what did you do in the end to resolve this issue @alejandro Perez? Just had one to doing a WordPress data import on a Vagrant Ubuntu Trellis LEMP box and want to deal with this properly.

    • This reply was modified 3 months, 1 week ago by Rhand.

    Well with:

    php_max_input_time: 300
    php_max_input_vars: 1000
    php_memory_limit: 256M

    we should be able to avoid these errors. If need be the php_max_execution_time could be made 300 as well

    Plugin Author Kevin Langley

    (@kevinlangleyjr)

    Hi @alejandro,

    I’ve just released a new version that should fix these issues for you. The 504 error is related to the memory limit and input time, but regardless, the issue is you were seeing after your timeout is fixed.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.