detectsqlpath() worked in 1.77 but doesn't for me in 1.77b

[chufford]

I tried doing a backup for the first time since upgrading to 1.77b. At first, my attachments directory didn't allow writing so no file was created. There also was no error message. I set the permissions of attachments to 777 and then the backup would create a file, named correctly, that was empty. Further investigation showed that it was trying to execute the command 'no mysql/mysqldump ...'. It looks like the changes in the detection code works worse for me that the old code. I commented out the changes in detectsqlpath() as well as some of the changes in the $write area of editconf.php and it then worked as it did before.

I now see where I could hard-wire this path in the config.php file, but thought you'd like to know about my experience.

[BGSWebDesign]

Hi,

It doesn't work for me either... thanks for letting me know.
When will we see a fix Dean?

Peace,

[DW]

You can set the path to MySQL manually with the $sqlpath variable in config.php.

It would be good to know what works for both of you so I can see if I need to update or fix my detection code.

[chufford]

CMD=/usr/bin/mysqldump is the command that it uses successfully when I commented out the new detect code from 1.77b. For me, it looks like there may be a logic error when 'no mysql' is returned. It used 'no mysql' rather than trying the other paths.

[DW]

Can you send the output of phpinfo() on your server to my email?

Code: [Select]

<?phpphpinfo();?>

[chufford]

My phpinfo (for a limited time...)
http://www1.smartsound.com/phpinfo.php

[DW]

got it thanks