custom taxonomy add like tags

The backend taxonomy displays as checkbox. The plugin also has a checkbox option, isn’t that sufficient for you need?

User musst Add taxonomy. Only to display avaiable Taxonomy is not a Solution.

new urls musst be created…/place/city

Right, the taxonomy creation feature yet not available in the plugin. So you could add a new “Action Hook” field and add a new text input field and using the wpuf_add_post_after_insert action hook, you can create the taxonomy.

Check the developer docs and the plugin integration area for hook list and example.

I found out only that this is not an option after i just bought the plugin. I think it should be a standard inclusion in this plugin. It is just a pity I couldn’t read all the forum post as I need this in my requirements. I think the plugin is far from complete

@kolhoffmmm, for only this one you think it’s far from complete?

I would have thought it being a standard as it is common to have a custom taxonomy for a custom post type. and tags are normally freely choosable not like categories which are normally well defined so a dropdown or checkbox will work for those, but they won’t work for tags. So yes for me it is one big thing missing to make this plugin incomplete.

Your current solution only allows a dropdown/checkbox and even that is not working nicely on custom tags (not categories)

@Tareq
I bought the Pro version, because I assumed I can cutom Taxonomys used as tags.

From your homepage
————————————————————-
Custom Taxonomy
Add your custom taxonomies to the form. Use them as Dropdown, Multiselect, Checkbox List.

Add your custom taxonomies to the form.
In Germany
Fügen Sie Ihren kundenspezifischen Taxonomien auf das Formular.
—————————————————————

The Description ist not really clear.

Add New is an necessary Feature.

Is ist possible to add this feature in the next Version?

Yes, I am considering it to add in the next version.

I said add taxonomies TO THE form and use them as dropdown…, not FROM THE form. I didn’t mentioned any feature thats not in the plugin 🙂

Marking as resolved as the solution is provided here.