When adding nodes to a taxonomy queue subqueue via the "Select title to add" autocomplete box, the results should be filtered by the same filters applicable for the subqueue. For example, if I have a vocabulary "category" (non multi-select) with the terms "products", "news", with a taxonomy queue linked to categories, when I go to add a node to the "products" subqueue it should not display nodes in the "news" subqueue.
Comments
Comment #1
franceslui commentedI also agree with what DamienMcKenna said in the bug report. This serious bug is still in version 6.x-2.0-rc3. I hope it can be fixed very soon. Thank you.
Comment #2
ezra-g commentedI agree that this is an important bug that should be fixed, but I don't think it should be marked as critical. Perhaps we need to implement a new hook for auto completion so that smartqueues can provide this functionality as well.
Comment #3
franceslui commentedOkay, it is not critical. I just wanted to emphasize that after users add a title, they expect that the title will be added. However, it is not the case and there are no errors or warnings if the new title cannot be added.
By the way, I suggest not using auto completion because users may have no idea what the first few characters are for the title they would like to add. Can we have drop down box which shows all the eligible titles that can be added?
Comment #4
amateescu commentedFixing a three year old bug feels so good :)
Commited attached patch to 6.x.
Comment #5
amateescu commentedWrong version..
Comment #6
gnugetI adding a new patch for the 7.x-2.x-dev version.
Comment #7
gnugetOks,
Here a new and improved version of the previous patch.
For made this patch was needed edit the params passed to the hook_nodequeue_autocomplete(), because in the D7 version is not used the var $where and $where_args anymore.
So, i changed the params for instead to pass the $where and the $where_args into the function is now passed the $query object and the function who implement the api now returns a new $query object with the modifications.
Comment #9
fizk commentedCommitted #6, as it has less impact on existing code in the wild. Thanks!
Comment #10
fizk commented