"Content summary" menu item (View)

Yeah, it's a bit of work in progress. It's meant as a customisation starting point and an alternative way to present the information found under Accessible content.
I'm hoping for feedback from people like you to evolve it in something that has wide appeal.
Being a View it is meant to be configured to your personal liking.

While content titles may be shown, clicking on them is still subject to the access rules enforced by core and Module Grants (if installed).

Closing after 3 months of no activity.

Default access control for the content summary view is role = authenticated user, a more secure access control would be allow access only to those with a particular permission, say 'edit revisions'.

Patch attached to change default view.

Thanks for the sugguestion!
Rik

I don't understand how to change the access to the menu item "content summary" ??
I have patched the file revisioning.views_default.inc too
I have changed manually the settings in the generated view, and change " role" to "access rights" --> edit revisions
I have rebuild rights permissions but that doesn't work
authenticated user who don't have the access to edit revisions can see the menu item too !
I try a lot of another rights but the user can see always the menu item ????

The only solution that I have found is to change the place of the menu item in navigation structure ...

This appears to have been closed because of inactivity (about a year) prior to exapndonline's patch in #4 from being posted. I think expandonline's patch is a good idea.

Could we get some review of the patch?

The patch in #4 looks fine. However I am not convinced "edit revisions" is, in general, a suitable default. "view revisions" or "authenticated user" is probably a better match for most situations, unless you want your content summary to be about content editable to the logged-in user, rather than viewable.

But as mentioned before, you can just go into the Views interface and pick any role or permission you like. It's about configuring the View to suit your use case.
The View that comes with Revisioning is just a configuration starting point, it is not meant to be a final answer to everyone's needs.

Things you may want to add are: filter by content type, filter by published/unpublished flag etc.

Question answered and no further activity. Closing.