[solved]MySQLDumper 1.24.4

[sunrisecc]

Is anyone using MySQLDumper 1.24.4 under XAMPP 1.77?

By luck, I checked the php error log and found that whenever I do a backup, I get a double entry in php_error.log showing the following:

PHP Warning: Cannot modify header information - headers already sent in D:\xampp\htdocs\msd\dump.php on line 452

The backup is successful and restores do not generate any warnings.

I have done a test second install of MSD and the errors are there. On my live host, no warnings are generated.

I am just curious if this is happening to anyone else.

I am communicating with the author of MSD.

[Altrea]

Hi sunrisecc (there is ALWAYS time for a short salutation, especially if you are asking for help at a community board. It's a matter of politeness),

I am using MySQLDumper, but not with XAMPP 1.7.7 but with XAMPP 1.7.3.

Please try one thing: Edit your \xampp\php\php.ini and change one setting

Code: Select all

;find
error_reporting = E_ALL | E_STRICT

;replace with
error_reporting = E_ALL & ~E_NOTICE

Maybe there is a E_STRICT message producing this aftereffect.

best wishes,
Altrea

[sunrisecc]

Hi Altrea:

I made the change as suggested. However the same two warnings were produced. I have reverted the php.ini file for now.

The irony is that if I had not checked the php_error_log, I would have never known about the warnings. There are no other errors other than when I do a backup with MSD.

Thank you for your suggestion.

[Altrea]

However the same two warnings were produced.

Have you restarted your Apache after the change?
php.ini changes just takes effect after Apache restart.

best wishes,
Altrea

[sunrisecc]

Have you restarted your Apache after the change?
php.ini changes just takes effect after Apache restart.

Yes, I even just did it again withe same results.

[JJ_Tagy]

Sounds like a bad script. I've never used whatever it is you are using, but it looks like a block wasn't properly exited out of or something because it is trying to load one page on top of an existing page when the header was already called.

[sunrisecc]

The problem is definitely within the interface of XAMPP 1.77 and MSD. On the MSD board, no one has run into the problem. I also use MSD on live servers with nary a problem.

[Altrea]

I will test msd on my Zend Server instances to check if it can be a XAMPP issue.
Since now i believe it is a msd issue, which is very confusing, because msd makes use of output buffering, so normally there is no way to output content and produce that issue

[sunrisecc]

Altrea:

Thank you for your help. I am following the topic on the MSD forum.

[Altrea]

Here is the link to the thread in the MySQLDumper Board: http://forum.mysqldumper.de/modify-head ... t6636.html
It does not affect the functionality of MySQLDumper and will not be fixed by the programmer before the next major release which is a complete redesign.
So i think we will mark this topic as solved even if it will not be really solved.

best wishes,
Altrea