[Vtigercrm-developers] Custom modules and migrating to vt7.5.0

[Alan Lord]

Nope I've never had an issue actually, and if you think about it, when 
you start the upgrade process from the UI, the first thing it does is to 
extract the latest vtiger upgrade zip file which overwrites the changed 
core files anyway - so if a function was dropped the file would be 
changed anyway?

I've only had this issue really when going from v5. So I do a 2 stage 
process from v5 to v6, then v6 to v7. But then I need an old server to 
do that anyway because getting v5 to run on anything more than php5 is a 
PITA ;-)

HTH

On 26/07/2023 16:21, Rubén A. Estrada Orozco wrote:
> Hi Alan,
> 
> I've always been hesitant to follow the procedure you mention (and have 
> in fact never tried it) because of the following: What if one migration 
> script along the chain relies on code of a specific version that is not 
> the latest you are migrating to?
> Hypothetical example: I migrate from 6.2 to 7.5. Following your 
> procedure you have vtiger 7.5 code base when executing all the migration 
> scripts. Now let's say that the migration script from 6.4 to 6.5 relies 
> on vitger's 6.5 code. And that the same code wouldn't work using Vtiger 
> 7.5 code.
> 
> Haven't you had that situation?
> 
> On Wed, Jul 26, 2023 at 1:03 AM Alan Lord <alanslists at gmail.com 
> <mailto:alanslists at gmail.com>> wrote:
> 
>     On 25/07/2023 18:50, Steve Kenow wrote:
>      >
>      > Having gone through a migration using all the steps of the UI, I
>     know
>      > that I get prompted to deactivate any custom modules before
>     proceeding.
>      > What's the 'right' way to do this and have the menu entries built?
>      >
> 
>     I generally to use a modified set of migration scripts when moving from
>     significant version to version, e.g. v5.x to v7.x or v6.x to v7.x, and
>     run them from the command line.
> 
>     The process I use is something like this...
> 
>     1. Install a completely new and clean 7.x. system (or whatever is the
>     latest version)
> 
>     2. Copy the custom module code into this clean vtiger and then modify
>     the code/port the extensions so they work correctly in your new vtiger
> 
>     https://docs.google.com/document/d/1ud-ddTHFfKeuJ6DciVJHNr8B5IR_v_gEBvPXa9TFbZs/edit <https://docs.google.com/document/d/1ud-ddTHFfKeuJ6DciVJHNr8B5IR_v_gEBvPXa9TFbZs/edit>
> 
>     2. Extract your source system and copy over the /storage and /test
>     directory contents (You can install it alongside - sometimes that helps
>     when testing stuff).
> 
>     3. Drop the clean vtiger database and import the source vtiger database
>     into the clean system
> 
>     4. Run the migration scripts, in-order, within the new system
> 
>     5. Clean up anything that's broken ;-)
> 
> 
>     HTH
> 
>     Al
> 
> 
>     _______________________________________________
>     http://www.vtiger.com/ <http://www.vtiger.com/>
> 
> 
> _______________________________________________
> http://www.vtiger.com/