I’m running into this error here on meta. I can’t reproduce it in my development environment, but I always get it here on meta.
Steps to reproduce:
- Click “New Topic” and leave the editor open
- Go to my user preferences
6 Likes
Can confirm. I am, however, able to close the error and interact with user preferences as expected, even with the post editor open.
1 Like
Hmm nope. I’ll add this bug to my list.
I get the same bug just when editing one of the “About the XYZ Category” topics. No need to navigate to user prefs.
1 Like
I got this bug earlier today.
2 Likes
Should this really be an alert? Or can it be a console.log entry?
I’m noticing it appearing on the Poll UI Plugin because I embed the editor in a Modal, while it is still open in on the topic/create new topic.
It initially took me by surprise because I wasn’t sure what “only supporting one matcher at the moment” meant, it would be nice if this were 1) more specific, such as, “AutoComplete: only supporting one matcher in an editor at the moment” and 2) a console.log statement, since it isn’t really breaking anything (from what I can tell).
On the upside this did catch a pretty ugly bug… nonetheless fixed per
https://github.com/discourse/discourse/commit/6d22354ac338fa9a98e89c67054abd77fad1c8fb
https://github.com/discourse/discourse-tagging/commit/abec4de26b3bf3d42d18b26b1c9f50d2f2c0b6a4
5 Likes