Uh, never mind? XD Sorry, I’ve misinterpreted what your page’s configuration is. Now I’m understanding these dropdowns all are supposed to work independently of each other, they are all essentially copies of each other, but all on the same page. I hope I have it right this time.
The behavior you describe does sound like a misconfigured multiple select setup. Please confirm that these dropdowns are NOT all in the same <form>
block. They should each have their own. And I was not entirely joking about “never mind”, forget about the array form and square brackets [], they do not apply to your configuration. (maybe it’ll help someone else finding this thread ?? )
A more likely related possibility is the javascript that submits the request (if that’s what the configuration is, more on this below) is picking up all the dropdowns at once because they all have the same ID, name, or whatever javascript is using to pick up the onchange action. Check the ID attribute for the dropdowns. They all must be different (javascript or not). But once the IDs are different, there needs to be separate event triggers to pick up each different field’s onchange event.
The javascript issue may not apply to your configuration. If the page request is sent immediately upon selection, then javascript or jQuery is at work. If there’s a submit button or something that initiates the page request, then javascript may or may not be at work. Without javascript, the single form block is the only possible explanation that comes to mind.
If javascript or jQuery is involved, then that script would need to be modified along with the ID or name of the dropdown. How that is done could be quite obvious or incredibly obscure. If the script is too obscure, it may be easier to either add a small submit (Go?) button and forget javasript, or rewrite the event handler.
Furthermore, if the script is picking up on the field name instead of ID, changing field names will require some sort of rewrite rules to cause the new names to be put back to the “cat” query var that WP needs. A script rewrite is probably preferable.
There could be another explanation, such as plugin or naming conflicts, but the above seem most likely. If you can investigate exactly how these forms are working, either a solution will present itself or we’ll know we need to focus elsewhere. Let us know what you can find out.
This post has grown quite long ?? It’s really not that complicated, just hard to explain, compounded by multiple possibilities and knock on effects. Don’t worry, we’ll work through it and find a solution.