[Vtigercrm-developers] Campaign Manager and large lists

Hamono, Chris (DPC) Chris.Hamono at sa.gov.au
Sun Jun 21 23:45:32 GMT 2015


Version 6.2


From: vtigercrm-developers-bounces at lists.vtigercrm.com [mailto:vtigercrm-developers-bounces at lists.vtigercrm.com] On Behalf Of Mariusz Krzaczkowski
Sent: Friday, 19 June 2015 6:32 PM
To: vtigercrm-developers at lists.vtigercrm.com
Subject: Re: [Vtigercrm-developers] Campaign Manager and large lists

For which version of vtiger is your patch?

Z poważaniem / Regards

Mariusz Krzaczkowski
Director of Product Development
M: +48 884-998-123
E: m.krzaczkowski at yetiforce.com<mailto:m.krzaczkowski at yetiforce.com>

We created an innovative open source project called YetiForceCRM. You can test it here<https://test.yetiforce.com/>, download<https://github.com/YetiForceCompany/YetiForceCRM> it for free or read its documentation<https://yetiforce.com/en/documentation.html>. Follow us on Twitter<https://twitter.com/YetiForceEN> to get real-time info about new functionalities and articles.

W dniu 2015-06-19 02:48, Hamono, Chris (DPC) napisał(a):
I have received a few requests for my modifications to get the campaign manager to behave a little more respectfully.

Rather than just respond to those emails I am posting my patches here for anyone to use.

Some of the changes in the patches aren't used (commented out) some are merely because I pushed the format button and reformatted the code to be more readable.  And I removed the tracking bug. If you want that you will need to re-enable it.

There is a lot of scope for further improvements. What I did was a rush job to get this working by a set time. It was also about saving face. We put our faith into vtiger and advised our client it was what they needed. When we actually tried to use it with their data it failed.

We had to make it work or admit that we sold them a pup (not in a good way).
Apply the patches in order 0001 0002 0003

There are no database changes. All the fixes are code based, they are core code changes. Be aware of this during upgrades.

The scheduled task that sends the emails is the IMPORT task, your cron needs to run and import schedule needs to be enabled. That is because the email queue was originally designed to send notifications out when large import processes had completed. This fixes those emails too as that never worked properly. I did not have time to create a separate email run queue and that would be inefficient.

If you are not sure why I did something. Ask!

DO NOT apply these patches to your production server. Try them on a dev server first!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20150622/6a8ded6b/attachment-0001.html>

More information about the vtigercrm-developers mailing list