(deprecated) Plugin outlet locations theme component

[RGJ (Richard - Communiteq)]

Another update, now including the wrapper outlets (and a link to the source file in Github when you click on any outlet)

And the last one for today: a setting to show the toggle to administrators only (thank you @pfaffman for that good idea )

[Arkshine]

Awesome! Thanks for the update!

Do you think it would be possible to support plugin outlets in raw templates?

[RGJ (Richard - Communiteq)]

Raw hbs are going away if I have understood correctly

@david

Now that the Ember 5 upgrade is almost behind us, removing widgets and raw-hbs is the main focus for our ‘modernising JS’ team

[Arkshine]

@david

It’s a similar story with the ‘raw hbs’ implementation of the topic list. It will be updated, but we don’t have a concrete plan/timeline yet.

Now that the Ember 5 upgrade is almost behind us, removing widgets and raw-hbs is the main focus for our ‘modernising JS’ team

I completely missed that part. Okay, nevermind then.

[mgol (Michał Gołębiowski-Owczarek)]

Thanks for the plugin! Can you add a license to the repository? It doesn’t have any now.

[RGJ (Richard - Communiteq)]

Thank you for pointing that out. I’ve added the license (MIT)

[mgol (Michał Gołębiowski-Owczarek)]

Thank you!

[Lilly]

@Canapin

There’s a little bug with the new user card as a theme component. I’m not sure it would happen when it’s shipped in core (if it is). Still… the outlets in the experimental user card still show up when outlets are toggled off:

Looks like this may have had a regression recently

[RGJ (Richard - Communiteq)]

Good spot @Lilly thank you!

There is a very broad CSS selector, just targeting div in there, so this is not something that’s only going to happen to the plugin outlet locations theme component, it’s something that’s going to be happening to everyone using these plugin outlets.

So instead of doing a lot of fragile CSS workarounds @jordan.vidrine maybe this is something that can be addressed in the user card theme component?

[Canapin (Coin-coin le Canapin)]

Another outlet showing up on the user summary page even when toggled off: user-profile-secondary

[david (David Taylor)]

I’d recommend checking out Introducing Discourse developer toolbar. The integration with core means it can provide a more robust experience, and include more plugin outlets.

user-profile-secondary correctly hides/shows there.

I’ll add a note about core’s new plugin-outlet feature in the OP. Hope that’s ok @RGJ. Perhaps we could also update the theme-component itself with some kind of deprecation message?

[Canapin (Coin-coin le Canapin)]

Thanks David, I’m aware of the dev tools I use on my local dev install, but I sometimes use the unofficial TC on production installs, especially when I don’t have access to my computer.

Or is there a way to enable these tools on a production install?

[Moin]

@Canapin

Or is there a way to enable these tools on a production install?

@david

In production, it can be enabled by running enableDevTools() in the browser console.

[Canapin (Coin-coin le Canapin)]

Gotcha, missed this part. Thanks! Time to remove the TC from my forums.

edit: and thanks, Richard, for this very helpful plugin I’ve used over the years, of course!

[RGJ (Richard - Communiteq)]

@david

Perhaps we could also update the theme-component itself with some kind of deprecation message?

Yes, I will do that in the next few days.
LOVE the new developer toolbar by the way!

[Arkshine]

Now that it’s integrated into the core, I just wanted to thank you, @RGJ, for initially creating this TC!
It saved us a lot of time, for sure.

[Andrew_Rowe]

@david

In production, it can be enabled by running enableDevTools() in the browser console. You can even try it here on Meta!

yes, this is awesome

[Monikas (JustMonika)]

It’s sad to see Theme component at the end of its life.

[RGJ (Richard - Communiteq)]

Did you see the developer toolbar? It’s so much more awesome!