That would be possible as a theme but the purpose of this component is to help distinguish topic posts from private messages. If every post appeared in message bubbles that would defeat the purpose.
This spacing should be fixed now too. Please can you update the component and confirm?
It looks good, but anyone who may have chosen “Message” is likely now going to get a bit confused, because the Reply button seems to have changed to Message (maybe a Discourse change?):
I think it’s related to a new change here:
I am so far struggling to think of text other than “
to Message” to use as appended text, that would work for both “Reply” and “Message” buttons, but if I think of something I will add it here.
That’s a recent Discourse change - and one I wasn’t aware of. It makes sense as using the word Message does help distinguish it from a Topic reply.
I presume the change from ‘Reply’ to ‘Message’ on the button is something configurable under the Customise > Text settings? It would be useful to know what Text setting has changed on Meta to use the word ‘Message’ on the composer dialogue?
NB This component feature is simply a convenient way to append (or prepend) text. The text is added to both the topic ‘Reply’ button and the composer ‘Message’ button so you will need to take that into account of you use this component feature. I could change it so you can append text separately for each button, or we could remove this feature and advise on using the native ‘Customise > Text’ functionality, if users want to change the text.
PS I simply append the word ‘Privately’ to help distinguish that this is a private message as opposed to a forum topic reply. That ‘Reply Privately’ and ‘Message Privately’ still works - but is a bit redundant now on the message button.
Good idea; I was able to change the value of
js.composer.create_pm (back?) to
Reply and achieve the same functionality as before, although with the new envelope icon on the composer “send” button (which is fine). @Osama may know of more changes that impact this theme component that we haven’t unconvered yet, given this commit and potentially any future work in this area:
I’m experiencing an inconvenience using this plugin: more often than not the message count in the header shows an unread message even though I don’t have any unread messages.
This was reported by some users and I’m seeing it too.
That message count in the header is not part of this component. That is part of the core Discourse messaging functionality.
This component simple styles the message text to look like speech bubbles.
Apologies, I got a little confused. I first reported this in the Quick messages plugin topic but thought that was a mistake and it belonged here. (I do think its a fault in the component since it only shows in the header\0