The attached patch adds another filter option, to filter on node types too.

I think the final aim of this feature would be to get an UI like this:

[view posts that are updated or promoted v]
[and v]
[of any type v]
[and v]
[in vocabulary v]
[and v]
[in term v]

the [and v] would be dropdown options where one can choose booleans OR or AND

the [in vocabulary v] and [in term v] will appear only when appropriate.

Lets say someone has assigned vocabulary 'drinks' and 'food' to blogs. When in 'type' the option 'of type blogs' is selected and [go] is pressed, then all vocabularies assigned to type blog appear in the selection box. In our case that would be 'drinks' and 'food'
If one selects 'food' and presses [go] again, the terms in vocabulary 'food' will appear in yet another selection box.

Anyway, this patch only allows one to select by type. But i'd like the above thing to be in drupal, since it allows us to better 'manage content'. And since drupal is a CMS, thats what we want.

Comments

Bèr Kessels’s picture

StatusFileSize
new7.52 KB

Updated some features. The UI looks like the filter-UI in mozilla mail. (well, a little :) )

Also multiple node-deletion is provided now, with confirmation.

please test, and give feedback!

Bèr

Bèr Kessels’s picture

StatusFileSize
new4.28 KB

Adding a screenshot

moshe weitzman’s picture

Project: Feature » Drupal core
Component: User interface » node system

does not apply cleanly against current CVS. please resubmit a patch.

Bèr Kessels’s picture

A new and imo better issue on this is opened at http://drupal.org/node/view/6781

laird’s picture

This patch is _not_ a duplicate of http://drupal.org/node/view/6781, as it supports batch deletion and more filtering than that patch, so I'm making it active.

This patch doesn't apply against 4.4.0, and I've had only moderate luck applying it manually. But having this functionality will make Drupal way more usable for managing large volumes of content. Is anyone else working on updating this patch?

jonbob’s picture

Bèr Kessels’s picture

Stevens overhaul of the /node/admin screen fixed this.

Anonymous’s picture