I can give it a go, if you’d like. I’ll need a couple of days to search through Discourse’s forums, & github code, to see if I can code a solution that doesn’t get overridden on updates, and one that doesn’t need to force the user’s db table Zone column public, but respects the user’s “hide my public profile and presence features” setting. Unless, you want it to be forced public (then, following that link’s post may be simplest)? Also, I have 80+ pawpaw seedlings to pot
The zone field you added is a text input field, so, if we can get it to show after the user’s name, @Janne.L & others could also write non USDA zones if they wanted (or, anything they wanted to show after their name…). Could potentially be abused, but converting the zone column to some other integer(s)/letter(s) (5a, 5b,…), limited, input, might be much more complicated, and probably force everyone to need to re-update that info. Although, that would make it easy to do things like custom css that colors the zone info differently, If you wanted to - like; zone 2 blue, zone 6 chartreuse, zone 8+, red, etc. but now I’m getting carried away. Might also want to show the Location field, or merge it with Zone field, as they seem to be basically the same thing; into one custom field that user’s can have show after their name, but that’s all up to you.
If you want the zone field forced public, following that link’s solution should work. I think you would just need to change version=“0.8.27” to whatever version you currently have, the number after user_field_ to whatever the Zone field is in user_fields.json, and copy-paste that script into the /header section under Themes, under Customize, after adding the user_field_# to the ‘public user custom fields’ site settings; but, disclaimer, I don’t have experience with Discourse , but I can learn it fast enough, just give me a few days if you’d like. I came across some of your posts in that Discourse dev forum; amazing what a site like this can cost every month, and you are providing it to us for free! So, thank you!, @scottfsmith.