You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Transfered admin issue: Select fields should show select option value not the id (see first screenshot).
After investigation of this issue I come to the conclusion that this is a frontend rather than an admin or backend issue. Here the reproduced bug as seem from the admin:
The issue is that for SELECT fields admin displays the id instead of the value of the select field. However, admin displays what it is supposed to display as can be seen from the database view:
However, also the backend does what it is supposed to do as it received the id instead of the value in case of a select field as can be seen from the network response of the frontend:
In summary, I think the propoer solution involves the frontend sending the value of the registration field option instead of the id in case the registration field is of type SELECT.
The text was updated successfully, but these errors were encountered:
hard to check what option the user selected from a value
the way the registration field options work is that they have a key and a value. the key is the id and the value is the actual string it represents. when saving the key it is easy to know what option the user stored.
if we look at this as just data and strings, it does make sense to store the actual value more than the id as a plain value.
after discussing with @camilovegag we do want to go ahead with this transition but it requires changes on admin in order to make sense of previous selected values
Overview
Transfered
admin
issue: Select fields should show select option value not the id (see first screenshot).After investigation of this issue I come to the conclusion that this is a
frontend
rather than anadmin
orbackend
issue. Here the reproduced bug as seem from the admin:The issue is that for
SELECT
fields admin displays theid
instead of thevalue
of the select field. However,admin
displays what it is supposed to display as can be seen from the database view:However, also the
backend
does what it is supposed to do as it received theid
instead of thevalue
in case of a select field as can be seen from the network response of the frontend:In summary, I think the propoer solution involves the
frontend
sending the value of the registration field option instead of the id in case the registration field is of typeSELECT
.The text was updated successfully, but these errors were encountered: