MySQLDumper 1.24.4 released / EN

Posted: 2011-01-24, 22:39 MySQLDumper 1.24.4 released / EN

Dear MySQLDumper-User,

just 1 week after the last release we had to react because there is a bug in version 1.24.3 which is related to Perl. If you are using the Perl script crondump.pl we recommend to update your files.
After uploading please go to the configuration, click the button "cronscript" and check your settings. After saving the configuration profile everything is up to date again.

Download

How do I have to do an update?
When you update from version 1.24, 1.24.2 or 1.24.3 you can simply copy the files from the unpacked zip file to your server (but keep your config.php file on the server - don't overwrite it!). If you had to move the Perl scripts to a cgi-bin folder, don't forget to do it again (there are changes in the Perl script).

If you want to update from an older version of MySQLDumper, please do a clean and fresh installation into another directory. If everything is working you can delete the old directory - otherwise you'll have that as a fallback.

With this version we addressed the following issues:

- General: If "inc" was anywhere in the path or the domain to the MySQLDumper-Root-Diretory the file runtime.php couldn't be included.
- Configuration: When saving the Perl configuration file, the selected databases to be backed up have been saved incorrectly.
- Home / directory protection: At creating the protection PHP-Warnings were shown if running PHP lower than 5.3.0.
- Perl: Some cosmetic changes in output
- Perl: Write "DROP VIEW" instead of "DROP TABLE" to backup file if table is a view.
- Perl: Added type of table to log output.

Best regards from your
MySQLDumper-Team

If any question comes up, feel free to ask us here.

**first backups** Joined: 09 Dec 2009 Posts: 1

I am using Windows 2003 with XAMPP and tried configuring an automated backup to be FTP-ed into another server using Perl. However, MySQLDumper is giving me the below error:

MySQLDumper - Perl CronDump [Version 1.24.4 (using perl v5.10.1)]
Software error:
Insecure dependency in eval while running with -T switch at C:/xampp/htdocs/msd/cgi-bin/crondump.pl line 231, <CONFIG> line 18.
For help, please send mail to the webmaster (webmaster@localhost), giving this error message and the time and date of the error.

What should I do? Please help.

Posted: 2011-01-25, 19:00 (No subject)

Configure Perl to not run with T-Switch.

**knows MySQLDumper** Joined: 02 Oct 2010 Posts: 5

The homepage says New Version 1.24.4 was released in Jan 2010 instead of 2011! Laughing

Posted: 2011-03-18, 23:56 (No subject)

**knows MySQLDumper** Joined: 27 Jan 2010 Posts: 4

DSB,

Although I don't use MySQLDumper as much as I should. I decided to to the upgrade a few linux sites to 1.24.4. They worked fine except for the one I had problems with last year.

see: http://forum.mysqldumper.de/couldn-t-read-runtime-php-version-1-24-stable-t5197.html

Got some errors so I did a clean install of 1.24.4

"inc" is still stripped out of incircle .. see red area in error below:

Problem back;
Warning: opendir() [function.opendir]: open_basedir restriction in effect. File(/home/ircle/public_html/msd/language/) is not within the allowed path(s): (/home/incircle:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/incircle/public_html/msd/inc/functions_global.php on line 810

Warning: opendir(/home/ircle/public_html/msd/language/) [function.opendir]: failed to open dir: Operation not permitted in/home/incircle/public_html/msd/inc/functions_global.php on line 810

Warning: readdir(): supplied argument is not a valid Directory resource in /home/incircle/public_html/msd/inc/functions_global.phpon line 813

My apologies for not digging deeper.. but figured I should at least let you know about this.

PS. I put my slightly hacked 1.24 stable back and it works no problem.

Posted: 2011-03-25, 00:05 (No subject)

Thank you for this information. I thought, that we carried the fix from 1.24 over to version 1.24.4. But your output proofs that obviously we made a mistake in this point.
Nevertheless, we are currently working on MySQLDumper version 2, which is redesigned from scratch and doesn't suffer from this issue. We stopped working on the 1.24 series and won't continue maintaining 2 totally different branches of the script. So as long as you can live with version 1.24 everything is fine. Wink

**knows MySQLDumper** Joined: 27 Jan 2010 Posts: 4

Thanks for prompt reply DSB,

No problem using 1.24 stable.

Looking forward to Version 2!

Gruß, Peter