Custom fields in my plugin: after upgrading from 1.19 to 1.26, a PATCH request doesn't populate derived fields anymore. I suspect a front-end issue

Hey @lucw, I apologize for the delay in getting back to you. We’re pretty busy with the next release.

Are the translation fields read-only or can they be modified? I would need to verify the exact version, but relatively recently, we made some changes in the frontend to ensure that the server updates only the read-only fields. Before this change, the following could happen:

  • The user modifies a field.
  • They move to the adjacent field and change another value, triggering a second request to the server.
  • The server responds to the first request and overwrites all other fields in the row, erasing the user’s latest modification.
  • The server then responds to the second request, restoring the value the user entered.

To avoid this flickering, we decided to overwrite only the read-only fields. These fields cannot be modified by the user and are recalculated by the server based on formulas. If your fields are not read-only, this might be causing your issue.