Nicolas GRIMLER

If it can help @Combodo, here is the current 3.1 instance configuration: ===== begin ===== iTopVersion: 3.1.1-1 iTopBuild: 12561 iTopBuildDate: 2023-12-19 10:53:23 MySQLVersion: 10.11.5-MariaDB-1:10.11.5+maria~deb11 PHPVersion: 8.1.28 OSVersion: Linux WebServerVersion: Apache PHPModules: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, Reflection, SPL, session, standard, cgi-fcgi, bcmath, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, iconv, imap, intl, ldap, exif,...

Hello all :) I've tried to upgrade my currently running iTop 3.1.1-1-12561 (with a bunch of extensions from iTopHub) to the new v3.2.0-beta1 but face a lot of errors that makes iTop unusable (backend & portal). Few basic pages are working (dashboards, users accounts list (but not profiles list), OQL query book ) but nearly all others are crashing with the following stack trace: 2024-07-05 20:03:09 | Error | 4 | Uncaught TypeError: MetaModel::GetHilightClass(): Return value must be of type string,...

Hi, I upgraded a test instance from 3.0.3 to 3.1 and noticed that synchro_exec does not work anymore. The script seems to not parse command line parameters correctly and more precisely the data_sources and always return the following error: # php synchro_exec.php --data_sources=5 --param_file=/etc/itop/cron.params ERROR: The data source (id=) does not exist. Exiting... If I use the synchro_exec.php file from the 3.0.3 release, it work as expected: # php synchro_exec.php --data_sources=5 --param_file=/etc/itop/cron.params...

Hi Pierre & Vincent, Thanks for your detailed feedback ! I know that the release date is for the end of the year, that's why I wrote 3.x in the title ;-) For the allow_menu_on_linkset option, I may have overlooked the documentation even if it's the 4th row of the list :-( I'll give it a try right now ! The "Catalog of Procedure" is not listed in the customer portal nor iTopHub :-( I already looked at a solution to provide some "templating/stencils" as many users ask me if it is possible to have a...

The v3 may be the good "future release" for this ;-)

Oh btw, If you want to see how much task a change can get, just look at the screenshot :p Best Regards, Nicolas.

Oh btw, If you want to see how much task a change can get, just look at the scrrenshot :p

Hi ! I was trying to explain (again) to some users what is the right workflow for work orders creation for changes (the same apply to user requests and incidents) and ask myself "Is there is a new/better way in v3?". Unfortunately the process is still the same and not really user friendly :-( For the background, the actual work flow is as follow: Create a ticket (User request, incident, change (normal, emergency, ...)) Save the ticket to let it have its reference ID set Enter in modification mode...