메타에 부정확한 플러그인 사용 가능 정보 표시

Here on Meta, some plugins include this callout saying they’re “available on all of our hosting tiers” when that’s not correct:
image

In some cases, that’s become inaccurate because the new free tier excludes the plugin. In others, an even higher tier than Starter is required. Per Discourse pricing, some examples are:

Math, Cakeday: require Starter or higher
Solved, Yearly Review: require Pro or higher

Some, like Subscriptions, do have correct notes…
image

…but maybe there should be a general checkup of these notes for official plugins.

4개의 좋아요

Some also still mention “Standard” instead of “Pro” :woman_shrugging:


Just a quick note in case anyone wants to update these: The category structure on Meta has changed so #bug no longer results in a category mention, so whenever you edit a topic of an official customization the category mentions in this block at the top need to be updated to continue to work as expected. Otherwise the result is:

3개의 좋아요

I’ll give this a bit of thought in the next day or two. I’m wondering if there’s a small change we can make here to reduce the need to keep two things in sync.

I suppose you could do something like image

Could even link right to https://discourse.org/pricing#compare-plugins, though you might want some scroll-margin-top to keep the headers from hiding a few lines:

(opacity hacked)

2개의 좋아요

That’s exactly the kind of thing I had in mind. I didn’t realize there was already a direct link to that section (I looked, and somehow missed it).

1개의 좋아요

I don’t think there’s a direct link on the page, but you can target an element with an id, and in this case the table itself has one:

image

2개의 좋아요

How does that work for plugins that aren’t on discourse.org? Like Discourse Staff Alias?

1개의 좋아요

Ah, yes – Staff Alias currently says
image

I guess only the plugins with a link to Discourse.org in the callout could be revised like my example. (Unless they wanted to update that plugin list to be comprehensive.)

2개의 좋아요

There’s been some discussion about this but I don’t think we’ve quite settled on an approach yet.

So perhaps we circle back to this part later.

1개의 좋아요

There should be some scroll margin on this now :+1:

1개의 좋아요

On the same subject: the “included in core” concept has been causing quite some confusion. In Communiteq we seem to keep having to explain that “included in core” does not imply “included in all hosting plans” and I’m pretty sure that is not only happening to us.

It would be good if this was explained better / more clearly somewhere.

2개의 좋아요

There sure is – looks perfect!