Hi Mickael,
Sorry for this, the version 1.0.1 currently on iTop Hub is not compatible with iTop 3.1.
A new version 1.0.2 will be released in January. In the meantime, I sent you an email to solve your issue...
Vincent
Last edit: Vincent @ Combodo 2023-11-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
you said “all extensions which needed to be upgraded to ensure iTop 3.1 compatibility are now released” but according to this list https://www.itophub.io/wiki/page?id=3_1_0:release:extensions the first 3.1 compatible version of “Send updates by email“ is 1.4.4. In iTop store the highest version is 1.3.2. That’s why I didn’t upgrade iTop to 3.1 yet. Do I understand something wrong?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Community,
all extensions which needed to be upgraded to ensure iTop 3.1 compatibility are now released.
This release includes :
* Approval process light
* Approval process automation
* Communication to the customers
* Datacenter view
* Datacenter view extended
* Follow-up forms without authentication
* Mail to ticket automation
Each version of those extensions also include improvements that are details in the extension change log.
Last edit: Delphine COILLE 2023-10-05
Hello,
Can you check the location hierarachy module.
I bought it and while upgrading from 3.0.3 to 3.1.2, I got those errors :
Fatal error: Uncaught Error: Call to undefined method SetupPage::log_info() in /home/my/public_html/itop/prod/setup/modulediscovery.class.inc.php(504) : eval()'d code:74
Stack trace:
0 /home/my/public_html/itop/prod/setup/runtimeenv.class.inc.php(1103): LocationHierarchyInstaller::AfterDatabaseCreation()
1 /home/my/public_html/itop/prod/setup/applicationinstaller.class.inc.php(911): RunTimeEnvironment->CallInstallerHandlers()
2 /home/my/public_html/itop/prod/setup/applicationinstaller.class.inc.php(336): ApplicationInstaller::AfterDBCreate()
3 /home/my/public_html/itop/prod/setup/wizardsteps.class.inc.php(2441): ApplicationInstaller->ExecuteStep()
4 /home/my/public_html/itop/prod/setup/ajax.dataloader.php(173): WizStepSummary->AsyncAction()
5 {main}
thrown in /home/my/public_html/itop/prod/setup/modulediscovery.class.inc.php(504) : eval()'d code on line 74
PHP error occured : msg=Uncaught Error: Call to undefined method SetupPage::log_info() in /home/my/public_html/itop/prod/setup/modulediscovery.class.inc.php(504) : eval()'d code:74
Stack trace:
0 /home/my/public_html/itop/prod/setup/runtimeenv.class.inc.php(1103): LocationHierarchyInstaller::AfterDatabaseCreation()
1 /home/my/public_html/itop/prod/setup/applicationinstaller.class.inc.php(911): RunTimeEnvironment->CallInstallerHandlers()
2 /home/my/public_html/itop/prod/setup/applicationinstaller.class.inc.php(336): ApplicationInstaller::AfterDBCreate()
3 /home/my/public_html/itop/prod/setup/wizardsteps.class.inc.php(2441): ApplicationInstaller->ExecuteStep()
4 /home/my/public_html/itop/prod/setup/ajax.dataloader.php(173): WizStepSummary->AsyncAction()
5 {main}
thrown, no=1, file=/home/my/public_html/itop/prod/setup/modulediscovery.class.inc.php(504) : eval()'d code, line=74
Hello Mickael,
Can you tell us which version of the "Location Hierarchy" extension you have?
Thanks,
Guillaume
Hi Mickael,
Sorry for this, the version 1.0.1 currently on iTop Hub is not compatible with iTop 3.1.
A new version 1.0.2 will be released in January. In the meantime, I sent you an email to solve your issue...
Vincent
Last edit: Vincent @ Combodo 2023-11-14
Hello,
you said “all extensions which needed to be upgraded to ensure iTop 3.1 compatibility are now released” but according to this list https://www.itophub.io/wiki/page?id=3_1_0:release:extensions the first 3.1 compatible version of “Send updates by email“ is 1.4.4. In iTop store the highest version is 1.3.2. That’s why I didn’t upgrade iTop to 3.1 yet. Do I understand something wrong?
Hi Eric,
I am not sure but I suspect that the 3.1 issue fixed in the 1.4.4 is not blocking.
Hi ad
I have problem about create ticket and assign approver to it with user profile is "portal user"