Skip to content
Home » vtiger CRM Version 5.2.0 Validation Build 2 Released

vtiger CRM Version 5.2.0 Validation Build 2 Released

It has been a couple of weeks since we released 5.2 VB1. We appreciate your feedback. There were a couple of features that weren’t quite ready when we released VB1 – Project Management, Mobile APIs, PDF Library framework. Today, we are pleased to release 5.2 VB2  to the community with these features.

5.2 Key Features

  • SMS Module.
  • Mobile API module.
  • Project Management.
  • User List view Navigation.
  • Calendar ical Import Export.
  • Reports Enhancement- Added Line Item Support.
  • Assets Module.
  • and more – Detailed list can be found in the Release notes,

We also fixed a number of bugs reported on 5.1 version. Bugs fixes included in 5.2 can be found here.

5.2 Release Plan

Before releasing the final version, we will be releasing a couple of builds of 5.2 to the community to get feedback and fix issues. We plan the following releases before the final version.

  • Validation Build1 (released May 20).
  • Validation Build2 (released June 15) .
  • Release Candidate.
  • Final Version.

Please do not use the 5.2 validation build on your production server. Data Migration from Validation Build2 to final version will not be supported.

VB2 Downloads:

For Windows, Vtiger CRM 5.2.0 VB2.exe

For Linux, Vtiger CRM 5.2.0 VB2.bin

Source, Vtiger CRM 5.2.0  VB2.tar.gz

Firefox plugin, Vtiger CRM 5.2.0 VB2 Firefox-Plugin.xpi

Customer Portal, Vtiger CRM 5.2.0 VB2 CustomerPortal.zip

Demo Links:
http://demo.vtiger.com/wip

http://demo.vtiger.com/wip/customerportal

customer portal login credentials,

user name: [email protected]

password: portal

To Report Issues:

1. Login to trac.vtiger.com (To get access to trac.vtiger.com, send an email to [email protected])

2. Set Milestone as 5.2.0. Version to 5.2.0-val2

3. Set appropriate Priority.

4. Provide clear description on the issue. make sure to cover key aspects like, how to reproduce the issue, your php version, browser and screen shots of the issue if possible.

for more documentation and getting involved guidelines visit here.