v2.11.3
This version is compatible with GLPI 9.5.5 only. Support of GLPI 9.5.4 and earlier has been dropped, see notes below to know the reason.
Important note:
Possible database issue before GLPI 9.5.5
It was found that the conversion from datetime to timestamp operated by GLPI may introduce a bug in this plugin. To solve the problem for everyone it has been decided to make this plugin compatible with GLPI 9.5.5 and drop compatibility with older 9.5.x maintenance releases. See this PR for more information: glpi-project/glpi#8872 . With this fix introduced in GLPI 9.5.5 users who convert to timestamp won't be affected by the bug, but those who converted earlier may still be impacted. To solve this, this version contains an database upgrade which repairs the impacted columns and the compatibility has been restricted to GLPI 9.5.5.
The issue was timestamp columns looking the following
`date_creation` TIMESTAMP NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(),
The statement ON UPDATE current_timestamp() is added by mysql, is unwanted and may be found on 2 tables of the plugin.
Change of behavior since 2.11.0
The growing popularity of this plugin makes it used in more complex use cases. Recent issues and feedbacks shows that two important design solutions must evolve:
- entity restrictions in some parts of the plugin;
- consistency checks when showing forms to requesters;
- processing their answers
- consistency checks when designing forms.
These enhancements will impact some complex use cases by changing the available items of dropdowns / assets when a requester fills in a form. Those changes will occur only in minor versions updates.
In other words, we recommend you to check carefully forms containing questions related to dropdowns, assets, users and groups before upgrading to version 2.11.x.
This version contains the following change:
entity of dropdowns is now relative to the form, not the user. see #2023. Those who want to keep the old behavior must revert this change.
Bug Fixes
- condition: avoid HTML entities in dropdown (451dfbd)
- dropdownfield: disable recursivity (daa7fb0)
- fields: prevent empty expression evaluation (f9fabb5), closes #2195
- form: bad sql expression for right check (2e9b693)
- form: bad SQL to find validator groups (42d0665)
- form: compatibility with dark theme (4c465f5)
- form: sort not applied on 1st display (cfe5347)
- form: version check on import (849db8e)
- formanswer: load answers when validating a formanswer (9ea1460)
- formanswer: no longer need to call showfields on display (9cea337)
- formanswers: execute show conditions when displaying formanswer (edd1247)
- issue: enable qtip for formanswer (72d89b0)
- issue: include 1st level validator groups of current user (f9addab)
- issue: php warning when running mailcollector (c4bc865)
- issue: restrict user dropdowns to current user in service catalog (9891c89)
- issue: update modificaitoin date when a followup is added to ticket (4d5ed7f)
- ldapfield: only last page of LDAP results rendered (ea4ddfc)
- question: make import resilient against missing parameters (1594e6f)
- section: ensure unique order for duplicate (9db4229)
- targetticket: date 'now' from a template (f40ec4d)
- apply translation on kb list (fb0f1a6)
- prevent inconsistent timestamps in DB (4b66eb8)
- responsive UI (33d8ee4)
- show menu when width is low (9ec53fa)
- targetticket,targetchange: bad return value in setTargetEntity (e0ddd2d)
- targetticket,targetchange: error when displaying tag from question settings (3c1ed6a)
- wizard: don't show tabs for KB item in service catalog (ea3afe5)
- wizard: responsiveness for mobile devices (e2508f3)
- wizard: show FAQ items only if have right (8d2cdf1)
- wizard: wrong menu highlighted when browsing FAQ (cfe2ac0)