 |
Register
Tuesday, January 06, 2009
|
|
|
 |
| You are not authorized to post a reply. |
|
| Author |
Messages |
|
rstordeur
Posts:4
 |
| 08/02/2006 11:08 AM |
|
Hi Bruce,
It seems that if the module is installed in a child portal (we do it during development prior to assigning the domain name), and when you assign an editor and they login to edit, they get logged out when the update button is clicked.
We attempted an 'add', a 'manage from list', 'edit', all to no avail. We get sent to the login screen.
This is a behavior we encountered with the portal-download module that is now part of DNN. When it is a child portal, it's broke, but when we 'promote' it, it works.
The problem is that we publish the portal as a child, then train our customers to maintain certain parts of the content (we almost never give them full admin rights). Only after they are trained do we make it a domain.
We temporarily can train them using the admin account, but when they see the admin function it introduces questions that are not pertinent to getting their site updated.
We are positive that the editing will work correctly when we 'promote' their site. Other sites on this installation of DNN (3.2.2) have WP and they work fine.
Thanks again for a great module,
Bob |
|
|
|
rstordeur
Posts:4
|
| 08/02/2006 11:24 AM |
|
OK, cancel everything i just wrote.
I guess we didn't understand the rights management correctly. Once we set the user from the 'manage from a list', all the editing worked fine.
However, it introduced one problem to our use of the module. Since only one person can be assigned editing rights, it violates the use of roles. We sometimes have more than one person in a company trying to edit content. If one person is assigned, no one else except an admin can edit it.
If they add an item (instead of the admin), it complicates things even further. I understand the idea controlling rights to individual items, but it doesn't seem that valuable. Multiple users (i.e. partners in a company) may want to be able to edit the same module.
True we could have an editing account that both could use, but again, that's against the idea of rights management through roles.
Any ideas for us?
Bob |
|
|
|
bcasson
Posts:88
|
| 08/06/2006 9:12 AM |
|
Bob, you got nothing better to do than come up with these challenges for me ;)
Let me give this one some thought. Sounds like owner groups might resolve this issue, your thoughts? |
|
|
|
bcasson
Posts:88
|
| 08/06/2006 10:18 AM |
|
On second thought the group idea is a bit messy, so rather than creating another layer, Roles would be a better way to go.
Here is how I think it could work: in 'Edit Security' section of Settings, you would have the option to indicate that either the 'Owner' can edit their own items, or the 'Role' can edit their own items. If you select 'Role' then anyone in the same role as the person who created the item would be able to edit the item. If you select 'Owner' then only the owner could edit the item.
This would be an 'either or' setting. |
|
|
|
rstordeur
Posts:4
|
| 08/07/2006 11:27 AM |
|
Excellent! That way no matter how many 'editors' are assigned to a role, they could add, change or delete!
I knew if I spent long hours of thinking of ways to challenge you, you would be up to the task!
BTW, our latest use of your module can be viewed on the development site, www.oneconnection.com/pnickel. The Rooms section on the 'Our Restaurant' page uses one module with the standard settings. All the menu pages use several modules with custom tempates that format the food menus and allow two alternate menu items for each food entry. Our client will be able to edit any and all menu items without having to contact us!
Thanks again for a great module! |
|
|
|
|
| You are not authorized to post a reply. |
|
|
|
ActiveForums 3.6
|
 |
|
|
|
|
|
|
|
|