Craft 5 Support

[theAdhocracy]

I realise that the entrification plan for Craft means that Tags will ultimately be rolled in Entries, but until a similar field UI is created, many people are continuing to use them. For Craft 5, this means there is no longer any way to view and edit Tags, without going via another content entry.

Basically, this plugin remains very useful and it would be great to see it get bumped to Craft 5, even if no other development work is planned 🤞

[joelzerner]

Completely agree, would love to see this ported over to Craft 5. The field UI in it's simplicity and speed is top notch and perfectly handles this type of tagging functionality.

Not sure what the migration path away from tags will be if we have to switch to using Entries instead.

[rob-c-baker]

While having this in Craft 5 would be great, due to time pressures, we took the decision to bite the bullet and convert the tags we use into entries - via the "entrification" command line tool. It worked pretty well. In terms of changes to templates - there were not that many and those that were needed were generally just things like swapping in a sectionId instead of a tag groupId. There would be more changes if querying tags from PHP context as it's a different element / model to start the query.

I started here: https://craftcms.com/docs/4.x/console-commands.html#entrify-tags - the command walks you through in a non-live environment, you can then make any template / code changes necessary and roll it all into a single deployment. There is one thing that is out with the normal deployment process: The command adjusts the data schema that the CMS works with and the last thing it does is provide the command that is needed to run on live directly (and manually) after deployment - this command moves the data from the removed tag groups into the newly created entries, based on the schema changes that arrived in the environment via project config.

Our tags are now entries, they are managed by the core CMS interface and we have one less dependency.

[smockensturm]

@joelzerner

"The field UI in it's simplicity and speed is top notch and perfectly handles this type of tagging functionality."

https://craftcms.com/docs/5.x/reference/element-types/tags.html

"A comparable tags field UI has not yet been introduced for entries. If you or your clients value this authoring experience, it is safe to continue using tags!"

We're at 5.5 now. What's the plan @brandonkelly ?

[theAdhocracy]

Just adding in here that it is pretty simple to fork this plugin and get it working with Craft 5. The only thing you need to change is the following in the composer.json:

 "require": {
    "craftcms/cms": "^5.0"
  },

Then modify your Craft project's composer.json in the way outlined in this comment, or like so (replace the bit in the github URL):

{
  "require": {
    "ether/tags": "dev-master"
  },
  "repositories": [
    { "type": "git", "url": "https://github.com/{...YOUR REPO...}/craft-tags" }
  ]
}