Tagging support is now part of Discourse


(Neil Lalonde) #1

The discourse-tagging plugin had a good run, but the time has come to make it a core part of Discourse. @eviltrout and I spent the last few days pulling that plugin into core and merged it today. If you’re using the discourse-tagging plugin, it will no longer be loaded after you upgrade.

Currently it behaves exactly the same was as the plugin. You’ll find the settings in a new category in admin:

Now that tagging isn’t a plugin, we’ll have an easier time working on some of the features people have been asking for and solve some problems we’ve known about for a while. Some examples:

  • Tag groupings
  • Better topic list filtering with tags
  • A better UI for managing tags
  • Performance problems

Missing routes for tags.showCategory and tags.showParentCategory
Tags box should have limited width
Can incoming Discourse email support replace old ticket portals?
Receive a badge for a post into a topic containing specific tag
The «Tagging» plugin uses a discontinued «Discourse.ajax» call
Upgrade from v2.0.0.beta10 +37 to 2.1.0.beta1 does fail
(Michael Downey) #2

Yay! After updating, do we need to remove the plugin in some way?

(Robin Ward) #3

Yes you should remove the plugin from your installation. There is a piece of code present to prevent it from loading but it’s cleaner if you remove it from your app.yml file.

(Michael Downey) #4

Excellent. And I assume all the data will move over “smoothly” so no need for us to adjust any configuration in the process?

(Robin Ward) #5

Yup, it’s still using the PluginStore for data so everything will transfer over exactly. We will migrate away from that soon to use proper tables and such, but it will migrate your data automatically like in any other version update.

(Rafael dos Santos Silva) #6


This is what I’m waiting for!

(Joshua Rosenfeld) #7

Safe to assume that you guys will be taking care of removing the plugin from hosted installations? Will all previous tagging setting be assumed by core (ie minimum TL for tag creation, tag usage, etc.)?

Edit: I can’t read apparently. Ignore the second question…

(Robin Ward) #8

It’s already been removed from our hosting container, so the next time a client is deployed they will get the tagging in core as opposed to the plugin.

(Peter N Lewis) #9

What version of Discourse does this apply to?

After upgrading to the specified version, other than removing the entry from the app.yml file, is there anything else we need to do? After removing it does we need to rebuild or will the plugin just disappear on its own at some future time?

The settings move to a new location, do they also retain their values?

(Joshua Rosenfeld) #10

Today’s version - so Discourse 1.6.0.beta2.

Yes. After editing the app.yml file you will need to rebuild.

(Mr. Casa) #11

As part of moving tagging to core, Could I tag topics via API? This is useful for the private email support that was added in 1.5 to add both email and tags.to topic via API

(Robin Ward) #12

Do you mean via Discourse’s server side API, or our discourse_api gem?

Because you’ve always been able to use the JSON API our server exposes to tag things. Moving things into core does not change that.

(Neil Lalonde) #13

2 posts were split to a new topic: Hash tag problem with tagging

(Jeff Atwood) #15

Hmm the Tags page does not have a proper HTML title @neil? If so we should fix that.

(Neil Lalonde) #16

Yeah I’ll add a title. It might be a regression from the move to core.

(Neil Lalonde) #17

3 posts were split to a new topic: How to restrict tagging


###How do I create a link to a tag in a post?

I don’t mean assign a tag to topic. I want to refer someone to a list of topics that have a specific tag. So far, I’ve been creating the link manually, as in getting the link from the tags page, and then using it in my post:



(Jeff Atwood) #19

type a hashtag # then type a few characters, this works for tags or categories.

(Neil Lalonde) #20

A post was split to a new topic: Emoji in tag names

(Neil Lalonde) #21