-
Notifications
You must be signed in to change notification settings - Fork 69
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
Impossible de mettre à jour le plugin au delà de la version 1.18.0 #817
Comments
Bonjour, avez-vous trouvé une solution à l'époque pour ce bug ? |
Bonjour @billtemate Non du coup, on est obligé de resté en 1.18.0 pour le plugin mais c'est un peu embêtant qu'on ne puisse plus le mettre à jour. Sachant que du coup on ne bénéficie pas de la correction du problème de doublon dans l'historique |
Hi It is possible that the concerned column has been incorrectly renamed. Could you check the columns in this table, identify the one with the incorrect renaming, and update its name to match the one shown in the error? |
Hi, I have tried to rename 3 columns and 1 table: ALTER TABLE ALTER TABLE ALTER TABLE ALTER TABLE This allows me to display the tickets and to expand all the dropdown lists. However, I have 2 lists where the history does not show, and if I select a value and save, it does not retain the selection. See the screenshot in debug mode. Thank you very much. |
Bonjour,
Nous sommes en version:
GLPI: 10.0.16
Champs supplémentaires; 1.18.0
Toutes les versions supérieures à 1.18.0 nous font l'erreur suivante :
![image](https://private-user-images.githubusercontent.com/151614740/359226656-f4c60cc3-22dd-47de-9751-da2ec952fb64.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MjEzOTMsIm5iZiI6MTczOTYyMTA5MywicGF0aCI6Ii8xNTE2MTQ3NDAvMzU5MjI2NjU2LWY0YzYwY2MzLTIyZGQtNDdkZS05NzUxLWRhMmVjOTUyZmI2NC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNVQxMjA0NTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00MDY3MDgwZTIzMWVkMjZhOTQxZmE4ZjAwYzM4NTRlYzFlYjJhNmEyZGRmZjJlYjJhNDUyN2MzZTRlYjc5OTBlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.vkL0a9TAKcjWFerWH__dwdPnqTnWhQw0fElTApN7ILI)
La mise à jour nous permettrait de corriger ce problème:
#685
Merci
The text was updated successfully, but these errors were encountered: