PEAK XOOPS - Smaller admin for contributers 
Smaller admin for contributers
- You cannot open a new topic into this forum
- Guests cannot post into this forum
Previous post
-
Next post
|
Parent
-
Children.1
|
Posted on 2005/1/11 1:34
macno
From: France
Posts: 12
From: France
Posts: 12
Hello,i have a lot of tynid modules and for each there is one contributer.
Is it possible to reduce the admin of each tynid : Only edit /add a text with spaw would be need for them, but the administrator could continue to have the entire admin.
Perhaps a solution would be to add an edit link on each article for the members who have special rights ?
I fear there would be a lot of errors if contributors have the entire rights.
Thanks to your help
Is it possible to reduce the admin of each tynid : Only edit /add a text with spaw would be need for them, but the administrator could continue to have the entire admin.
Perhaps a solution would be to add an edit link on each article for the members who have special rights ?
I fear there would be a lot of errors if contributors have the entire rights.
Thanks to your help
Votes:0
Average:0.00
GIJOE
Posts: 4110
Posts: 4110
hi macno
If you want edit icon, edit the template tinycontent*_index.html of the latest TinyD.
FROM:
TO:
If you want edit icon, edit the template tinycontent*_index.html of the latest TinyD.
FROM:
<{* A sample displaying Edit link only for system admin *}>
<{* <{if $xoops_isadmin == 1 }><a href="<{$mod_url}>/admin/index.php?op=edit&id=<{$id}>">[Edit]</a><{/if}> *}>
<{* If you turn this on, disable this module's cache *}>
TO:
<{* A sample displaying Edit link only for system admin *}>
<{if $xoops_isadmin == 1 }><a href="<{$mod_url}>/admin/index.php?op=edit&id=<{$id}>">[Edit]</a><{/if}>
<{* If you turn this on, disable this module's cache *}>
Votes:0
Average:0.00
macno
From: France
Posts: 12
From: France
Posts: 12
Merci 
Votes:0
Average:0.00
macelee
Posts: 3
Posts: 3
Just installed this module and converted a few old static pages. Excellent work!
I have the same need as macno and want to give a few userid the permission to edit the contents in the tinyD module but do not want to give them full Administrator right. I want to simply hack the module and hardcode those usenames at places where the permission is checked so that they are able to edit the content. Would you please tell me in which file the permission is checked?
Although xoops has 'Group', if I use 10 instances of tinyd I would have to create 10 customised groups so that the contributors can help me maintain the content. I think this is not a graceful solution. As a long-term solution, may I ask you to consider the following idea: each tinyd instance maintains a list of usernames who are given the permission to edit the content. The site administrator can add names to the list or delete names from the list.
I have the same need as macno and want to give a few userid the permission to edit the contents in the tinyD module but do not want to give them full Administrator right. I want to simply hack the module and hardcode those usenames at places where the permission is checked so that they are able to edit the content. Would you please tell me in which file the permission is checked?
Although xoops has 'Group', if I use 10 instances of tinyd I would have to create 10 customised groups so that the contributors can help me maintain the content. I think this is not a graceful solution. As a long-term solution, may I ask you to consider the following idea: each tinyd instance maintains a list of usernames who are given the permission to edit the content. The site administrator can add names to the list or delete names from the list.
Votes:0
Average:0.00
Previous post
-
Next post
|
Parent
-
No child
|
Posted on 2005/5/6 14:23
GIJOE
Posts: 4110
Posts: 4110
hi macelee.
Quote:The permission is checked in XOOPS core.
Quote:What you said sounds quite reasonable for me .
OK.
I'll add a controller for writers but admin.
And the rights should be based on uname.
Quote:
I have the same need as macno and want to give a few userid the permission to edit the contents in the tinyD module but do not want to give them full Administrator right. I want to simply hack the module and hardcode those usenames at places where the permission is checked so that they are able to edit the content. Would you please tell me in which file the permission is checked?
Quote:
Although xoops has 'Group', if I use 10 instances of tinyd I would have to create 10 customised groups so that the contributors can help me maintain the content. I think this is not a graceful solution. As a long-term solution, may I ask you to consider the following idea: each tinyd instance maintains a list of usernames who are given the permission to edit the content. The site administrator can add names to the list or delete names from the list.
OK.
I'll add a controller for writers but admin.
And the rights should be based on uname.
Votes:0
Average:0.00
Login