Page 1 of 1

Errors after updating to 3.4.4

Posted: Tue Mar 05, 2024 1:42 pm
by shddcit
Errors after updating to 3.4.4

- After updating Hesk to version 3.4.4, when changing even the theme of a request for some categories, which cannot see the mandatory fields for other categories, it began to require that these fields, which are not needed for this category, also be filled in when saving changes.
- The mandatory fields selected in the settings are for other categories. This was not the case before the update.
Example of error message:

Error
Mandatory field not filled: Department/Chair/Institute
Mandatory field not filled: Request Category
Mandatory field not filled: For which unit is the purchase made
Mandatory field not filled: Purchase Type
Mandatory field not filled: Responsible Person for Purchase
Mandatory field not filled: Cartridge Receipt
Mandatory field not filled: Storage of Used Cartridge
Mandatory field not filled: Allocated Amount for Purchase
Mandatory field not filled: Rector Responsible for Funds

Re: Errors after updating to 3.4.4

Posted: Tue Mar 05, 2024 3:43 pm
by Klemen
Hi,

Thanks for reporting. I did some testing - confirm this happens only when you EDIT a ticket? Otherwise it works OK?

Re: Errors after updating to 3.4.4

Posted: Tue Mar 05, 2024 3:52 pm
by Klemen
And related question - does it fix the issue for you if you upload this edit_post.php file into your Hesk admin folder (overwrite original file)?
https://hesk.com/extras/hesk3/hesk344_edit_fix.zip

Re: Errors after updating to 3.4.4

Posted: Wed Mar 06, 2024 3:14 am
by shddcit
Yes, this happens only during editing. At least, this problem did not occur when creating requests, only when editing them.

After replacing the file with your new one, the problem disappeared.
Thank you.

Re: Errors after updating to 3.4.4

Posted: Wed Mar 06, 2024 8:50 am
by Klemen
Glad to hear that solved it.

This is a new bug we created when solving another bug, but didn't notice it during the testing as it only happens in special cases :oops:

We will wait a few more days to see if anything else surfaces, then release a minor update to include this fix to everyone.