Limiting user rights to edit pages

[intru]

I'm fairly new to CMSMS, and trying to build a website for a client. The client will have a userlogin for the backend, and only have very limited rights (edit some pages, not all, add news).
I figured out how to give a user/group the rights to only edit certain pages, and this works really well. So when the client logs in, he has only 2 things under content 'pages' and 'news'. (He has permissions to modify/delete news, and is an 'editional editor' of certain pages)

The problem is editing the pages, in the pages overview (listcontent.php) there is to much information visible (the client doesn't need to know what template the page has, or who the owner is). And when editing a certain page, the client is able to change the content type, and weather or not a page is cachable. This is way beyond the knowledge of my client, and therefore I only want him to be able to edit the content itself.

Is there any way to do this?

[calguy1000]

CMS 1.3 has improved this a bit.

The cachable flag can now be hidden from additional editors
and the template name is still displayed, but it's only a string, not a link
the content type and owner are still displayed.

[intru]

That's nice to hear, but won't solve my problem (now). I think I will delve into the sourcecode and modify it so that my client only sees the information that he will actually use. But this will probably bring me in troubles when updated to a newer version, right?

An other workaround that I though of is trying to hide the information using a modified admin theme and css. This makes updating to a newer version easier, but theoretically  the client could still change the data (but i will probably not happen).

Any ideas/suggestions what option will be best?

[Pierre M.]

Hello,

...I think I will delve into the sourcecode and modify it so that my client only sees the information that he will actually use. But this will probably bring me in troubles when updated to a newer version, right?

...unless you submit your patch in the forge... and it get accepted and merged.

Pierre M.

[intru]

...unless you submit your patch in the forge... and it get accepted and merged.

I've made all the changes that I needed, and it was quite easy. I manually made an extra permission, and checked for it in the places of relevance. But the problem with submitting this to the forge would be: it's made specifically for my situation. I've made changed to the file to edit a page, but not to add a page (since my client won't do that). So it wouldn't be a nice consistent patch : (

[applejack]

Hi Intu

So how did you make it so that a certain user can only edit certain pages as I didn't realise this could be done. Is this via the admin or using FEU?

Please ignore I worked it out.