Quick Messages Plugin

Any clues where should I hunt for errors if seeing this?


Relevant .yml snip:

    - exec:
        cd: $home/plugins
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-spoiler-alert.git
          - git clone https://github.com/discourse/discourse-solved.git
          - git clone https://github.com/discourse/discourse-voting
          - git clone https://github.com/discourse/discourse-checklist
          # slack integ
          - git clone https://github.com/discourse/discourse-chat-integration.git
          - git clone https://github.com/discourse/discourse-policy
          - git clone https://github.com/discourse/discourse-calendar

          - git clone https://github.com/angusmcleod/discourse-question-answer
          # chat plugin
          # - git clone https://github.com/gdpelican/babble.git
          # quick messages
          - git clone https://github.com/angusmcleod/discourse-quick-messages
          # parallel editing
          - git clone https://github.com/gdpelican/collude
          # reactions
          - git clone https://github.com/gdpelican/retort

Hey @pihentagy, do you mean the fact quick messages is not linked to a repo and doesn’t have a settings link? This is just because I hadn’t hooked up this metadata for the plugin.

You can find the quick messages settings by going into your settings and searching for “quick messages”.

In any event, I’ve added that metadata in :slight_smile:



Did you figure out a solution for this?

Unfortunately not. :expressionless:

@jord8on Hey, are you talking about this?

Happy to add it into the work schedule if we can:

  1. Get a feature request: Feature Request

  2. Get 5 votes or a sponsor for it.

See further here: https://discourse.angusmcleod.com.au/k/how-to/how-to-request-a-plugin-feature/894

cc @terraboss

1 Like

Plugin outside

Yes on mobile devices the chat windows renders outside the screen. On my forum it is the same.
Is there a solution for this?

@hewo7 @Bank_Live Thanks for the prompts about this. I’ll fix it tomorrow :+1:


@angus A great plugin, works perfectly!

I guess this isn’t a priority at the moment, but while you are fixing things, would it be possible to fix these:

New Message text is a bit off.


Emojis and Image icons are not alligned properly.


Maybe move this field, as well as the icons, as they are too close to the edge on the top.


Thank you and once again, well done!

1 Like

@Bank_Live @hewo7 The mobile UI bug is fixed:


@calebs I’ve also made some style tweaks and some other fixes



@angus Thank You! Works perfect! :+1:


I seem to be getting a bug where users can carry on typing below the visible screen. I’ve turned off all plugins which i’m able to turn off and the issue remains. Is anyone else having this?

1 Like

Thanks @AndyatFocallocal I’ve pushed a fix for this.



Thanks for creating and maintaining this awesome plugin, I have encountered a few issues with this:-

  1. The images are being shown fine inside the message box but the lightbox doesn’t work. Clicking the image takes to image link and doesn’t show it in the lightbox, thus breaks the conversation. Is there a way to disable lightbox in a quick message window or have lightbox working properly.
  2. It doesn’t mention the subject of the message anywhere, and thus the message list becomes very hard to recognize.
  3. It doesn’t display the message in the mobile view.


And shows following in the console

_application-91a6f00c2b614e1bd00e24153375bde25ec3d14f53dcdcfc6a19c8d7ea0e5d89.js:14093 Uncaught TypeError: e.substr is not a function
    at n.excerptTruncated (_application-91a6f00c2b614e1bd00e24153375bde25ec3d14f53dcdcfc6a19c8d7ea0e5d89.js:14093)
    at n.<anonymous> (_application-91a6f00c2b614e1bd00e24153375bde25ec3d14f53dcdcfc6a19c8d7ea0e5d89.js:83)
    at n.i.get (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:27422)
    at J (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:25836)
    at t.r.compute (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:13693)
    at t.value (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:13431)
    at t.value (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:57889)
    at e.t.initialize (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:57350)
    at e.t.peek (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:57325)
    at Object.evaluate (_ember_jquery-d430881a3fb1403871256e5a02423c4b20a78793685e92088613ca9a701baf88.js:58536)

Is this a plugin or a theme? The former is added by editing the yml file, the latter the UI

1 Like

The feature isn’t live on the sandbox? (https://thepavilion.io/) I’d love to see the plugin in action.

Is there a way to allow only certain ‘groups’ to use your Quick Messages Plugin :question:

If not, would you consider adding this feature :question:

By the way, we use Quick Messages a LOT and love it but would like to limit its’ use, perhaps trust level would be another acceptable way to do that…

EDIT: Ooops, we just figured out how to acceptably manage this using your ‘quick message required badge’ settings parameter…


Are mobile devices supposed to be able to work with this plugin? When I attempt to use the Quick Message interface on my iPhone Xr in Safari in iOS 13, I experience various UI bugs. I cannot tap into the text box to enter a username for the recipient because it doesn’t register the tap. Also, when I start type and then tap outside to hide the on-display keyboard, the message box extends up into the header of the forum page so I cannot close the message box. Very strange. I wanted to use this in lieu of Babble, but it has so many UI issues that it’s not currently an option.


What version of iOS 13 are you on? Have you tried updating to the latest version?


I am on the latest release. I have access to several different iPhones and I think the issue comes down to the curved screen with the sensor cutout or “notch” at the top. The Xr and 11 Pro (standard and Max) have this issue, whereas the iPhone 6S does not. It may be that Safari is to blame for improperly rendering the display boundaries in interpreting the code.

1 Like