Discourse-events 'this.router' error

[Ethsim2 (Ethan)]

@saquetim

If you encounter any issues, please report them below

on my admin dashboard of Discourse instance, where only Discourse is 8 commits behind

[NateDhaliwal]

Hi @ethsim2, could you describe the problem you’re facing here?

[Lhc_fl (Linca)]

discourse-locations Locations Plugin 🌍 is not a official plugin, I took a quick look and it does contain deprecated API. I guess you should make an update request to the plugin author

[Ethsim2 (Ethan)]

it’s the same error, reported below;

Events Plugin

before updating discourse, i had the same problem as before, and then same problem again after enabling “Custom Header Links (Icons)” [IMG_1170] [IMG_1171] after updating [IMG_1172]

but replicating on Desktop this is

[Ethsim2 (Ethan)]

@Lhc_fl

discourse-locations Locations Plugin is not a official plugin, I took a quick look and it does contain deprecated API. I guess you should make an update request to the plugin author

Locations is the plugin where i can still access it’s admin UI,

Plugin Author has been quite active on Meta recently

[NateDhaliwal]

Pardon me if I’m ignorant, but how is this relevant to this post stream change?

[Ethsim2 (Ethan)]

@Ethsim2

deprecation id: discourse-post-stream-widget-overrides

[Lhc_fl (Linca)]

Oh, I see, but this is a deprecation related to Upcoming topic-list changes - how to prepare themes and plugins, not the post stream change.

[Ethsim2 (Ethan)]

okay i’ll update discourse and then post in there if still have same UI issue with discourse-events

Edit: UI issue exists but discussion momentum is still here

[Lhc_fl (Linca)]

I took a quick look and I believe the discourse-events plugin uses deprecated code. I recommend disabling it.

assets/javascripts/discourse/helpers/event-label.js

[david (David Taylor)]

Yellow deprecation warnings should not cause errors on a site, so there is no need to disable the plugin because of those. Deprecation warnings are just there to warn developers about future changes.

The this.router error in the screenshot is unrelated to the post-stream deprecations, so I’m going to move this discussion into its own topic, and then close it since the issue is already reported over in the plugin’s own topic.