Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.
I’m submitting a…
Regression (a behavior that stopped working in a new release)
[ x] Bug report
Performance issue
Documentation issue or request
Current behavior
Prior to yesterdays update this was working fine.
Expected behavior
The rating should be saved to MongoDB.
Minimal reproduction of the problem
Create a new schema.
Add a number (set the UI to Rating (stars))
Create a content item of that new schema
Select 1 star and notice how the value is not persisted in the database
Okay did another test and this time I changed the “Editor” from “Stars” to “Input” and now I can successfully save the value 1. I still need the “Stars” editor to work however!
I also found out that when you create a new item using the API with 1 star rating then this works also. So it is only from the Editorial UI that it does not work.
It will not autodeploy, but I will deploy it today. This time you do not have to wait so long. I was afraid aboput the previous release (because of I was expecting that something will go wrong), but now the fear is gone
