[Vtigercrm-developers] Campaign Manager and large lists

Stacey Johnson stacey.johnson110 at gmail.com
Fri Jun 19 12:27:42 GMT 2015


Yea Simone, get me details on priv

TNx

Stacey

On Fri, Jun 19, 2015 at 1:44 PM, Simone Travaglini <
simonetravaglini at gmail.com> wrote:

> Hi,
> if you need we developed an email campaign module that we are relasing in
> this day.
> The module permit to set batch and have a specific scheduler.
> Permit also to create list, have report, performing change in list of
> people who opened email, link tracking.
> Permit also to create new campaign starting from other campaign (select
> all people who opened email).
>
> In next days we will post all functionality and sell it... if someone
> interest could ask to me!
>
> 2015-06-19 2:48 GMT+02:00 Hamono, Chris (DPC) <Chris.Hamono at sa.gov.au>:
>
>> 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!
>>
>>
>>
>>
>>
>> Chris
>>
>> _______________________________________________
>> http://www.vtiger.com/
>>
>
>
>
> --
> Simone Travaglini
> 328 5499846
> Linkedin: Simone Travaglini
>
>
> Rispetta l'ambiente: non stampare questa mail se non ti è veramente
> necessario!
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20150619/6ed67733/attachment.html>


More information about the vtigercrm-developers mailing list