WordPress.org

Support

Support » Plugins and Hacks » [Resolved] set_time_limit and "headers already sent" errors when .sql download begins

[Resolved] set_time_limit and "headers already sent" errors when .sql download begins

  • Migrate DB is the only plugin installed and activated on a fresh install of WP 3.9.1 but I’m seeing errors when the download is initiated.

    Warning: set_time_limit() has been disabled for security reasons in /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php on line 771
    Warning: Cannot modify header information – headers already sent by (output started at /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php:771) in /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php on line 775

    Warning: Cannot modify header information – headers already sent by (output started at /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php:771) in /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php on line 776

    Warning: Cannot modify header information – headers already sent by (output started at /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php:771) in /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php on line 777

    Warning: Cannot modify header information – headers already sent by (output started at /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php:771) in /home/carisouv/public_html/wp-content/plugins/wp-migrate-db/wp-migrate-db.php on line 778

    Followed by a dump of the SQL in the browser.

    Checked my PHP config and safe_mode is off. Any advice on what I should look at next?

    https://wordpress.org/plugins/wp-migrate-db/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi ajfleming,

    This has been corrected in our development code and will be available in the next public release of the plugin.

    Apologies for the inconvenience.

    Cheers,

    Chris

    Great! Thanks Chris.

    If any others read this befor the next public release, you can work around the problem by unchecking the Save file to your computer option, and then using the download link on the following confirmation page.

    I have fixed it commenting line 771
    //set_time_limit( 0 );

    is it ok?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Resolved] set_time_limit and "headers already sent" errors when .sql download begins’ is closed to new replies.