TYPO3 Core

Hi,

A few weeks ago I had this topic on my desk as work for a client of mine. We are currently evaluating to publish the solution to an open Git repository.
What I'd like to point out is that there was/is no reason for an own render type for tags but simply re-use the existing groupbox.

What we basically did for haven a flexible tagging api in the projects:

• introduce an own tag table (flat hierarchy, non translatable)
• introduce some PHP api to add tagging fields to a table (similar to \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::makeCategorizable)
• we use group fields with internal_type db
• the suggest wizard is configured using an own receiverClass
  • if the query result is empty (no matching tag yet) or the query result doesn't contain the exact search word, a new element "Create tag" is added to the autocomplete list
• we extend / overwrite the FormEngine-JavaScript
  • new tags ("Create tag") are attached to the groupbox but not yet saved to the database
  • the identifier (NEW-uid) is stored within the form to be able to use new tags multiple times (e.g. if you have multiple tag fields)
  • after adding an entry to the groupbox the suggest field is emptied and focused again

The client and me decided to not introduce a new render type for the tag-handling but to re-use the groupbox. That way the editors to not have to manage yet another field type and the groupbox is perfectly fine to handle all needs.

Maybe these thoughts help you a bit.