not pressed “New Topic” button. How to solve this problem?
Is discourse presence plugin compatible with ember 2.4?
Okay, I see what you are referring to now. This is due to using the Material Design customizations. Not a bug in Discourse.
With the Ember upgrade, the Material Design customization is broken.
ping @rewphus (I’m sure you are likely busy, but this is more of an FYI).
Disable all changes to CSS, the problem is the same. The button “New Topic” does not work.
JavaScript would be adding that button, that floating new topic button doesn’t exist here on Meta. So it is definitely customization related.
Also the error message references plugin-third-party, which means it is either plugin related or customization related.
I’ll take a look, but the button should be JavaScript free. I simply repurposed the existing New Topic button.
Since it is possible to find out the reason why there were these mistakes? And whether they are associated with a broken button “New Topic”?
ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:17
DEPRECATION: `discourse/views/topic-status` was moved to `discourse/raw-views/topic-status`
o @ ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:17
ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:11
TypeError: Cannot read property 'id' of undefined
at r.addUser (plugin-third-party-d1cfc0345c6ccf870d483818ab57590cdc4dd4ae06f941bc763cf99d9982005b.js:3)
at r.isOpened (plugin-third-party-d1cfc0345c6ccf870d483818ab57590cdc4dd4ae06f941bc763cf99d9982005b.js:3)
at Object.p [as applyStr] (ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:9)
at Object.d [as sendEvent] (ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:8)
at b (ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:9)
at Object.s [as propertyDidChange] (ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:9)
at Object.c [as set] (ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:9)
at r.set (ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:12)
at r.value [as _setModel] (application-d4b2d7f0cdaf202455de0c1c5ca14493ed5b86bde273db5e51ceaa34e4818ad5.js:9)
at application-d4b2d7f0cdaf202455de0c1c5ca14493ed5b86bde273db5e51ceaa34e4818ad5.js:9
s @ ember_jquery-37ec8949e7219a8c2b3cdebef9d43bc64a66860ec196f3e10bea842d0296256f.js:11
@sam please help to fix the button “New Topic”?
When pressed in the browser chrome firefox nothing happens. And the field of a new message or reply does not open.
What plugins do you have installed that are not official? As the error references plugin-third-party
meaning you have a plugin that isn’t playing nice.
And if you do not have any other third party plugins enabled, what customizations do you still have enabled?
I like almost all disabled plug-ins that could affect the operation of the button. But she had not earned. ((
One of these plug-ins caused this error.
##- git clone GitHub - discourse/onebox: A gem for turning URLs into website previews
##- git clone GitHub - discourse/discourse-solved: Allow accepted answers on topics
##- git clone GitHub - discourse/discourse-adplugin: Official Discourse Advertising Plugin. Install & Start Serving Ads on Your Discourse Forum
##- git clone GitHub - discourse/discourse-slack-official: Official Slack integration for Discourse
##- git clone GitHub - discourse/discourse-translator
##- git clone GitHub - discourse/discourse-cakeday: Show a birthday cake emoji beside the names of members on their join anniversary, or their actual birthday -- and a browsable directory of upcoming anniversaries / birthdays.
##- git clone GitHub - discourse/discourse-spoiler-alert: A plugin for discourse to hide spoilers behind the spoiler-alert jQuery plugin
##- git clone GitHub - discourse/discourse-canned-replies: Adds a means to insert templates from the composer.
##- git clone GitHub - discourse/discourse-presence
I submitted a pull request that fixes this (for us).
The fixed version is deployed on the Blockstack Forums.