I apologize in advance if this is not the appropriate place for my question, but I'm relatively new to this so I wasn't sure (if I should ask this question in another manner, please let me know).

From the release notes for the 6.x-1.0-beta1 version:

NOTE: This version removes the administrative settings page (at admin/settings/nodeadmin).

I just wondered why the administrative settings page was removed, and whether there will be a way to configure this module's settings in the future. Thank you!

Comments

arithmetric’s picture

arithmetric commented
Title: Question re: settings » Why was the administrative settings page removed?
Category: feature » support
Status: Active » Closed (works as designed)

An earlier version of this module had an administrative settings page for two choices: first, which content types to include on the Content Administration page, and second, whether to use the JavaScript-based dynamic interface by default or whether to fall back on a much less functional basic HTML version.

In beta 1, I removed both of these choices, because they no longer apply to how I the module works.

Instead of choosing which content types to show on the Content Administration page, I've added the ability to filter nodes by content type through the interface on the CA page itself.

Since the main purpose of this module is to add functionality that requires JavaScript, I don't see a reason to keep the option for disabling this functionality. However, the CA page still degrades gracefully to a very basic list of content if the user does not have JavaScript enabled.

If in a future version there are choices best made through an administrative settings page, then I will bring one back.

alison’s picture

alison
she/her
commented

Thank you for the reply, makes sense.

stevendeporre’s picture

stevendeporre commented

I think it makes sense to have some kind of administration possibility to limit functionality to users. Eg: I have some content types that I use for site-wide layout etc, which my users should not be able to change. Since user capabilities seem to be overruled by this module, a limit content types administration would be quite usefull

arithmetric’s picture

arithmetric commented

Hi stevendeporre,

Thanks for your comments.

I understand that it could be useful to limit which nodes are displayed through the Content Administration page, but I think it is simpler and more flexible to provide filters that can be changed on-the-fly rather than having a set of options on another page for what is visible through the Content Administration page.

However, I want to clarify that user permissions should not be ignored or circumvented by this module. A user should only be able to view, create, edit, or delete nodes through Content Administration that the user is authorized to view, create, edit, or delete.

In the 1.0-beta1 version, a user may see icons for viewing, editing, or deleting nodes without the proper access permissions, however the user cannot actually view, edit, or delete these nodes. This will be fixed in a future release.