02-12-2015, 07:37 AM
I'd say this has happened always, that part of the code has never worked correctly since it was released by vtiger. In other words, vtiger crm 5.4 had the same problem and we haven't looked into fixing it (yet).
I have been telling users of vtiger CRM 5.4 the same thing I told you for years.
At the moment there is no solution. We will look into it eventually but there are more important things in front.
I have been telling users of vtiger CRM 5.4 the same thing I told you for years.
At the moment there is no solution. We will look into it eventually but there are more important things in front.
Joe
TSolucio
TSolucio