Page 1 of 1

MySQL dump module with CMSMS 1.11.6

Posted: Wed May 15, 2013 2:24 am
by casidougal
CMS Version 1.11.6
MysqlDump 1.2.4
PHP Version 5.3.21
Server Database (server_db_type) mysql (mysqli) 5.0.96
Server Software (server_software) apache
Server Operating System (server_os) linux 2.6.32-358.0.1.el6.x86_64 on x86_64
Hosted on GoDaddy shared hosting account Hosting Configuration 2.2

Hi,

I just installed 1.11.6 and the most recent MySQL dump module 1.2.4.

The module seems to be working but On the Preferences screen there are four warnings as listed below. Does anyone know what's going on with this and if this will cause problems at some point down the road with the backups? Is there a way to resolve these warnings? Thank you very much in advance!

I've installed quite a few CMSMS sites all with the MySQL dump module. The last version I had done installs on was 1.11.4 and I didn't get these warnings.

Code: Select all

Warning: mysql_get_server_info() [function.mysql-get-server-info]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /home/content/77/11093477/html/modules/MysqlDump/MysqlDump.module.php on line 340

Warning: mysql_get_server_info() [function.mysql-get-server-info]: A link to the server could not be established in /home/content/77/11093477/html/modules/MysqlDump/MysqlDump.module.php on line 340

Warning: mysql_get_server_info() [function.mysql-get-server-info]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /home/content/77/11093477/html/modules/MysqlDump/MysqlDump.module.php on line 90

Warning: mysql_get_server_info() [function.mysql-get-server-info]: A link to the server could not be established in /home/content/77/11093477/html/modules/MysqlDump/MysqlDump.module.php on line 90
Also, when I execute a backup I get the following messages:

Code: Select all

Warning: mysql_real_escape_string() [function.mysql-real-escape-string]: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /home/content/77/11093477/html/modules/MysqlDump/MysqlDump.module.php on line 396

Warning: mysql_real_escape_string() [function.mysql-real-escape-string]: A link to the server could not be established in /home/content/77/11093477/html/modules/MysqlDump/MysqlDump.module.php on line 396
Task started

Deprecated: Function eregi_replace() is deprecated in /home/content/77/11093477/html/modules/MysqlDump/MysqlDump.module.php on line 439

Re: MySQL dump module with CMSMS 1.11.6

Posted: Wed May 15, 2013 5:13 pm
by Dr.CSS
There is a very good chance it doesn't work with the latest CMSMS...

Last Release Date: 2009-08-23 (45 months ago)

Re: MySQL dump module with CMSMS 1.11.6

Posted: Wed May 15, 2013 5:52 pm
by Rolf
Last Commit Date: 2011-02-14 (27 months ago)

Re: MySQL dump module with CMSMS 1.11.6

Posted: Wed May 15, 2013 6:41 pm
by casidougal
Is anyone aware of any other "one click" database backup solutions for CMSMS 1.11.6?

This is a great solution for our sites because non-techncial content mangers can click the MySQL dump backup before making changes . . . doesn't involve having to go through cpanel or phpMyAdmin.

Re: MySQL dump module with CMSMS 1.11.6

Posted: Wed May 15, 2013 6:58 pm
by calguy1000
The problem is probably because
a: that module uses mysql_ functions directly, which rely on a 'current' mysql connection
b: new installs of CMSMS use 'mysqli_' because mysql_ functions were deprecated
(see it's not just you guys that have to deal with that stuff.. you're just at the end of the chain).

BTW I noticed when I looked through the code
1: the module doesn't do proper checks to see if it's possible to use those functions
(it could be checking a config value, and producing an error).
2. The module uses the ereg functions which were deprecated long ago
3. The module uses 'shell commands' which are not supported on many shared hosts (this is one place where blocking some php functions is a good thing to do on shared hosts).

Also:

Another developer can't just 'change' that module, and make it available to everybody. We respect copyright, authors workflow, and their design and intent for a module. Therefore the other developer must either get the approval of the module author, OR fork the module.

If you hire somebody to make changes, and that somebody doesn't have the approval of the module author (for whatever reason), then the only solution is to fork.

If the hired developer doesn't fork the module on the forge, and just gives you a 'fixed' .xml or .tar.gz file, then you essentially have a custom module that you are responsible for. This may be a good thing, or a bad thing, depending on your needs.

Re: MySQL dump module with CMSMS 1.11.6

Posted: Wed May 15, 2013 7:17 pm
by casidougal
Thank you for the response and the insight on this topic. I agree that the authors copyright should be respected.

I will make sure and pass that info along to a developer if I'm able to hire someone to assist in this.

BTW, I posted this in the commercial section . . . I'd be interested in getting an estimate from anyone who is qualified and interested. Thanks!