Bonjour, probablement dû à une récente mise à jour de la version de Discourse (actuellement sur la 2.5.0 beta2), je ne peux plus modifier les champs personnalisés des utilisateurs (même si tous sont toujours marqués comme « modifiables après l’inscription » dans le menu de personnalisation) — et je ne peux même pas modifier mes propres champs personnalisés en tant qu’administrateur.
Le contenu existant des champs s’affiche toujours, mais sans l’icône de crayon/édition.
Je constate également que je ne peux pas modifier l’adresse e-mail de quiconque (y compris la mienne), ce qui posera problème pour les personnes qui changent de fournisseur de messagerie puis oublient leur mot de passe de connexion.
Manque-t-il quelque chose de mon côté ou s’agit-il d’un bug ?
Weirdly, while I can find and edit the email address by clicking on ‘account’, custom fields for me don’t show up when I click ‘profile’. Only the default fields are displayed.
If I then click the ‘Normal’ menu (without selecting any of the drop down options) , some but not all custom user fields sometimes appear (but often don’t).
If the custom fields are showing and I refresh my browser, they disappear, until I click on the ‘Normal’ menu button again.
If editing my own user account as administrator, there is no ‘Normal’ menu to click on, but I get a similar temporary effect by clicking on the ‘Expand’ (or ‘Collapse’) button.
I don’t imagine this behavior is deliberate?
A second issue/request is that I think that all these fields should be editable directly from wherever they are displayed to the user or admin - seems unnecessarily labyrinthine and not especially intuitive to disallow this, especially if there are a lot of accounts to manually update, or if user is not very familiar with where settings are buried within the interface.
Fantastic!! That would be much appreciated. Happy to test anything it that helps.
**Edit - if this is not too cheeky a question, do you have a rough sense of how long it might take? I have naively been telling my existing MyBB users that their new Discourse based forum will go live on 15 March (before I discovered this issue)