Rather than having code to handle display of the moderation queue, it would be neat to make this module Views-enabled, so users could have fine-grained customization over how the list looked and who had access to it.

Comments

pwolanin’s picture

pwolanin commented

Well, I know zero about making this happen (still avoiding the views module- probably to my own regret), but I think it's important to not make the module dependent on the views module (modr8 module description - "Easy, dedicated moderation of content").

yched’s picture

yched commented

+1 on this idea - More and more modules move towards delegating their contents listings to Views module (OG, Audio), and that is a really good thing IMO.

The tricky thing here might be that Views is currently not very form-generating oriented, I think.

pwolanin’s picture

pwolanin commented
Status: Active » Closed (won't fix)
haggins’s picture

haggins commented
Status: Closed (won't fix) » Active

Maybe it would help at first when there would be a (ajaxified) path to approve a single node. I.e admin/modr8/approve/$nid

So we could create a list of nodes in moderation status of an exposed content type (for all who are not familiar with views: this creates automatically a customizeable content-type filter above the list) and provide a link to moderators to approve each single node. In the first step I think it would be enough to provide such a link or even an ajaxified one.

mathankumarc’s picture

mathankumarc commented
Version: 6.x-1.x-dev » 7.x-1.x-dev

New features are going into 7.x