-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GLPI 10.0 compatibility #462
Conversation
07cf7e1
to
4e6a033
Compare
8d4a536
to
661f989
Compare
631aa1b
to
35bf447
Compare
35bf447
to
4d1ab73
Compare
Checked 10.0.0-rc2 with fields 1.13.0-rc2 and issue with read-only fields as reported by @stonebuzz still exist. Let me know whether I should open new issue or is it OK to report here. I've tested all the field types. These RO fields does not work completely:
It is possible to save them regardless of "Read Only" setting in field setup. Issue is also with Users field. If set to RO it is not displayed in container at all but after container saving it contains value "Myself". Also I've noticed that behavior of "Number" field changed. In 9.5.x version in allowed to enter floating point. Now it is not possible, just whole numbers are accepted, Feature or bug? Also if whole container is set as Read Only for given profile some fields are editable (you are just not able to save them):
|
4108e66
to
67c9e2b
Compare
3cdf230
to
9ac917e
Compare
- Permit installation on GLPI 10.0.x - Replace deprecated usage of Html::autocompletionTextField() - Fix DBmysqlIterator usage - Fix showForm() signature - Use same PHP minimal version as GLPI core - Upgrade to symfony/yaml 5.4 - Remove deprecated usage of integer display width - Use default GLPI charset/collation during install/update - Force database dynamic row format - Move fields display to a twig template - Display YAML export button only on existing items, and move it in item toolbar
- ignore inactive fields - fix warning when mandatory field is not yet initialized
9ac917e
to
ea7bb88
Compare
No description provided.