[Vtigercrm-developers] vtiger upgrade from 7 to 8
Rubén A. Estrada Orozco
rulotec1 at gmail.com
Fri Oct 4 07:53:49 GMT 2024
Thank you guys for sharing your knowledge.
Alan, any chance you might share your modified scripts?
On Thu, Oct 3, 2024 at 7:19 AM Angelo Paglialonga <
info at angelopaglialonga.com> wrote:
> Ciao Ruben i do mostly the same as Alan, but i run those scripts from the
> browser.
>
>
>
>
>
> *Dott. Angelo Paglialonga*
> Consulenza vTiger CRM ad alto ROI.
> Telefono: 338.6077866
> Sito web*: *angelopaglialonga.com
> <https://treeway.it/angelo//shorturl.php?id=6457a0339d9398.33634588>
>
> Il giorno 3 ott 2024, alle ore 13:03, Alan Lord <alanslists at gmail.com> ha
> scritto:
>
> On 03/10/2024 11:27, Rubén A. Estrada Orozco wrote:
>
> Angelo and Alan,
> Could you please comment on my last email. Please let me insist. I would
> like to know if you agree with my observations and how you run the db
> migration from command line.
>
>
> You are probably right Ruben, but to be honest with you I rarely (if ever)
> use the web-based migration now.
>
> My scripts are now very far from standard (see how many issues from me on
> code.vtiger.com relate to migration scripts) but the basic modification
> is pretty straightforward.
>
> As an example look at the first one:
>
>
> https://code.vtiger.com/vtiger/vtigercrm/-/blob/master/modules/Migration/schema/540_to_600RC.php
>
> Before the if(!defined('VTIGER_UPGRADE') test I add:
>
> const VTIGER_UPGRADE = true;
> $Vtiger_Utils_Log = true;
> require_once('include/logging.php');
> require_once('config.php');
> require_once('include/utils/CommonUtils.php');
> require_once('includes/main/WebUI.php');
> ini_set('memory_limit', '-1');
> // Let's see some errors
> ini_set('error_reporting', E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT &
> ~E_WARNING); // I can change this going forward :-)
> ini_set('display_startup_errors', 1);
> ini_set('display_errors', 1);
>
>
> This sets the VTIGER_UPRADE constant to true and includes some files
> (especially the WebUI.PHP) that enable you to use the command line.
>
> I save these files as, for example, 540_to_600RC-cli.php
>
> I also set the pear db to die on error.
>
> You can't really read the output very easily as it contains html markup
> but you get the idea...
>
> I usually run them as the web server user from the vtiger root directory,
> e.g.:
>
> sudo su - www-data -s /bin/bash
>
> (ubuntu server user www-data has no shell by default) You can run them as
> root and then just chown everything back to the web user afterwards if its
> easier.
>
> You can also write a shell script to iterate over each file based on the
> current version.
>
> You can also log the output (2&<1) into files from each version update so
> you can review at your leisure.
>
> You will need to hack a few of them as I recall as some things didn't work
> quite right initially - my commit log for my modified scripts start in Sept
> 2015 ;-)
>
> HTH
>
> Al
>
>
> _______________________________________________
> http://www.vtiger.com/
>
>
> _______________________________________________
> http://www.vtiger.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20241004/4c6ac09c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: AngeloPaglialonga-foto-firma.png
Type: image/png
Size: 20265 bytes
Desc: not available
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20241004/4c6ac09c/attachment-0001.png>
More information about the vtigercrm-developers
mailing list