Pagers should probably be added to the accessible content pages. As it stands now, those tabs become fairly useless on a site with thousands of nodes (especially the view and edit ones).

Comments

crea’s picture

crea commented

I would say, effort must be spent towards Revisioning Views integration. These listings in MG exist purely for Revisioning. Please see #463652: Add Views Support

mcarbone’s picture

mcarbone commented
Status: Active » Postponed

Valid point.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Agree with both crea and mcarbone that a previous/next/skip-to pager would be a nice feature.

I suspect there may be some complications in implementing it through a View as the data shown under "Accessible content" isn't a straight "view" in the SQL/Drupal sense. The data is filtered by the special Module Grants content access function. Is it easy to pass the data through this filter in the context of a standard Drupal view?

crea’s picture

crea commented

Rik I think you will have to ask that in Views queue.

mcarbone’s picture

mcarbone commented

I think you could do it through the views handlers somehow.

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Postponed » Closed (duplicate)

Will come out of the wash with #463652: Add Views Support

endiku’s picture

endiku commented

Revisioning combined with MG is a fantastic combo but I do not see the logic in the statement that Accessible Content via Module Grants is a revisioning issue or "exists purely for revisioning". The Accessible Content listing is a fantastic tool with or without Revisioning.

The idea that a module should be tooled with only one other module in mind is typically not a good way to go unless it is truly a sub-module. Accessible content stands out great on its own. In the cases where Revisioning is not installed MG can still do a lot of good and Accessible content is still a great tool to manage content. The problem of thousands of nodes and no filter and/or pager to deal with those nodes is a problem that MG itself should address and not be farmed out to the Revisioning module. Otherwise Revisioning becomes a requirement instead of supported.