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

[Steve Kenow]

Thank you. It looks like my process is very similar to yours, Alan, except
for the execution of the upgrade scripts.

Sutharsan - the custom modules are extensions from VT Experts, plus 1 that
was created using their custom module creator. I know there are a few that
will need to be upgraded with their process once everything else is done. I
haven't found any unexpected behaviors or other ill side effects from
having them enabled when I ran the db migration scripts, which does save me
some time.

Apart from that, it seems odd that the core migration will add menu entries
for active custom modules and not for the inactive modules. It would seem
more is needed to get entries into vtiger_app2tab so when they are
activated they show up.

*Steve Kenow*
Retail Data Systems of Minnesota
End-User Services & Support Manager
Direct: (952) 392-2686
Office: (952) 934-4002
skenow at rdspos.com



Support Questions/Issues? Email rdshelp at rdspos.com (non-emergencies) or
call (952) 934-4002 24/7


On Wed, Jul 26, 2023 at 2:10 AM Sutharsan J <ajstharsan at gmail.com> wrote:

> Hi
>
> What are the custom modules? We're they Developed by you or third party,
> such as Vtexperts? They have their own way to upgrade extentions.
>
> And if those are developed by you following entity modules standards, I
> don't think they should be disabled.
>
> we upgraded different versions
> 1. Vtiger 6.0 to 7.4
> 2. 6.5 to 7.5
>
> The db was upgraded using vtiger migration scripts, then core
> customizations were added manually.
>
> Those were success but took time more than 100 hours because of some core
> customization old developers did.
>
> Thanks
> Sutharsan jeganathan
>
> On Tue, 25 Jul 2023 at 23:23 Steve Kenow <skenow at rdspos.com> wrote:
>
>> Hello again - still running through the upgrade process and finding
>> things to address once we move forward.
>>
>> My process:
>>
>>    1. Clean install of 7.5.0
>>    2. Copy custom module folders from 6.5.0 to 7.5.0 instance
>>    3. Backup db from 6.5.0
>>    4. Load db to new db
>>    5. Sign in to a copy of vt650 with custom modules pointing at the
>>    backup db and deactivate the custom modules
>>    6. Edit vt750/config.inc.php to access new db
>>    7. Edit vt750/vtigerversion.php to be at 6.5.0
>>    8. Access vt750/index.php??module=Migration&view=Index&mode=step1
>>    9. Login and wait
>>
>> Since I haven't had the custom modules activated yet in vt750, I haven't
>> looked for them. They show up in the module manager. Today, I activated one
>> of them and it wasn't in any menu - the All menu option is not in V7+. I
>> wasn't able to add to any menu categories through the administration area.
>> Searching here, I find this was identified and 7.1.0 added them to the
>> TOOLS menu. Not for me. Manually added the entry to vtiger_app2tab and it
>> was where I wanted it.
>>
>> I had some work done on a module and decided to take another backup and
>> migrate again. In my haste, I didn't deactivate the custom modules before
>> starting the migration script. Guess what? This time all the custom modules
>> showed up in the TOOLS menu.
>>
>> 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?
>>
>> *Steve Kenow*
>> Retail Data Systems of Minnesota
>> End-User Services & Support Manager
>> Direct: (952) 392-2686
>> Office: (952) 934-4002
>> skenow at rdspos.com
>>
>>
>>
>> Support Questions/Issues? Email rdshelp at rdspos.com (non-emergencies) or
>> call (952) 934-4002 24/7
>> _______________________________________________
>> http://www.vtiger.com/
>
> --
> Development Manager
> Radus28 Software Solution
> [image: Radus28 Software Solution]
> 123, Level 2, Mc Larens Building
> Baudhaloka Mw.
> Colombo 04
> Sri Lanka
> M : +94773795291
> E  : sutharsan at radus28.com
> W : www.radus28.com
> _______________________________________________
> http://www.vtiger.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20230726/8377a560/attachment.html>