Is it possible to have the native functionality of parent and child tag groups within the wizard? For example, I have created a new tag group “Test - Parent Tag Group” with a tag test-parent, then another tag group " Test - Sub Group 1" with a tag test-sub1 and set this tag group to have a parent of " Test - Parent Tag Group".
In the Discourse composer I would only see test-parent as my only option until I select that tag, then I can see test-sub1. In the wizard, if I add both of these tag groups, then I see both:
I’m looking to move from categories to tags with sub tags for each ‘category’ tag. Not having this functionality might be a deal breaker for me. I may be forced to move back to the composer for creating topics, which would be very unfortunate. Thanks guys!
I’m trying to approach this another way by having two tag fields, one with a primary tag group and another with a secondary tag group. Of course, you can only use one tag field in the action section. So I’m trying to workaround this by having if statements for the tag; if w{step_1_field_1} is tag-name, then apply that tag, but I’m having an issue of it recognizing the tag from the tag field. For example this does not work:
So I tried outputting the tag in the composer to see what the tag field was returning, which was [“abstract”], so I tried that in the text field with = and is but nothing seems to work. Any ideas how to get it to recognize this?
I’m also curious, is there any active development happening anymore @Angus? I’m starting to wonder if using the wizard going forward is the right move for us if development has stalled.
Nevermind all that, after working through this with the help of AI, it seems there’s no way to achieve what I want. Instead this is now a feature request. What I really need is the ability to have two tag fields that can multiple tags, and then merge those on topic creation. So, the main thing I need is for the tags action step to have an AND option instead of just OR
Hey David, you’re right that there is no active development on the plugin. Unfortunately we couldn’t make the economics of maintaining this work out.
We paused all payment collection on custom wizard subscriptions in 2025, and will be removing all remaining subscription code in the coming months as all legacy subscriptions phase out.
While the plugin does still work, it is unlikely we’ll be adding new features.
I’m sorry to hear that Angus, for you and everyone using it. Will it be maintained to keep working for Discourse changes, or is this the end of the road?
