{"id":421799,"date":"2022-10-18T12:06:30","date_gmt":"2022-10-18T10:06:30","guid":{"rendered":"https:\/\/glpi-project.org\/?p=421799"},"modified":"2025-06-16T13:19:46","modified_gmt":"2025-06-16T12:19:46","slug":"formcreator-glpi-project","status":"publish","type":"post","link":"https:\/\/www.glpi-project.org\/fr\/formcreator-glpi-project\/","title":{"rendered":"New version of Formcreator 2.13.2"},"content":{"rendered":"

This version is compatible with GLPI 10.0.<\/p>

Upgrade from 2.13.0 or later<\/strong><\/p>

A database sanity check is done before running the upgrade. If the tables of the plugin have a difference with the expected schema the upgrade will fail with a message similar to the following:<\/p>

The database schema is not consistent with the installed Formcreator 2.13.0.
To see the logs enable the plugin and run the command bin\/console glpi:database:check_schema_integrity -p formcreator<\/p>

It is required to fix the database, using the diff produced by the CLI command given in the message. Once done, try again to upgrade.<\/p>

\u2139\ufe0f If you know what you are doing you may bypass the sanity check from CLI with the following command.<\/p>

bin\/console glpi:plugin:install formcreator -f -p skip-db-check<\/p>

Possible encoding problems in tickets created in GLPI 9.5 or older<\/h3>

\u26a0\ufe0f GLPI 10.0 encodes rich text content in a different way compared to GLPI 9.5. This revealed some bugs in the plugin in previous versions and GLPI may display old tickets with HTML tags. A CLI tool is available to fix 2 types of inconsistencies. You should test the command in a testing environment or do a backup first.<\/strong><\/p>

bin\/console glpi:plugins:formcreator:clean_tickets<\/p>

Bug Fixes<\/p><\/blockquote>