Hi. I have two queries...
(1) I want to allow the Editor role of the CMSMS based website I am producing for my employer to be able to add/modify/delete Frontend Users as well as create pages and news items. However, the only Frontend User specific permissions option that appears in the Group Permissions page is Modify FrontEndUser Properties, which doesn't do very much.
If I allow them the options to Add/Modify/Delete Users, they can then do this for Frontend Users, but can also do it for the backend users too, which is not really advisable!
Is there any way around this? As a busy site developer/designer with overall admin control of this and other sites, I don't want to have be responsible for the menial task of adding new users myself.... that's for administrative types to do!
(2) The Add and Edit Users part of the Frontend Users is split over two pages, with the username and password on one page and the specified fields on the other, connected by a Next button at the bottom. How annoying. It took me quite a while to figure out why I couldn't see the email address and other few specified fields of the user, and I'm the site developer! So it could prove problematic to the administrative people who are going to be adding these new users.
Is there any specific reason why this is so and why all the info for a person couldn't be accessible from one page? And will I end up breaking my site if I try and move the code over for this into one section with one submit button on one page?
Many thanks,
Mark B.
[SOLVED] Frontend Users: restrict user admin by Editor + Edit user annoyance
[SOLVED] Frontend Users: restrict user admin by Editor + Edit user annoyance
Last edited by neuroboy on Thu Jan 21, 2010 3:46 pm, edited 1 time in total.
Re: Frontend Users: restrict user admin by Editor + Edit user annoyance
In the FEU admin panel, there is an option to allow FEU-specific permissions. Did you enable this option? It sounds like you did not.neuroboy wrote: Hi. I have two queries...
(1) I want to allow the Editor role of the CMSMS based website I am producing for my employer to be able to add/modify/delete Frontend Users as well as create pages and news items. However, the only Frontend User specific permissions option that appears in the Group Permissions page is Modify FrontEndUser Properties, which doesn't do very much.
If I allow them the options to Add/Modify/Delete Users, they can then do this for Frontend Users, but can also do it for the backend users too, which is not really advisable!
Is there any way around this? As a busy site developer/designer with overall admin control of this and other sites, I don't want to have be responsible for the menial task of adding new users myself.... that's for administrative types to do!
Quite probably, unless you're a quite proficient coder. You will also render your site unsupportable by the dev team or the FEU developer, as will happen with any modification to the CMSMS (or module) source code.neuroboy wrote: (2) The Add and Edit Users part of the Frontend Users is split over two pages, with the username and password on one page and the specified fields on the other, connected by a Next button at the bottom. How annoying. It took me quite a while to figure out why I couldn't see the email address and other few specified fields of the user, and I'm the site developer! So it could prove problematic to the administrative people who are going to be adding these new users.
Is there any specific reason why this is so and why all the info for a person couldn't be accessible from one page? And will I end up breaking my site if I try and move the code over for this into one section with one submit button on one page?
Re: Frontend Users: restrict user admin by Editor + Edit user annoyance
(1) I knew it was something simple that I'd overlooked.
(2) You might be right... I've hacked about the code of another CMS before (Wordpress to be precise) but this looks a bit a
more complicated. I'll leave be, though I might make the 'Next' button a bit more prominent... perhaps a big red flashing one.
Many thanks for your help and advice, jmcgin51.
Regards,
Mark.
(2) You might be right... I've hacked about the code of another CMS before (Wordpress to be precise) but this looks a bit a
more complicated. I'll leave be, though I might make the 'Next' button a bit more prominent... perhaps a big red flashing one.
Many thanks for your help and advice, jmcgin51.
Regards,
Mark.