[BUG] Unable to change between New Topic and New Message options on Discourse
gnikit opened this issue · 8 comments
I noticed a change in Fortran-lang Discourse and I am relatively sure that it is a bug. When creating a new topic you used to be able to choose by clicking the + sign between:
- New Topic
- New Message
Now the only available option is the New Topic.
The easiest way to send a message now is: Go to your profile > Messages > New Message and even then the only available option when pressing the + sign is New Topic
How do you know it's a bug and not an intentional UI change? I agree it's not as easy to send messages as it is to open new topics.
Another "easy" way to send a message is to click on a user and press the "Message" button.
How do you know it's a bug and not an intentional UI change?
I would suspect that if it was a feature in the second case you would be able to swap between New Message and New Topic, but if you click New Topic, you are unable to get back to New Message, so you have to discard the message and start again.
I agree that's weird UI, though I never tried doing that (I didn't even know you can click on the + or the envelope to change the mode until just now).
Another thing I noticed on Discourse that might be related to things "breaking" or it might be a completely other thing that needs its own issue, is that replying to someone's answer does not always show once you post your reply. I do not recall that always being the case and I have examples as new as 6d ago where it worked. Maybe it is has something to do with the category of the posts? I really don't know.
What I typed:
vs How it displays:
thread is here: https://fortran-lang.discourse.group/t/fortran-developers-poll-2022/3877/6
What is should look like:
thread is here: https://fortran-lang.discourse.group/t/asking-questions-in-fortran-lang-already-posted-in-stack-overflow/3828/5
As I understand it, the "in response to" is shown only if the response does not immediately follow the post that it responds to. I believe it's been like this since the start of Fortran Discourse.
Anyhow, these kinds of issues and questions won't be resolved by us but should be directed to https://meta.discourse.org/.
Thanks, I suspected it might related to upstream.
It's still useful to raise these questions within Fortran-lang, as there have been many tweaks to the Fortran Discourse that we could change on our end, so I didn't mean to discourage you from opening them here. Opening a Meta post on Fortran-lang Discourse is more appropriate for those than a GitHub issue here.
Sure thing, and I of course I am not discouraged by your reply, but I closed the report promptly to keep the number of open issues to a manageable level. Will post on Fortran-lang>Meta next time, cheers.