I just migrated my itop beta to beta2, and there seems to be a few problems :
1 - When I create a incident ticket or service request ticket to test, I cannot delete them. Picture included below. Error code : Fatal error, iTop cannot continue. Error: To continue this operation, the following parameters are missing : class and selectObject[]..
2 - In the portal, if I have no tickets opened, going to the ongoing tickets or closed tickets sections brings you to a crash page. This was not the case prior to the upgrade.
Thanks for the feedbacks! The first error has been fixed just after the beta2 under 67afbd1d8.
Regarding the portal crash, can you tell us more about your configuration :
- Do you have any customization? (I see that you have a custom theme)
- Can you add "&debug=true" to the URL, make the crash happen again and give us the complete error message / trace?
Thanks!
Guillaume
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
See pictures below for my addons. the only changes i've made manually in the code are color switches in the bootstrap file from orange to red for a few hexa colors codes and thats it.
Log from the debug ( pictured version below):
Exception
Symfony\Component\Debug\Exception\ ContextErrorException
in env-production/itop-portal-base/portal/src/Controller/ManageBrickController.php (line 824)
in env-production/itop-portal-base/portal/src/Controller/ManageBrickController.php (line 824)
ManageBrickController->GetData() in env-production/itop-portal-base/portal/src/Controller/ManageBrickController.php (line 98)
ManageBrickController->DisplayAction() in lib/symfony/http-kernel/HttpKernel.php (line 151)
HttpKernel->handleRaw() in lib/symfony/http-kernel/HttpKernel.php (line 68)
HttpKernel->handle() in lib/symfony/http-kernel/Kernel.php (line 200)
Kernel->handle() in env-production/itop-portal-base/portal/public/index.php (line 51)
require_once(array('string', '/var/www/html/itop/env-production/itop-portal-base/portal/public/index.php')) in env-production/itop-portal-base/index.php (line 38)
require_once(array('string', '/var/www/html/itop/env-production/itop-portal-base/index.php')) in pages/exec.php (line 62)
Seems like there is an issue related to bug N°4012 (internal bug tracker). Would it be possible to have:
- The content of the env-production/core/module_designs/itop-portal.xml file (no confidential information in it, only the portal conf)
- The content of the log/error.log corresponding to the time of this error ?
The problem is in a debug trace, when we try to output the complete OQL used by the portal when trying to build the elements table.
Thanks,
Guillaume
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You caught me with my pants down on that one though because I did made a modification to the xml file mentionned here : I changed the default value from list to mosaic on line 272, but its the only change I've made.
Hi, I tried this extention, Actually I do have it, but it clearly doesn't work. The view stays at 'list' even with this added. So I made the change manually.
EDIT : I checked your link, I dont think I have this one, i'll give it a shot.
Last edit: Sebastien Jean 2021-07-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I applied that extension and replaced the modification I made to the itop-portal.xml file, the mosaic view works, thanks! I still have the bug for the tickets closed/ ongoing tickets when I have no tickets still though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also for iTop 3.0.0, the fix (da217a1c) was merged to the corresponding develop branch... But after beta2 packaging.
So it will be available only in beta3.
In the meantime you can patch your installed 3.0.0-beta or beta2 manually.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I just migrated my itop beta to beta2, and there seems to be a few problems :
1 - When I create a incident ticket or service request ticket to test, I cannot delete them. Picture included below. Error code : Fatal error, iTop cannot continue. Error: To continue this operation, the following parameters are missing : class and selectObject[]..
2 - In the portal, if I have no tickets opened, going to the ongoing tickets or closed tickets sections brings you to a crash page. This was not the case prior to the upgrade.
Thanks in advance and have a good day!
Hello Sebastien,
Thanks for the feedbacks! The first error has been fixed just after the beta2 under 67afbd1d8.
Regarding the portal crash, can you tell us more about your configuration :
- Do you have any customization? (I see that you have a custom theme)
- Can you add "&debug=true" to the URL, make the crash happen again and give us the complete error message / trace?
Thanks!
Guillaume
Hi,
See pictures below for my addons. the only changes i've made manually in the code are color switches in the bootstrap file from orange to red for a few hexa colors codes and thats it.
Log from the debug ( pictured version below):
Exception
Symfony\Component\Debug\Exception\ ContextErrorException
in env-production/itop-portal-base/portal/src/Controller/ManageBrickController.php (line 824)
in env-production/itop-portal-base/portal/src/Controller/ManageBrickController.php (line 824)
ManageBrickController->GetData() in env-production/itop-portal-base/portal/src/Controller/ManageBrickController.php (line 98)
ManageBrickController->DisplayAction() in lib/symfony/http-kernel/HttpKernel.php (line 151)
HttpKernel->handleRaw() in lib/symfony/http-kernel/HttpKernel.php (line 68)
HttpKernel->handle() in lib/symfony/http-kernel/Kernel.php (line 200)
Kernel->handle() in env-production/itop-portal-base/portal/public/index.php (line 51)
require_once(array('string', '/var/www/html/itop/env-production/itop-portal-base/portal/public/index.php')) in env-production/itop-portal-base/index.php (line 38)
require_once(array('string', '/var/www/html/itop/env-production/itop-portal-base/index.php')) in pages/exec.php (line 62)
Seems like there is an issue related to bug N°4012 (internal bug tracker). Would it be possible to have:
- The content of the env-production/core/module_designs/itop-portal.xml file (no confidential information in it, only the portal conf)
- The content of the log/error.log corresponding to the time of this error ?
The problem is in a debug trace, when we try to output the complete OQL used by the portal when trying to build the elements table.
Thanks,
Guillaume
Here are both files.
You caught me with my pants down on that one though because I did made a modification to the xml file mentionned here : I changed the default value from list to mosaic on line 272, but its the only change I've made.
Modifying files from the core is not recommended as you will loose your modifications on each upgrade / setup. Actually there is an extension for this, check this one : https://sourceforge.net/p/itop/discussion/third-party-extensions/thread/8d2a09c3/
I'll check your files in the coming days. :)
Hi, I tried this extention, Actually I do have it, but it clearly doesn't work. The view stays at 'list' even with this added. So I made the change manually.
EDIT : I checked your link, I dont think I have this one, i'll give it a shot.
Last edit: Sebastien Jean 2021-07-09
I applied that extension and replaced the modification I made to the itop-portal.xml file, the mosaic view works, thanks! I still have the bug for the tickets closed/ ongoing tickets when I have no tickets still though.
Hello Sebastien,
This is indeed a regression, very sorry about that... We are fixing the bug and will keep you up to date.
The problem happens when opening the "On going tickets" or the "Closed tickets" when there is no item to display.
Cheers,
Guillaume
Hello,
This is fixed in iTop 2.7.5-1 that will be published tomorrow.
Combodo internal ref : N°4161
Also for iTop 3.0.0, the fix (da217a1c) was merged to the corresponding develop branch... But after beta2 packaging.
So it will be available only in beta3.
In the meantime you can patch your installed 3.0.0-beta or beta2 manually.
That's perfect Pierre, i'll update it manually for now. Thanks!