-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[9.5.3] - Missing type for Ticket template! #8418
Comments
This problem seems to occur when we add a solution with a category selected, which in our case is always! |
Same problem here. Also, if you try to assign the requester as technician, the same error occurs. |
I had to clear the 'Ticket template' from Entity and put it in the users profile to get rid of the error message. In the settings of the user I cannot choose 'Default entity' (it's empty, it's cleared everytime I try to change it). |
Confirmed! I had to remove the template from each entity and apply it to the Profiles. |
Hi, |
Can confirm the issue is present. I don't think the workaround is a good idea if you have a lot of people in one entity. |
HELLO! |
@trasher and Teclib Groups! just to inform them. I upgraded to version 9.5.5 and the error reported on that issue in 2020 still persists. The gif is fast. But follow the printout of the error message log in php-erros.log log in sql-erros.log |
Hi, So it seems to be a problem that have to be fixed in FormCreator plugin. Please open an issue on plugin repository. Regards |
Hi @phamorais I opened an issue in Formcreator, linked to this one. Could you share in the Formcreator's issue the complete backtrace. Your tail command returned too few lines and the beginning of the backtrace seems missiing. Also, please confirm that the ticket being created has a group in the actors. It seems this is important to reproduce. |
Hello.
After upgrading (today) to 9.5.3, we are getting lots of errors in php-errors.log saying Missing type for Ticket template!
What is it?
Logs
php-errors.log
Screenshots
The text was updated successfully, but these errors were encountered: