After upgrading to iTop 3.1.3, Customized Request Forms extension (version 2.4.1) stops working

[lgsfeacd]

Are you willing to create (at a later stage) a PR for that?

No

iTop version

3.1.3

PHP version

8.0.30

Reproduction procedure

1. Create a request template with a drop-down list field using an OQL (for example "SELECT Service")
2. Fill the form in the standard portal (it works in Back Office User interface)
3. Go to drop-down list field. After typing 2 characters, the field gets empty and appears a window with the error:
   "Could not load data, please contact your iTop administrator"

The followings warnings appears in the PHP error log :

[28-May-2026 16:32:45 Europe/Paris] PHP Warning: Undefined array key "layout" in /var/www/html/itop/env-production/itop-portal-base/portal/src/Form/ObjectFormManager.php on line 1555
[28-May-2026 16:32:45 Europe/Paris] PHP Warning: Undefined array key "type" in /var/www/html/itop/env-production/itop-portal-base/portal/src/Form/ObjectFormManager.php on line 1342
[28-May-2026 16:32:45 Europe/Paris] PHP Warning: Undefined array key "layout" in /var/www/html/itop/env-production/itop-portal-base/portal/src/Form/ObjectFormManager.php on line 1390
[28-May-2026 16:32:45 Europe/Paris] PHP Warning: Undefined array key "type" in /var/www/html/itop/env-production/itop-portal-base/portal/src/Form/ObjectFormManager.php on line 1449

Additional information (if needed)

No response

[jbostoen]

iTop 3.2 LTS is the current long-term support release. You might want to upgrade to that.

Perhaps a newer version of the Customized Request Forms extension might fix your issue?
https://www.itophub.io/wiki/page?id=extensions:request-templates

[lgsfeacd]

We are currently using iTop 3.0 and as an intermediate step we have considered upgrading to 3.1 before 3.2.
Customized Request Forms is a paid extension. Is there any way to know which version would resolve the issue?

[jf-cbd]

Hello @lgsfeacd, we're not aware of this problem. We suggest you upgrading your iTop to latest version (the way you described is good) to see if this fixes your issue.
Could it be because portal users couldn't see Services objects ? (and the error wouldn't be caught properly)