user restriction to settings page

[Manfred62]

just testing some configs in roles, users etc.

How can I restrict a non-admin-user to not see the settings inside a page (page - edit - settings)?

If I restrict the user, will he be able to publish/unpublish a side (e.g. with this module) anyway?

thanks

[pwired]

Actually this is an important part of a cms. A good front end should also be a user or client restricted back end. A user or client should login to a restricted back end where only limited pages and fields can be edited. Many times clients ask for such a setup where they only see a simplyfied part of the backend with only a few pages for them to edit. I just started with PW and am also trying to figure this out.

[Pete]

There are a few issues here that I think have been discussed before - the settings tab for a page also contains the page name field /your-page-name/ so you can't really do without it (what if a client changes a page title completely after creation for example? The page name won't update itself - and rightly so as it is the URL so you don't want to assume that the URL should change itself if that URL has been indexed by search engines). It also contains the visibility settings for the page, so if they accidentally publish a page instead of leaving it hidden after save then they would have no way to un-publish it again without that tab.

There are also things like template selection in that tab that can be useful to editors/clients... in fact, everything on that tab could be useful for an end user

I don't think it should be able to be hidden, but rather the end user should be informed what the features there actually do.

[Manfred62]

Hi Pete,

thanks for the infos.

[Soma]

It is possible to create a little module that hides it per permission or role.