vtiger

[philip]

Hi,

After much delay vtigercrm 4.2.4 has been released.

This is the first community driven release, so a big thanks goes out to all the people involved in making this happen. Our Special Thanks to MFedy K and Allan Bush.

This is mostly a bug fix release, but it does mark the first release using the new SVN/Trac system which helps us harness the power of the community contributions and track issues and their fixes so everyone can help out. The trac system can be seen here: http://vtiger.fosslabs.com

A list of fixed bugs can be seen using the trac ticket system here:
http://vtiger.fosslabs.com/cgi-bin/trac.cgi/query?status=closed&milestone=4.2.4&order=priority

A full changelog can be seen trough the trac svn log here:
http://vtiger.fosslabs.com/cgi-bin/trac.cgi/log/vtigercrm/tags/vtigercrm-4.2.4?action=stop_on_copy&rev=6885&stop_rev=&mode=follow_copy&verbose=on

vtigercrm 4.2.4 can be downloaded here:

http://www.vtiger.com/download/vtigercrm-4.2.4.exe
http://www.vtiger.com/download/vtigercrm-4.2.4.bin
http://www.vtiger.com/download/vtigercrm-4.2.4.tar.gz
http://www.vtiger.com/download/vtigercrm-phpdocs-4.2.4.zip

For a new installation simply extract the files into a directory accessible through your apache setup then point your web browser to that directory on your website and follow the installation instructions. Software you'll require is apache (1.3.x or 2.x) with php (4.3+, no 5.x support yet) and mysql (4.x).

You can post any issues or suggestions at http://vtiger.fosslabs.com/cgi-bin/trac.cgi/newticket


UPGRADING

If you are upgrading from a previous version of vtigercrm first backup all data then follow the instructions for the appropriate version below:

4.2.3:
- No database changes are need if you are using a seccessfull installation.
- If tables were only partially created for you using an earlier version please wipe your database and try with 4.2.4, your problems should be solved.
- To save your current configuration copy the config.php file from your old installation to config.inc.php in the new installation. You'll also have to edit the config file as follows:
- change the following variable names in config.php

from:
$dbconfig['db_host_name'] =
$dbconfig['db_user_name'] =

to:
$dbconfig['db_hostname'] =
$dbconfig['db_username'] =

- If your 4.2.3 installation has previously been upgraded from an earlier release there is one database modification missed in pervious upgrades you will want to make manually:
alter table wordtemplates drop primary key;
alter table wordtemplates change filename filename varchar(100) not null;
alter table wordtemplates add column templateid integer(19) primary key;


4.2.2 (aka 4.2 patch2):
- Apply the 4.2.3 patch as per: http://forums.vtiger.com/viewtopic.php?t=4166
- Then follow the instructions for a 4.2.3 upgrade.


4.2.1 or 4.2:
- Apply the 4.2.2 patch as per: http://forums.vtiger.com/viewtopic.php?t=2903
- Then follow the instructions for a 4.2.2 upgrade.


Philip

[khaverblad]

philip wrote: 4.2.3:
- No database changes are need if you are using a seccessfull installation.
- If tables were only partially created for you using an earlier version please wipe your database and try with 4.2.4, your problems should be solved.
- To save your current configuration copy the config.php file from your old installation to config.inc.php in the new installation. You'll also have to edit the config file as follows:
- change the following variable names in config.php

from:
$dbconfig['db_host_name'] =
$dbconfig['db_user_name'] =

to:
$dbconfig['db_hostname'] =
$dbconfig['db_username'] =

- If your 4.2.3 installation has previously been upgraded from an earlier release there is one database modification missed in pervious upgrades you will want to make manually:
alter table wordtemplates drop primary key;
alter table wordtemplates change filename filename varchar(100) not null;
alter table wordtemplates add column templateid integer(19) primary key;

Got couple of questions based on above upgrade instructions that could be a bit more clear, so got some few questions:

1) What should I download; the full 4.2.4 package?

2) First it says that no database changes is needed, but needed if partially created - who would one know? I'm running with 4.2.3 that has been upgraded from 4.01 to 4.2 and then added with patch2 and vulnerability patch. So according to the documentation it should be a fully 4.2.3 version. So the instruction is kind of fuzzy and running around in circles....

3) An further down it says there is one database modification missed in pervious upgrades - has there been released a fix for this? Really you should; if there is a flaw, bug or whatever discovered there should be released a fix! This I think would at least also let you guys publish some easier upgrade instructions. Reading around I found that there are quite a few questions about how to do the upgrade due to confusing upgrades instructions. Suggestion would be to have a team testers that give you feedback on how easy the instructions worked out.

While on the topic for upgrades and patches; but are there any kind of mailinglist or alert service available to get the latest info about released upgrades, patches and new versions?

Keep up the great work you have done so far.