From: Matthew G. <gr...@mu...> - 2004-02-09 00:50:42
|
I'm want to fix this bug, but need some clarification on permissions. What designer permission level should grant access to the admrespondent and admdesigner pages? pgroup, puser or must the designer have both? The manage.php page allows access to menu items to the "superuser" or a designer with "puser" or "pgroup" permissions. http://sourceforge.net/tracker/index.php?func=detail&aid=754420&group_id=8956&atid=108956 -- mcg ------------------------------------- The IT Lab (http://www.itlab.musc.edu) |
From: James E. F. <jf...@uv...> - 2004-02-09 03:20:00
|
Matthew Gregg wrote: > I'm want to fix this bug, but need some clarification on permissions. > What designer permission level should grant access to the admrespondent > and admdesigner pages? > pgroup, puser or must the designer have both? The manage.php page allows > access to menu items to the "superuser" or a designer with "puser" or > "pgroup" permissions. > > http://sourceforge.net/tracker/index.php?func=detail&aid=754420&group_id=8956&atid=108956 I think my intent was that superuser could add designers and respondents, and designers could add respondents. However, if there is another preference I'll defer to someone who actually uses phpESP regularly. :-) -James |
From: Matthew G. <gr...@mu...> - 2004-02-10 01:14:47
|
On Sun, 2004-02-08 at 22:19, James E. Flemer wrote: > Matthew Gregg wrote: > > I'm want to fix this bug, but need some clarification on permissions. > > What designer permission level should grant access to the admrespondent > > and admdesigner pages? > > pgroup, puser or must the designer have both? The manage.php page allows > > access to menu items to the "superuser" or a designer with "puser" or > > "pgroup" permissions. > > > > http://sourceforge.net/tracker/index.php?func=detail&aid=754420&group_id=8956&atid=108956 > > I think my intent was that superuser could add designers and > respondents, and designers could add respondents. However, if there is > another preference I'll defer to someone who actually uses phpESP > regularly. :-) How about this: Designers with "puser" see the "Manage Respondent Accounts" menu and have access to the related pages, since "puser" permission corresponds to the "Administer Group Respondents" setting in the account setup. Designers cannot see nor access the "Manage Designer Accounts" menu/pages. SuperUser does everything. > > -James > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel -- mcg ------------------------------------- The IT Lab (http://www.itlab.musc.edu) |
From: James E. F. <jf...@uv...> - 2004-02-10 22:41:12
|
Matthew Gregg wrote: > On Sun, 2004-02-08 at 22:19, James E. Flemer wrote: > >>Matthew Gregg wrote: >> >>>I'm want to fix this bug, but need some clarification on permissions. >>>What designer permission level should grant access to the admrespondent >>>and admdesigner pages? >>>pgroup, puser or must the designer have both? The manage.php page allows >>>access to menu items to the "superuser" or a designer with "puser" or >>>"pgroup" permissions. >>> >>>http://sourceforge.net/tracker/index.php?func=detail&aid=754420&group_id=8956&atid=108956 >> >>I think my intent was that superuser could add designers and >>respondents, and designers could add respondents. However, if there is >>another preference I'll defer to someone who actually uses phpESP >>regularly. :-) > > How about this: > Designers with "puser" see the "Manage Respondent Accounts" menu and > have access to the related pages, since "puser" permission corresponds > to the "Administer Group Respondents" setting in the account setup. > > Designers cannot see nor access the "Manage Designer Accounts" > menu/pages. > > SuperUser does everything. +1 |
From: Stefan C. <sch...@ea...> - 2004-02-11 13:59:55
Attachments:
db_def.sql
|
I've followed the discussion about the DEFAULT NULL values. Here's the SQL schema I use in my (highly) modified version of PHPesp. Might give some help here and there. stF |
From: Matthew G. <gr...@mu...> - 2004-02-13 22:15:59
|
Please give the patch located here[1] a try. It also contains a fix for bug #: 890830(the mysql_populate.sql problem on mySQL version 4.x), the patch should apply cleanly to current CVS. [1] http://bfs.itlab.musc.edu/~greggmc/stuff/permission_mysql4.patch On Tue, 2004-02-10 at 17:40, James E. Flemer wrote: > Matthew Gregg wrote: > > On Sun, 2004-02-08 at 22:19, James E. Flemer wrote: > > > >>Matthew Gregg wrote: > >> > >>>I'm want to fix this bug, but need some clarification on permissions. > >>>What designer permission level should grant access to the admrespondent > >>>and admdesigner pages? > >>>pgroup, puser or must the designer have both? The manage.php page allows > >>>access to menu items to the "superuser" or a designer with "puser" or > >>>"pgroup" permissions. > >>> > >>>http://sourceforge.net/tracker/index.php?func=detail&aid=754420&group_id=8956&atid=108956 > >> > >>I think my intent was that superuser could add designers and > >>respondents, and designers could add respondents. However, if there is > >>another preference I'll defer to someone who actually uses phpESP > >>regularly. :-) > > > > How about this: > > Designers with "puser" see the "Manage Respondent Accounts" menu and > > have access to the related pages, since "puser" permission corresponds > > to the "Administer Group Respondents" setting in the account setup. > > > > Designers cannot see nor access the "Manage Designer Accounts" > > menu/pages. > > > > SuperUser does everything. > > +1 > > > -- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel -- mcg -- The IT Lab (http://www.itlab.musc.edu) |
From: Matthew G. <gr...@mu...> - 2004-02-20 02:49:14
|
I'm ready to apply this to CVS. Any objections? On Fri, 2004-02-13 at 17:13, Matthew Gregg wrote: > Please give the patch located here[1] a try. It also contains a fix for > bug #: 890830(the mysql_populate.sql problem on mySQL version 4.x), the > patch should apply cleanly to current CVS. > > [1] http://bfs.itlab.musc.edu/~greggmc/stuff/permission_mysql4.patch > > > On Tue, 2004-02-10 at 17:40, James E. Flemer wrote: > > Matthew Gregg wrote: > > > On Sun, 2004-02-08 at 22:19, James E. Flemer wrote: > > > > > >>Matthew Gregg wrote: > > >> > > >>>I'm want to fix this bug, but need some clarification on permissions. > > >>>What designer permission level should grant access to the admrespondent > > >>>and admdesigner pages? > > >>>pgroup, puser or must the designer have both? The manage.php page allows > > >>>access to menu items to the "superuser" or a designer with "puser" or > > >>>"pgroup" permissions. > > >>> > > >>>http://sourceforge.net/tracker/index.php?func=detail&aid=754420&group_id=8956&atid=108956 > > >> > > >>I think my intent was that superuser could add designers and > > >>respondents, and designers could add respondents. However, if there is > > >>another preference I'll defer to someone who actually uses phpESP > > >>regularly. :-) > > > > > > How about this: > > > Designers with "puser" see the "Manage Respondent Accounts" menu and > > > have access to the related pages, since "puser" permission corresponds > > > to the "Administer Group Respondents" setting in the account setup. > > > > > > Designers cannot see nor access the "Manage Designer Accounts" > > > menu/pages. > > > > > > SuperUser does everything. > > > > +1 > > > > > > -- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > phpESP-devel mailing list > > php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpesp-devel -- mcg ------------------------------------- The IT Lab (http://www.itlab.musc.edu) |
From: James E. F. <jf...@uv...> - 2004-02-21 04:40:21
|
No objections. Note that changing the _('...') text will mean that the gettext tables will need regeneration. I normally just do that before releases, but perhaps it should be done sometime soon, since releases are not to frequent. I should probably also check in the script I use to generate & merge the tables ... or at least put them somewhere so other developers can use them. -James Matthew Gregg wrote: > I'm ready to apply this to CVS. Any objections? > > On Fri, 2004-02-13 at 17:13, Matthew Gregg wrote: > >>Please give the patch located here[1] a try. It also contains a fix for >>bug #: 890830(the mysql_populate.sql problem on mySQL version 4.x), the >>patch should apply cleanly to current CVS. >> >>[1] http://bfs.itlab.musc.edu/~greggmc/stuff/permission_mysql4.patch |
From: Aaron A. <lt...@fr...> - 2004-02-10 03:38:55
|
I have just confirmed that bug. Any user has rights to add a designer if they navigate directly to manage.php?where=admdesigner -----Original Message----- From: php...@li... [mailto:php...@li...] On Behalf Of James E. Flemer Sent: Sunday, February 08, 2004 9:20 PM To: phpESP-devel Subject: Re: [phpesp-dev] Bug 754420 Matthew Gregg wrote: > I'm want to fix this bug, but need some clarification on permissions. > What designer permission level should grant access to the > admrespondent and admdesigner pages? > pgroup, puser or must the designer have both? The manage.php page > allows access to menu items to the "superuser" or a designer with > "puser" or "pgroup" permissions. > > http://sourceforge.net/tracker/index.php?func=detail&aid=754420&group_ > id=8956&atid=108956 I think my intent was that superuser could add designers and respondents, and designers could add respondents. However, if there is another preference I'll defer to someone who actually uses phpESP regularly. :-) -James ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ phpESP-devel mailing list php...@li... https://lists.sourceforge.net/lists/listinfo/phpesp-devel |