Main Page | About | Help | FAQ | Special pages | Log in
	Printable version | Disclaimers | Privacy policy

Vtiger CRM 5.0.4 - Release Notes

From vtiger.com

Contents 1 5.0.4 Overview 2 Software Requirements 2.1 Important Note 3 MySQL Configuration 4 Features & Enhancements 5 Bug Fixes 6 Integrated Patches 7 Known Issues 8 Limitations 9 Migration Steps 9.1 To Migrate from 5.x versions 9.2 To Migrate from 4.2.x versions 10 Modified Tables after 5.0.3

[edit] 5.0.4 Overview

5.0.4 is mainly a bug fix release. The main highlight of the release is security and UTF-8 support in most of the product, except for some parts of dashboard.

Over 900 bug fixes, 50 patches and few minor feature enhancements have been incorporated in this release.

[edit] Software Requirements

Apache: v2.0.40 and above
MySQL: v4.1.x – v5.1.x
PHP: v5.0.x – v5.2.x

[edit] Important Note

1. vtiger CRM 5.0.4 does not work with PHP 4.x version. For more information look here

2. Please remove, 'STRICT_TRANS_TABLES' from the 'SQL MODE'. Otherwise, you may face issues with saving data.
For more details on how to set SQL_MODE, please refer to: http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html

[edit] MySQL Configuration

If you are using an existing MySQL database (instead of the one bundled in the EXE/bin downloads), please make sure that UTF-8 support is enabled in MySQL.

The MySQL database that has been bundled in the EXE and bin files has already been pre-configured for UTF-8 support. So, if you are using the bundled database then no changes are necessary.

Note: Please remove, 'STRICT_TRANS_TABLES' from the 'SQL MODE'. Otherwise, you may face issues with saving data.

[edit] Features & Enhancements

Following feature enhancement requests have been addressed in 5.0.4. Please click the ticket id for additional details.

1510 Contacts, leads - always drops back to first page of list

3230 Multiple Attachments not supported

4107 provide delete option for related to field(contact) in calendar.

4109 Accounts -vs- Contacts and saving emails sent?

4131 HTML Based E-mail Templates

4175 Email notification when User is added

3907 Firefox : Small note description

4075 Ability to change default mysite page

3013 Allow multiple attachments when sending emails.

4118 Order filter name alphabetically

4183 & 4382 Import/Export functionalities for Trouble Tickets & Vendors module

38557 Accounts > Mailer Export : Exports contacts (depending on search criteira) from the Accounts from a previous search into a CSV.

2607 Selective Export : Export the selected records.

4131 HTML Based E-mail Templates

- StandardUser configuration in installation : During Vtiger installation, we now provide a feature to set the configuration for StandardUser also, similar to the Admin user.

- Role based PickList : Picklist values can now be defined based on roles. So different set of picklist values can be assigned, for all the modules, based on User roles.

- Firefox plug-in dynamic Role based PickList for Trouble Tickets : Picklist values for Trouble tickets can be defined based on roles.

- Send Mail option has been added to send mass mail to Campaigns related Leads/Contacts ( From Related list view )

[edit] Bug Fixes

We have fixed about 900+ issues in the 5.0.4 release. Here are the Top 10 bug fixes:

2051 Always problem with accents

2107 Huge security hole

2196 Inconsitency in charset (UTF-8)

3952 Migration problem from 5.03RC2 to latest SVN

4050 Error on lead conversion

4201 Version need to be changed

2214 i18n issue with picklists

2590 Saved picklist value not remained when edit

2620 UTF-8 support for Notifications and report folder name

3728 Webmail -->attachment img not forwad to another mails

For more, please see this Trac report of issues fixed in 5.0.4.

[edit] Integrated Patches

We have integrated around 50 patches in 5.0.4 release. Here are a few of them:

3283 i18n issue at calendar (all events and tasks)

2279 Role assignment upon user creation broken

2318 RTF document merge instead of word merge

2346 Calendar Week View Action button displays improperly

2350 Navigation dropdown problem in IE (and Safari?)

2404 Problem with HTML Tags in AltBody(Text) on Email, (umlaute)

2730 Problem in Search and Tag Search when modules are disabled for a profile

3004 patches to log entries for php 5.2

3719 Error causing blank screen problem - fix

3832 picklist encoding problem

For more, please see this Trac report of patches integrated in 5.0.4.

[edit] Known Issues

We have about 150 issues to be fixed. For complete details, please see this Trac report of Known issues in 5.0.4.

1. Some of the UTF-8 character will not be supported in Outlook (English/US Installation) , So that some values may get disturbed.
2. Some of the UTF-8 character will not be supported in Office Plugin (English/US Installation), So that some values may get disturbed.
3. In Mail merge the values with tags or in symbol "<>" will not merge properly.
4. Some Special chars not getting displayed correctly in dashboard.
5. Office & Outlook plugins will not work properly with office 2007 and outlook 2007.
6. Field length validation is not available.
7. System details information will not be complete, if operating system applies restriction.
8. Created Time and Modified Time depends on the timezone format set in php configuration or server.
9. Pagination is not supported in Global Search.

[edit] Limitations

1. Chat :- Chat does not work during the heavy load in the server
2. In future release, week view UI will be changed, so all the events are displayed at start time of the event.
3. If events start time is lesser than the Calendar start time, it will not be displayed in the calendar view.
4. Limited Field Level Security in Inventory PDF, Dashboards and Search results

[edit] Migration Steps

Note:

1. Please remove, 'STRICT_TRANS_TABLES' from the 'SQL MODE'. Otherwise, you may face issues with saving data.
2. Please take the database dump before proceeding with the migration to be on safer side.
3. Before Migration, In File: modules\Migration\PatchApply.php

   set_time_limit(-1);

change it to

   set_time_limit(0);

[edit] To Migrate from 5.x versions

Step 1 : Backup user_priveleges/CustomInvoiceNo.php (if it exists)
Step 2 : Download the patch (vtigercrm-5.0.0-patch4.zip) and unzip it in the vtiger CRM home directory. So that attached zip files will overwrite the existing files.
Step 3 : Restore back the user_priveleges/CustomInvoiceNo.php file and give complete permission to all the users on this file.
Step 4 : Please do the following changes in config.inc.php before starting migration

        Set the value of  $default_charset  as  'UTF-8'.  
        ie.,  $default_charset = 'UTF-8';         
        and add the following lines at the end of the file before ?>.      
        // trim descriptions, titles in listviews to this value
        $listview_max_textlength = 40;

Step 5 : Go to Smarty/templates_c and remove all the cached files which ends with ".tpl.php". If not you may not get the ui changes properly.
Step 6 : Login as admin user. Once you login, you will notice some error on the home page as follows:

Fatal error: Call to a member function FetchRow() on a non-object in ....\include\database\PearDatabase.php on line 424  
        
This is expected behavior as there has been lot of database table changes.  
Ignore this for now and proceed with the next step.

Step 7 : Click on the Settings tab
Step 8 : Go to Migration Wizard.
Step 9 : Use the option 'Upgrade my vtiger 5.x version to Current Version (5.0.4)'
Step 10: Click on Migrate.
Step 11: Once you are done with migration, Go to your browser options and clear the cache.

[edit] To Migrate from 4.2.x versions

Step 1  : Take the dump of your database.

         mysqldump <database_name> [ -u username -p ] > dump_file.sql 

Step 2  : Create an empty database

         mysql> create database <new_database>;

Step 3  : Import the data into new database from the dump file.

         mysql> use database <new_database>;
         mysql> source <complete_path>\dump_file.sql

Step 4  : Install vtiger 5.0.4 (during installation give a different database name <dummy_database>)
Step 5  : Login as admin user
Step 6  : Click on the Settings tab
Step 7  : Go to Migration Wizard.
Step 8  : Use the option 'Migration from vtiger 4.2.x (4.2Patch2/4.2.3/4.2.4) to Current Version (5.0.4)'
Step 9  : Select Source -> Select 'I have a new database with 4.2.3 Data'
Step 10 : Give proper database connection parameters and provide the name of the newly created database ( <mew_database>) into which the dump file is imported.
Step 11 : Click on Migrate.
Step 12 : Make a note of all the query failures (if any)
Step 13 : Goto config.inc.php -> Change the database name to <new_database>

         $dbconfig['db_name'] = <new_database>;

[edit] Modified Tables after 5.0.3

Table Name	Changes Done
vtiger_users	1.Increased user_name field size from 20 to 255 2.Increased date_format field size from 30 to 200 3.Increased activiy_view field size from 25 to 200 4.Increased lead_view field size from 25 to 200 5.Added tagcloud_view column 6.Added internal_mailer column 7.Added crypt_type column
vtiger_sharedcalendar	1.Updated type into InnoDB
vtiger_blocks	1.Updated type into InnoDB
vtiger_account	1.Increased account_type field size from 50 to 200 2.Increased industry field size from 50 to 200 3.Increased rating field size from 50 to 200
vtiger_contactdetails	1.Increased salutation field size from 50 to 200
vtiger_contactsubdetails	1.Increased leadsource field size from 50 to 200
vtiger_portalinfo	1.Updated type into InnoDB
vtiger_customerdetails	1.Updated type into InnoDB
vtiger_leaddetails	1.Increased salutation field size from 10 to 200 2.Increased industry field size from 50 to 200 3.Increased rating field size from 50 to 200 4.Increased leadsource field size from 50 to 200
vtiger_potential	1.Increased Amount field size from 10.2 to 14.2 2.Increased sales_stage field size from 50 to 200 3.Increased potentialtype field size from 50 to 200 4.Increased leadsource field size from 50 to 200
vtiger_activity	1.Added recuringtype column 2.Increased activitytype field size from 50 to 200 3.Increased duration_minutes field size from 2 to 200 4.Increased status field size from 100 to 200 5.Increased eventstatus field size from 100 to 200 6.Increased priority field size from 150 to 200 7.Renamed the index 'activity_status_eventstatus_idx' to 'activity_status_idx' and removed the column 'eventstatus' from the above index
vtiger_attachments	1.Increased name field size from 100 to 255 2.Changed path field type from varchar to TEXT. 3.Added Subject column 4.Renamed the index 'attachments_description_name<wbr>_type_attachmentsid_idx' to 'attachments_description_type<wbr>_attachmentsid_idx' and removed the column 'name' from the above index
vtiger_vendor	1.Increased glacct field size from 50 to 200
vtiger_products	1.Changed 'qtyinstock' field from Integer(11) to Decimal(25,3) 2.Increased productcategory field size from 40 to 200 3.Increased manufacturer field size from 40 to 200
vtiger_manufacturer	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_users2group	1.Updated type into InnoDB
vtiger_group2role	1.Updated type into InnoDB
vtiger_group2rs	1.Updated type into InnoDB
vtiger_campaign	1.Decreased campaigntype field size from 255 to 200 2.Decreased campaignstatus field size from 255 to 200 3.Decreased expectedresponse field size from 255 to 200
vtiger_cntactivityrel	1.Added an Index 'cntactivityrel_activityid_idx'
vtiger_troubletickets	1.Removed description column 2.Increased priority field size from 150 to 200 2.Increased severity field size from 150 to 200 2.Increased status field size from 150 to 200 2.Increased category field size from 150 to 200
vtiger_headers	1.Updated type into InnoDB
vtiger_import_maps	1.Updated type into InnoDB
vtiger_systems	1.Updated type into InnoDB 2.Increased server field size from 30 to 100 2.Increased server_username field size from 30 to 100 2.Increased server_password field size from 30 to 100
vtiger_currency_info	1.Updated type into InnoDB
vtiger_defaultcv	1.Updated type into InnoDB
vtiger_emailtemplates	1.Updated type into InnoDB
vtiger_faq	1.Increased category field size from 100 to 200 2.Increased status field size from 100 to 200
vtiger_files	1.Updated type into InnoDB
vtiger_loginhistory	1.Updated type into InnoDB
vtiger_ticketstracktime	1.Updated type into InnoDB
vtiger_users_last_import	1.Updated type into InnoDB
vtiger_wordtemplates	1.Updated type into InnoDB
vtiger_accounttype	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_leadsource	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_opportunity_type	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_leadstatus	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_eventstatus	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_industry	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_salutationtype	1.Removed sortorderid column 2.Added picklist_valueid column 3.Updated type into InnoDB
vtiger_taskpriority	1.Removed sortorderid column 2.Added picklist_valueid column 3.Updated type into InnoDB 4.Increased taskpriority field size from 100 to 200
vtiger_taskstatus	1.Removed sortorderid column 2.Added picklist_valueid column 3.Updated type into InnoDB 4.Increased taskstatus field size from 100 to 200
vtiger_sales_stage	1.Removed sortorderid column 2.Added picklist_valueid column 3.Updated type into InnoDB
vtiger_faqcategories	1.Removed sortorderid column 2.Added picklist_valueid column 3.Updated type into InnoDB 4.Increased faqcategories field size from 60 to 200
vtiger_faqstatus	1.Removed sortorderid column 2.Added picklist_valueid column 3.Updated type into InnoDB 4.Increased faqstatus field size from 60 to 200
vtiger_rating	1.Removed sortorderid column 2.Added picklist_valueid column 3.Updated type into InnoDB
vtiger_ticketcategories	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid 3.Updated type into InnoDB 4.Increased ticketcategories field size from 100 to 200
vtiger_ticketpriorities	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid 3.Updated type into InnoDB 4.Increased ticketpriorities field size from 100 to 200
vtiger_ticketseverities	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid 3.Updated type into InnoDB 4.Increased ticketseverities field size from 100 to 200
vtiger_ticketstatus	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid 3.Updated type into InnoDB 4.Increased ticketstatus field size from 60 to 200
vtiger_activsubtype	1.Updated type into InnoDB
vtiger_durationhrs	1.Updated type into InnoDB
vtiger_durationmins	1.Updated type into InnoDB
vtiger_profile2tab	1.Updated type into InnoDB
vtiger_profile2standardpermissions	1.Updated type into InnoDB
vtiger_profile2field	1.Updated type into InnoDB
vtiger_role2profile	1.Updated type into InnoDB
vtiger_def_org_share	1.Updated type into InnoDB
vtiger_def_org_field	1.Updated type into InnoDB
vtiger_profile2utility	1.Updated type into InnoDB
vtiger_productcategory	1.Removed sortorderid column 2.Added picklist_valueid column
vtiger_salesorder	1.Increased carrier field size from 100 to 200
vtiger_notificationscheduler	1.Added column TYPE
vtiger_relatedlists	1.Updated type into InnoDB
vtiger_rss	1.Updated type into InnoDB
vtiger_mail_accounts	1.column mail_password size changed from 20 to 250 2.Updated type into InnoDB
vtiger_quotes	1.Column team is removed 2.Increased carrier field size from 100 to 200
vtiger_purchaseorder	1.Increased carrier field size from 100 to 200
vtiger_activity_reminder	1.Updated type into InnoDB
vtiger_usageunit	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_glacct	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_quotestage	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_invoicestatus	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_postatus	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_sostatus	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_carrier	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_recurringevents	Contraint fk1 is added
vtiger_inventory_tandc	1.Updated type into InnoDB
vtiger_campaigntype	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_campaignstatus	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_expectedresponse	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_picklist	New
vtiger_role2picklist	New
vtiger_picklistvalues_seq	New
vtiger_portal	1.Added column setdefault
vtiger_soapservice	New
vtiger_freetags	1.Updated type into InnoDB
vtiger_emaildetails	1.Updated type into InnoDB
vtiger_invitees	1.Updated type into InnoDB
vtiger_status	1.column SORTORDERID changed into PRESENCE 2.column PRESENCE changed into picklist_valueid
vtiger_inventoryproductrel	1.Quantity changed from Interger(19) to Decimal(25,3)
vtiger_version	1.Updated type into InnoDB

Edit this page | Discuss this page | Page history | What links here | Related changes Main Page | About vtiger.com | Find: This page has been accessed 5,383 times. This page was last modified 08:55, 12 June 2008.