OK... it needs to be documented somewhere at a minimum. Are those the only
changes that someone would need to do upgradeing from 4.2.x to 4.2.4? I
think so, but am not certain. I can build the updater for 4.2.5.<br /><br
/>> Brian Devendorf wrote:<br />> <br />>>Want to run an idea
past everyone...<br />>><br />>>When someone updates from
v4.2.3 to v4.2.4, they will need to update<br />>>their config.php.
At a minimum they need to change:<br />>> $dbconfig['db_host_name']
=<br />>> $dbconfig['db_user_name'] =<br />>>To:<br
/>>> $dbconfig['db_hostname'] =<br
/>>> $dbconfig['db_username'] =<br />>><br />>>Should
this be accomplished in the index.php... if it doesn't see a<br
/>>>db_hostname, check for db_host_name. If that exists, launch
4.2.3 to<br />>>4.2.4 upgrade routine (currently just changing those
two entries).<br />>><br />>>Does this sound like a good idea?
Anyone have any better idea?<br />>><br />>><br />> We can
do that in 4.2.5, but for 4.2.4 it will just be some if<br />>
(!isset()) calls in index.php.<br />> <br />> Mike<br />>
_______________________________________________<br />> This vtiger.com
email is sponsored by: Zoho Writer. Are you still using<br />> your
desktop word processor for typing documents? Try the AJAX enabled,<br
/>> collaboration-friendly online word processor, Zoho Writer for
FREE<br />> instead!<br />> http://zohowriter.com/?vt<br />>