- Affected version
- 2.2.13
Unlike most core functionality, the tagging UI isn't implemented via a controller plugin and thus requires each content type to roll it's own
So while tag building/changing/display uses common template/code, the actual editing UI is not standard despite being a copy&paste between the 3 official implementations thread/media/resources.
aka I want to implement some tagging UI changes but realised I need to hunt down half a dozen different *_tags` templates used for the tag editing
actionTag method in full.So while tag building/changing/display uses common template/code, the actual editing UI is not standard despite being a copy&paste between the 3 official implementations thread/media/resources.
aka I want to implement some tagging UI changes but realised I need to hunt down half a dozen different *_tags` templates used for the tag editing