Kev,

Got a Feature Request that I feel is pretty important.

The ViewOptions DNN IActionable menu should be based off of the module settings for who can actually edit the options (or Admin/Host if not defined yet).

For example if only HOSTS can edit the Options, then the IActionable should not be present for Admins...

Why is this important?

The DNN module permission is then usable just like a standard DNN module.

This also allows ListX developers the use of the DNN System value of .IsEditable in the module logic.

Admins can set edit rights to the module as normal.

The ListX module now takes natural advantage of DNN's Security.

No "View Options" would be available to " module editors" (ie. people that have module edit rights but not ListX edit rights)

This is a common permissions technique used for DNN sites.

Actually, this (or was) already the case with ListX. The current release version has it removed for one specific reason. ListX handles its binding in the PreRender - which means it doesn't yet know if it is editable until that point. The problem here - the versions of DNN preceding 3.2 and even the initial version of this have a bit of an odd behaviour in that it binds said menu at Initialize time. So, even when ListX completely drops the container menu - it still appears! I've been working on a few changes to this, but it may mean that this functionality will only work for 3.25 and later.