[Vtigercrm-developers] Updating VTiger without losing customizations?

Prasad prasad at vtiger.com
Thu Mar 22 03:30:38 GMT 2018


>
> Not sure how to preserve custom code between major upgrades such as 5.4 to
> 6.x to 7.x without any re coding.


When convention of framework changes - you need to redo.​

--
FB <http://www.facebook.com/vtiger> I Twit <http://twitter.com/vtigercrm> I
LIn <https://www.linkedin.com/company/1270573?trk=tyah> I Blog
<https://blogs.vtiger.com> I Website <https://www.vtiger.com/>

On Thu, Mar 22, 2018 at 8:47 AM, Sutharsan Jeganathan <ajstharsan at gmail.com>
wrote:

> Hi
>
> There are several points have to be discussed regarding non-core changes.
> Non core changes won't be affected (probably) through minor version upgrade
> such as 7.1 to 7.2.
>
> Normally you have to keep your code in separate files rather than
> vtiger(core) files. You may extend core classes into yours like
>
> Google_map_Js("Your_Map_Js", {}, { }
>
> Not sure how to preserve custom code between major upgrades such as 5.4 to
> 6.x to 7.x without any re coding.
>
>
> Cheers
> Sutharsan Jeganathan
>
> On Thu, Mar 22, 2018 at 1:22 AM, Alex Hall <ahall at autodist.com> wrote:
>
>> Hello all,
>> Is there a safe way to update VTiger? We added our API key to
>> layouts/modules/google/resources/map.js, for instance, but the recent
>> update overwrote that file, thus losing our key. What's the best way to
>> handle source changes like this? My thought is to rename a copy of our
>> modified version, so that updates won't touch that copy. This has the
>> problems of dealing with removed directories in an update, and of merging
>> changes back into the updated source. Is there a better solution? Thanks.
>>
>> --
>> Alex Hall
>> Automatic Distributors, IT department
>> ahall at autodist.com
>>
>> _______________________________________________
>> http://www.vtiger.com/
>>
>
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20180322/74b256e4/attachment-0001.html>


More information about the vtigercrm-developers mailing list