[Vtigercrm-developers] upgrade to 7.2

[Uma S]

Sure! Ruben, will wait for your response.

On Thu, Nov 14, 2019 at 11:48 PM Rubén A. Estrada Orozco <rulotec1 at gmail.com>
wrote:

> Thanks Uma,
>
> I've done two migrations so far and it happened in both. I didn't look
> into vtiger_version and vtigerversion.php but at the botton of vtiger's UI
> the version was 7.1.0.
>
> I will keep an eye on that for the next migration and report back.
>
>
>
> Saludos
>
> Rubén
>
>
> On Thu, Nov 14, 2019 at 7:13 AM Uma S <uma.s at vtiger.com> wrote:
>
>> Hi Ruben,
>>
>> Sorry! I could not able to reproduce this issue, while migrating from
>> 7.1.0 to 7.2.0, Please do check this Screen-sScreen-shothot
>> <https://sc.vtiger.in/screenshots/uma-sc-at-14-11-2019-18-31-43.png>.
>>
>> Can you please verify what is the current version of your source during
>> migration? from vtiger_version table and vtigerversion.php file?
>>
>> Only with respect to this current version, it executes the migration
>> file. I expect something is going wrong there.
>>
>> On Thu, Nov 14, 2019 at 9:28 AM Rubén A. Estrada Orozco <
>> rulotec1 at gmail.com> wrote:
>>
>>> Thanks for the tips! I'll try them out in my next migration. Running the
>>> migration scripts from cli sounds attractive.
>>>
>>> I hope Uma, ore somebody from VT can comment on why the 701 -> 710
>>> schema script is run on the 7.1.0 to 7.2.0 migration.
>>>
>>>
>>> Saludos
>>>
>>> Rubén
>>>
>>>
>>> On Wed, Nov 13, 2019 at 1:37 PM Alan Lord <alanslists at gmail.com> wrote:
>>>
>>>> On 13/11/2019 19:06, Rubén A. Estrada Orozco wrote:
>>>> > Thanks for the input Alan! It's very helpful.
>>>>
>>>> > 1. How do you turn on the logs in the case of migrations? I have
>>>> tried
>>>> > enabling it by setting 'LOG4PHP_DEBUG' => true in
>>>> config.performance.php
>>>> > without luck :( It has been very frustrating that migration scripts
>>>> just
>>>> > silently fail and I can't get fatal errors to display.
>>>>
>>>> You also need to edit the log4php.properties file to enable debug
>>>> logging; change where it says "FATAL" to "DEBUG".
>>>>
>>>> > 2. How do you run the migration scripts by the command line? I assume
>>>> > running for example php -f 701_to_710.php wouldn't work because of
>>>> > dependencies in the script.
>>>>
>>>> It's probably not something I would recommend unless you know what you
>>>> are doing or have lots of time to play, test & fail ;-) It's a thing
>>>> I've been working on (on and off) since 2015 according to my git commit
>>>> history ;-)
>>>>
>>>> Anyway - basically you need to do this:
>>>>
>>>> Depending on the process (New Installation, or a Migration) you need to
>>>> set the VTIGER_UPGRADE and/or INSTALLATION_MODE constants. You need
>>>> include a few files at the top such as the config.php and the
>>>> WebbUI.php
>>>> so the class loader works. Then it is helpful, but not essential, to
>>>> edit the scripts so the output is readable on the cli as most of it is
>>>> echoed with html tags such as br, p etc... I also turn on php
>>>> error_reporting as this can be a lot more helpful than the debug logs.
>>>>
>>>> You also really have to run the scripts as the web-server user because
>>>> they need write access to the vtiger filesystem... I would never
>>>> recommend using a super user account. FWIW on linux I create a
>>>> .bash_alias entry for this
>>>>
>>>> alias phpwww='sudo -u www-data php'
>>>>
>>>> so from the command line I just need to type
>>>>
>>>> # phpwww file-to-run.php
>>>>
>>>> Hope that helps
>>>>
>>>> Al
>>>>
>>>> _______________________________________________
>>>> http://www.vtiger.com/
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>
>>
>>
>> --
>> With
>> Best Regards
>> Uma.S
>> Vtiger Team
>> _______________________________________________
>> http://www.vtiger.com/
>
> _______________________________________________
> http://www.vtiger.com/



-- 
With
Best Regards
Uma.S
Vtiger Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20191115/43e40fa1/attachment-0001.html>