After a lot of swearing through gritted teeth I discovered that, much like the reserved term issue that results in a 404 error (‘page not found’) when processing a form:
the same thing happens when using custom taxonomies. In my case the problem was the
<select name="taxonomy">I was using for a drop-down. Change it to
<select name="get_taxonomy">and the form now processes properly.
- The topic ‘Custom taxonomy cause 404 errors with forms’ is closed to new replies.