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
on the frontend on the person detail view, e.g http://openhluttaw.info/en_US/person-detail/?personId=0a38ea8c39dc4fd4a5dc5504a60bfa4d , for the field “TOWNSHIP” , �It’s showing “MP for Kayah-9", which i am sure it is the data from the “post_label_en” from our sheets. But what we wish to display is something like “”TOWNSHIP - Kayah-9", so i think this data for “Kayah-9” should come from the “area_name_en” from our sheets.
But then when we pull from the “area” or “area_id” from our http://api.openhluttaw.org/en/memberships, some “area” or “area_id” are showing “null”, or some are showing popitids, like “area_id”: “4603322fe4d742bdbe0f7a6506e02b34”.
And so, Htoon Lin said he can’t make it to display the area_name from the area_id.
Can you help me how we can achieve this?
The text was updated successfully, but these errors were encountered:
i think this issue is almost resolved. I just realized/saw a simple or obvious workaround we should be using on the frontend. We will test it in few days, and will close this issue if it work.
on the frontend on the person detail view, e.g http://openhluttaw.info/en_US/person-detail/?personId=0a38ea8c39dc4fd4a5dc5504a60bfa4d , for the field “TOWNSHIP” , �It’s showing “MP for Kayah-9", which i am sure it is the data from the “post_label_en” from our sheets. But what we wish to display is something like “”TOWNSHIP - Kayah-9", so i think this data for “Kayah-9” should come from the “area_name_en” from our sheets.
But then when we pull from the “area” or “area_id” from our http://api.openhluttaw.org/en/memberships, some “area” or “area_id” are showing “null”, or some are showing popitids, like “area_id”: “4603322fe4d742bdbe0f7a6506e02b34”.
And so, Htoon Lin said he can’t make it to display the area_name from the area_id.
Can you help me how we can achieve this?
The text was updated successfully, but these errors were encountered: