Hello, we are interested in seeing how possible it would be to have development done that could make CMSMS have a much simpler and cleaner user management system. Something that will essentially allow individual pages to be viewable only by certain users/groups (and this means visible to them in their own specific splash page after log-in) is what we are looking for.
Along with this we are also looking for a very robust version control system for content pages that would allow editors to have to accept any changes to pages following the submission of pages to an editing queue. This would include, for the editor, a list of pages they need to edit for approval before their submission on their main login page.
If this isn't clear enough, and I imagine it will require more clarification, please let me know and we can sort out the details.
We are also already aware that some of this functionality is available in Frontend User Management, for example.
Thanks a lot!
Company Looking For Greater User/Group Management and Version Control.
Company Looking For Greater User/Group Management and Version Control.
Last edited by nsc on Tue Jul 14, 2009 12:04 am, edited 1 time in total.
Re: Company Looking For Greater User/Group Management and Version Control.
This is already available via FrontEndUsers/CustomContent (and SelfRegistration if needed).nsc wrote: Hello, we are interested in seeing how possible it would be to have development done that could make CMSMS have a much simpler and cleaner user management system. Something that will essentially allow individual pages to be viewable only by certain users/groups (and this means visible to them in their own specific splash page after log-in) is what we are looking for.
Full integrated version control is not yet implemented. I'm sure if you wanted to contribute to the development of this feature, it would speed the process along.
Re: Company Looking For Greater User/Group Management and Version Control.
We would love to pay for the further development of CMSMS in terms of version control, but as I noted we are aware that the basic functionality is available to us through Frontend User Management.
Our difficulty is that, and this is as far as I can tell, there is no point and click way of managing users and groups in a simplistic manner. This would mean immediately being able to set some pages or all of them to being available to certain groups of users or group. Indeed one can use {if $$ccuser->loggedin()} and other similar functionality but much of that requires us to continually put certain Frontend User Management code into each page. For the people writing up our content, we need them to be able to input the content and then be able to click which groups and or users that content would be visible to once they have logged in. An example case is, if we wanted to add a new group and have 10 or so pages of content that we already have assigned to another group show up when members of the new group log in. We would need to add new memberof('newgroup') lines to the content. This is problematic for future managers of the site who aren't comfortable with this, however negligible, level of technical work.
Hopefully this makes sense. Again, if we think we will be able to achieve the technical support reference db for individual customers that we are looking to build we are more than willing to pay for the development of this functionality.
Our difficulty is that, and this is as far as I can tell, there is no point and click way of managing users and groups in a simplistic manner. This would mean immediately being able to set some pages or all of them to being available to certain groups of users or group. Indeed one can use {if $$ccuser->loggedin()} and other similar functionality but much of that requires us to continually put certain Frontend User Management code into each page. For the people writing up our content, we need them to be able to input the content and then be able to click which groups and or users that content would be visible to once they have logged in. An example case is, if we wanted to add a new group and have 10 or so pages of content that we already have assigned to another group show up when members of the new group log in. We would need to add new memberof('newgroup') lines to the content. This is problematic for future managers of the site who aren't comfortable with this, however negligible, level of technical work.
Hopefully this makes sense. Again, if we think we will be able to achieve the technical support reference db for individual customers that we are looking to build we are more than willing to pay for the development of this functionality.
Re: Company Looking For Greater User/Group Management and Version Control.
I do understand what you are looking for, and there are others who have requested similar features.
In the meantime, I still think that easy user management can be handled through some creative use of templates, Smarty variables, extra page attributes, the menu manager, etc. And once this is set up, your content managers don't need to worry about it.
For example, in your original post you mentioned that you wanted the ability to have users automatically redirected to an appropriate page on login, based on username or usergroup. This functionality already exists in FEU. You can also display a menu on that page that only contains the pages that user/group should be able to view. This page can also display uploaded files that should be visible only to x group.
I'm not saying that your admins will be able to be completely free from any technical knowledge, but the requirements should be pretty minimal if the site developer does his homework.
In the meantime, I still think that easy user management can be handled through some creative use of templates, Smarty variables, extra page attributes, the menu manager, etc. And once this is set up, your content managers don't need to worry about it.
For example, in your original post you mentioned that you wanted the ability to have users automatically redirected to an appropriate page on login, based on username or usergroup. This functionality already exists in FEU. You can also display a menu on that page that only contains the pages that user/group should be able to view. This page can also display uploaded files that should be visible only to x group.
I'm not saying that your admins will be able to be completely free from any technical knowledge, but the requirements should be pretty minimal if the site developer does his homework.
