Menu
▾
▴
phpwebsite-developers
|
From: Richard S. <ri...@ri...> - 2003-06-02 08:47:57
|
Does the allow access take into consideration the group permissions? Say for instance I create a group that can edit and delete stuff from my module. Then I create a user in that group I just created with none of the module permissions checked, would that user have the permissions of editing and deleting stuff since the group has it or not? I would try it myself but I my module isn't that far developed yet ;-) Thanks, Richard S. |
|
From: Richard S. <ri...@ri...> - 2003-06-02 09:31:44
|
Eh, never-mind, I found it in the devdoc :-X On Monday, June 2, 2003, at 01:47 AM, Richard Sumilang wrote: > Does the allow access take into consideration the group permissions? > Say for instance I create a group that can edit and delete stuff from > my module. Then I create a user in that group I just created with none > of the module permissions checked, would that user have the > permissions of editing and deleting stuff since the group has it or > not? I would try it myself but I my module isn't that far developed > yet ;-) > > Thanks, > Richard S. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: Matthew M. <ma...@tu...> - 2003-06-02 12:01:51
|
> Does the allow access take into consideration the group permissions? Yes, a user inherits all the group permissions of which they are a member. Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Eloi G. <el...@re...> - 2003-06-02 17:22:04
|
> > Does the allow access take into consideration the group permissions? > > Yes, a user inherits all the group permissions of which they are a member. However they do have to be an admin. |
|
From: <ad...@tu...> - 2003-06-03 12:40:37
|
Any user you want to give even the slightest admin privlages to any module needs to be an admin. All other users are simply users. I wonder if the "admin" flag could be eliminated all together and if the user has any permissions assigned to them, it would simply allow the access to the modules. Matt: Is there another reason the admin flag exists that I'm just missing? Adam >> > Does the allow access take into consideration the group permissions? >> >> Yes, a user inherits all the group permissions of which they are a >> member. > > However they do have to be an admin. > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Matthew M. <ma...@tu...> - 2003-06-03 12:48:10
|
> Matt: Is there another reason the admin flag exists that I'm just missing? Funny you should mention this Adam. Back around a year and a half ago you personally asked for this feature. =) The thinking was that it would allow an admin to instantly turn an admin into a user (in case they did something bad) or just so permissions could be set without actual admin priviledges. I have no problem removing it, but I think these are important concerns. What do you think? Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: <ad...@tu...> - 2003-06-03 14:01:07
|
Matt matt...you know I ask for features all the time. It doesn't mean you should listen to me :) Just kidding...I remember the request now and our conversation about it and you're right it is a needed feature. I'm wondering if we should change the wording or something to make it more intuitive as to it's function. Tell me what you think. Adam >> Matt: Is there another reason the admin flag exists that I'm just >> missing? > > Funny you should mention this Adam. Back around a year and a half ago you > personally asked for this feature. =) > > The thinking was that it would allow an admin to instantly turn an admin > into a user (in case they did something bad) or just so permissions could > be set without actual admin priviledges. > > I have no problem removing it, but I think these are important concerns. > > What do you think? > > Matthew McNaney > Internet Systems Architect > Electronic Student Services > Appalachian State University > Phone: 828-262-6493 > phpwebsite.appstate.edu > ess.appstate.edu > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Richard S. <ri...@ri...> - 2003-06-03 15:34:25
|
I really don't like the fact that the person has to be an admin in order to use the allow_access() function on them. On my module I'm working on, I have users that are just users and don't administer anything but yet I need to give them certain permissions on what they can and cant do. In order for me to check their permissions I have to make them administrators??? Doesn't make logically sense for me??? Best Regards, Richard S. On Tuesday, June 3, 2003, at 07:01 AM, ad...@tu... wrote: > Matt matt...you know I ask for features all the time. It doesn't mean > you > should listen to me :) Just kidding...I remember the request now and > our > conversation about it and you're right it is a needed feature. I'm > wondering if we should change the wording or something to make it more > intuitive as to it's function. Tell me what you think. > > Adam > >>> Matt: Is there another reason the admin flag exists that I'm just >>> missing? >> >> Funny you should mention this Adam. Back around a year and a half ago >> you >> personally asked for this feature. =) >> >> The thinking was that it would allow an admin to instantly turn an >> admin >> into a user (in case they did something bad) or just so permissions >> could >> be set without actual admin priviledges. >> >> I have no problem removing it, but I think these are important >> concerns. >> >> What do you think? >> >> Matthew McNaney >> Internet Systems Architect >> Electronic Student Services >> Appalachian State University >> Phone: 828-262-6493 >> phpwebsite.appstate.edu >> ess.appstate.edu >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: eBay >> Get office equipment for less on eBay! >> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> > > > -- > Adam Morton > Developer - Electronic Student Services > http://phpwebsite.appstate.edu > Founder - Appalachian Linux Users Group > http://alug.appstate.edu > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: <ad...@tu...> - 2003-06-03 15:39:46
|
I had a conversation with Brian and we came up with chaning the wording on the checkbox and maybe the position of it in the form to "change" the functionality of it. We could change it to "Activate Permissions" and if a user has been "bad" the deity of the site can uncheck it which would basicallly disable all permissions on that user. This should allow for Sumilang to get the functionality he needs and maybe clear up some confusion as to the functionality of that flag. Thoughts? Adam > I really don't like the fact that the person has to be an admin in > order to use the allow_access() function on them. On my module I'm > working on, I have users that are just users and don't administer > anything but yet I need to give them certain permissions on what they > can and cant do. In order for me to check their permissions I have to > make them administrators??? Doesn't make logically sense for me??? > > Best Regards, > Richard S. > > > > On Tuesday, June 3, 2003, at 07:01 AM, ad...@tu... wrote: > >> Matt matt...you know I ask for features all the time. It doesn't mean >> you >> should listen to me :) Just kidding...I remember the request now and >> our >> conversation about it and you're right it is a needed feature. I'm >> wondering if we should change the wording or something to make it more >> intuitive as to it's function. Tell me what you think. >> >> Adam >> >>>> Matt: Is there another reason the admin flag exists that I'm just >>>> missing? >>> >>> Funny you should mention this Adam. Back around a year and a half ago >>> you >>> personally asked for this feature. =) >>> >>> The thinking was that it would allow an admin to instantly turn an >>> admin >>> into a user (in case they did something bad) or just so permissions >>> could >>> be set without actual admin priviledges. >>> >>> I have no problem removing it, but I think these are important >>> concerns. >>> >>> What do you think? >>> >>> Matthew McNaney >>> Internet Systems Architect >>> Electronic Student Services >>> Appalachian State University >>> Phone: 828-262-6493 >>> phpwebsite.appstate.edu >>> ess.appstate.edu >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: eBay >>> Get office equipment for less on eBay! >>> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >>> _______________________________________________ >>> Phpwebsite-developers mailing list >>> Php...@li... >>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >>> >> >> >> -- >> Adam Morton >> Developer - Electronic Student Services >> http://phpwebsite.appstate.edu >> Founder - Appalachian Linux Users Group >> http://alug.appstate.edu >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: eBay >> Get office equipment for less on eBay! >> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Richard S. <ri...@ri...> - 2003-06-03 17:19:12
|
Almost their but it still seems a bit redundant. Instead of making it a 'Activate Permissions' switch, how about a 'Activate / Disable Account' switch? Typically when I don't want to have a user access the system anymore I don't delete the account or remove all their permissions but rather deactivate it. Permissions should always be available which is why I find a 'Activate Permissions' switch a bit redundant. I think that will be more overall useful in general and and cause less confusion. I was personally stuck for a long time writing my module when I couldn't figure out why my permissions where not working with the allow_access() function. I think the Administer switch causes confusion from a developer and user point of view. Best Regards, Richard Sumilang On Tuesday, June 3, 2003, at 08:39 AM, ad...@tu... wrote: > I had a conversation with Brian and we came up with chaning the > wording on > the checkbox and maybe the position of it in the form to "change" the > functionality of it. We could change it to "Activate Permissions" and > if > a user has been "bad" the deity of the site can uncheck it which would > basicallly disable all permissions on that user. This should allow for > Sumilang to get the functionality he needs and maybe clear up some > confusion as to the functionality of that flag. Thoughts? > > Adam > >> I really don't like the fact that the person has to be an admin in >> order to use the allow_access() function on them. On my module I'm >> working on, I have users that are just users and don't administer >> anything but yet I need to give them certain permissions on what they >> can and cant do. In order for me to check their permissions I have to >> make them administrators??? Doesn't make logically sense for me??? >> >> Best Regards, >> Richard S. >> >> >> >> On Tuesday, June 3, 2003, at 07:01 AM, ad...@tu... wrote: >> >>> Matt matt...you know I ask for features all the time. It doesn't >>> mean >>> you >>> should listen to me :) Just kidding...I remember the request now and >>> our >>> conversation about it and you're right it is a needed feature. I'm >>> wondering if we should change the wording or something to make it >>> more >>> intuitive as to it's function. Tell me what you think. >>> >>> Adam >>> >>>>> Matt: Is there another reason the admin flag exists that I'm just >>>>> missing? >>>> >>>> Funny you should mention this Adam. Back around a year and a half >>>> ago >>>> you >>>> personally asked for this feature. =) >>>> >>>> The thinking was that it would allow an admin to instantly turn an >>>> admin >>>> into a user (in case they did something bad) or just so permissions >>>> could >>>> be set without actual admin priviledges. >>>> >>>> I have no problem removing it, but I think these are important >>>> concerns. >>>> >>>> What do you think? >>>> >>>> Matthew McNaney >>>> Internet Systems Architect >>>> Electronic Student Services >>>> Appalachian State University >>>> Phone: 828-262-6493 >>>> phpwebsite.appstate.edu >>>> ess.appstate.edu >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: eBay >>>> Get office equipment for less on eBay! >>>> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >>>> _______________________________________________ >>>> Phpwebsite-developers mailing list >>>> Php...@li... >>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >>>> >>> >>> >>> -- >>> Adam Morton >>> Developer - Electronic Student Services >>> http://phpwebsite.appstate.edu >>> Founder - Appalachian Linux Users Group >>> http://alug.appstate.edu >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: eBay >>> Get office equipment for less on eBay! >>> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >>> _______________________________________________ >>> Phpwebsite-developers mailing list >>> Php...@li... >>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >>> >>> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: eBay >> Get office equipment for less on eBay! >> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> > > > -- > Adam Morton > Developer - Electronic Student Services > http://phpwebsite.appstate.edu > Founder - Appalachian Linux Users Group > http://alug.appstate.edu > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: Eloi G. <el...@re...> - 2003-06-03 17:48:13
|
+1 Sorry, I got this message as soon as I sent mine off. I agree wholeheartedly with Richard. ----- Original Message ----- From: "Richard Sumilang" <ri...@ri...> To: <ad...@tu...> Cc: <php...@li...> Sent: Tuesday, June 03, 2003 1:19 PM Subject: Re: [Phpwebsite-developers] allow_access() question > Almost their but it still seems a bit redundant. Instead of making it a > 'Activate Permissions' switch, how about a 'Activate / Disable Account' > switch? Typically when I don't want to have a user access the system > anymore I don't delete the account or remove all their permissions but > rather deactivate it. Permissions should always be available which is > why I find a 'Activate Permissions' switch a bit redundant. I think > that will be more overall useful in general and and cause less > confusion. > > I was personally stuck for a long time writing my module when I > couldn't figure out why my permissions where not working with the > allow_access() function. I think the Administer switch causes confusion > from a developer and user point of view. > > Best Regards, > Richard Sumilang |
|
From: <ad...@tu...> - 2003-06-03 18:02:26
|
I also agree that disabling the account may be a better method for handling this situation. I'd like to add that if the account is disabled that when the user tries to log in, a message is printed to that effect notifying them their account has been disabled and to contact the site administrator. +1 to Sumilang's method. Adam > +1 > > Sorry, I got this message as soon as I sent mine off. > I agree wholeheartedly with Richard. > > > ----- Original Message ----- > From: "Richard Sumilang" <ri...@ri...> > To: <ad...@tu...> > Cc: <php...@li...> > Sent: Tuesday, June 03, 2003 1:19 PM > Subject: Re: [Phpwebsite-developers] allow_access() question > > >> Almost their but it still seems a bit redundant. Instead of making it a >> 'Activate Permissions' switch, how about a 'Activate / Disable Account' >> switch? Typically when I don't want to have a user access the system >> anymore I don't delete the account or remove all their permissions but >> rather deactivate it. Permissions should always be available which is >> why I find a 'Activate Permissions' switch a bit redundant. I think >> that will be more overall useful in general and and cause less >> confusion. >> >> I was personally stuck for a long time writing my module when I >> couldn't figure out why my permissions where not working with the >> allow_access() function. I think the Administer switch causes confusion >> from a developer and user point of view. >> >> Best Regards, >> Richard Sumilang > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Steven L. <st...@tu...> - 2003-06-03 19:42:35
|
+1 from me too, I like the idea Steven > I also agree that disabling the account may be a better method for > handling this situation. I'd like to add that if the account is disabled > that when the user tries to log in, a message is printed to that effect > notifying them their account has been disabled and to contact the site > administrator. > > +1 to Sumilang's method. > > Adam > > >> +1 >> >> Sorry, I got this message as soon as I sent mine off. >> I agree wholeheartedly with Richard. >> >> >> ----- Original Message ----- >> From: "Richard Sumilang" <ri...@ri...> >> To: <ad...@tu...> >> Cc: <php...@li...> >> Sent: Tuesday, June 03, 2003 1:19 PM >> Subject: Re: [Phpwebsite-developers] allow_access() question >> >> >>> Almost their but it still seems a bit redundant. Instead of making it a >>> 'Activate Permissions' switch, how about a 'Activate / Disable Account' >>> switch? Typically when I don't want to have a user access the system >>> anymore I don't delete the account or remove all their permissions but >>> rather deactivate it. Permissions should always be available which is >>> why I find a 'Activate Permissions' switch a bit redundant. I think >>> that will be more overall useful in general and and cause less >>> confusion. >>> >>> I was personally stuck for a long time writing my module when I >>> couldn't figure out why my permissions where not working with the >>> allow_access() function. I think the Administer switch causes confusion >>> from a developer and user point of view. >>> >>> Best Regards, >>> Richard Sumilang >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: eBay >> Get office equipment for less on eBay! >> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> > > > -- > Adam Morton > Developer - Electronic Student Services > http://phpwebsite.appstate.edu > Founder - Appalachian Linux Users Group > http://alug.appstate.edu > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Steven Levin Electronic Student Services Appalachian State University Phone: 828.262.2431 PhpWebsite Development Team URL: http://phpwebsite.appstate.edu Email: st...@NO... |
|
From: Richard S. <ri...@ri...> - 2003-06-03 20:02:46
|
Can I add a point to my idea? If so, +1 to myself :-) On Tuesday, June 3, 2003, at 12:42 PM, Steven Levin wrote: > +1 from me too, I like the idea > > Steven > >> I also agree that disabling the account may be a better method for >> handling this situation. I'd like to add that if the account is >> disabled >> that when the user tries to log in, a message is printed to that >> effect >> notifying them their account has been disabled and to contact the site >> administrator. >> >> +1 to Sumilang's method. >> >> Adam >> >> >>> +1 >>> >>> Sorry, I got this message as soon as I sent mine off. >>> I agree wholeheartedly with Richard. >>> >>> >>> ----- Original Message ----- >>> From: "Richard Sumilang" <ri...@ri...> >>> To: <ad...@tu...> >>> Cc: <php...@li...> >>> Sent: Tuesday, June 03, 2003 1:19 PM >>> Subject: Re: [Phpwebsite-developers] allow_access() question >>> >>> >>>> Almost their but it still seems a bit redundant. Instead of making >>>> it a >>>> 'Activate Permissions' switch, how about a 'Activate / Disable >>>> Account' >>>> switch? Typically when I don't want to have a user access the system >>>> anymore I don't delete the account or remove all their permissions >>>> but >>>> rather deactivate it. Permissions should always be available which >>>> is >>>> why I find a 'Activate Permissions' switch a bit redundant. I think >>>> that will be more overall useful in general and and cause less >>>> confusion. >>>> >>>> I was personally stuck for a long time writing my module when I >>>> couldn't figure out why my permissions where not working with the >>>> allow_access() function. I think the Administer switch causes >>>> confusion >>>> from a developer and user point of view. >>>> >>>> Best Regards, >>>> Richard Sumilang >>> >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: eBay >>> Get office equipment for less on eBay! >>> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >>> _______________________________________________ >>> Phpwebsite-developers mailing list >>> Php...@li... >>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >>> >> >> >> -- >> Adam Morton >> Developer - Electronic Student Services >> http://phpwebsite.appstate.edu >> Founder - Appalachian Linux Users Group >> http://alug.appstate.edu >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: eBay >> Get office equipment for less on eBay! >> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> > > > -- > Steven Levin > Electronic Student Services > Appalachian State University > Phone: 828.262.2431 > PhpWebsite Development Team > URL: http://phpwebsite.appstate.edu > Email: st...@NO... > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: Richard S. <ri...@ri...> - 2003-06-03 20:30:05
|
So to cut right to the chase, when can we see it implemented ;-) I'm will to help if needed. Best Regards, Richard Sumilang On Tuesday, June 3, 2003, at 01:02 PM, Richard Sumilang wrote: > Can I add a point to my idea? > > If so, +1 to myself :-) > > > > > On Tuesday, June 3, 2003, at 12:42 PM, Steven Levin wrote: > >> +1 from me too, I like the idea >> >> Steven >> >>> I also agree that disabling the account may be a better method for >>> handling this situation. I'd like to add that if the account is >>> disabled >>> that when the user tries to log in, a message is printed to that >>> effect >>> notifying them their account has been disabled and to contact the >>> site >>> administrator. >>> >>> +1 to Sumilang's method. >>> >>> Adam >>> >>> >>>> +1 >>>> >>>> Sorry, I got this message as soon as I sent mine off. >>>> I agree wholeheartedly with Richard. >>>> >>>> >>>> ----- Original Message ----- >>>> From: "Richard Sumilang" <ri...@ri...> >>>> To: <ad...@tu...> >>>> Cc: <php...@li...> >>>> Sent: Tuesday, June 03, 2003 1:19 PM >>>> Subject: Re: [Phpwebsite-developers] allow_access() question >>>> >>>> >>>>> Almost their but it still seems a bit redundant. Instead of making >>>>> it a >>>>> 'Activate Permissions' switch, how about a 'Activate / Disable >>>>> Account' >>>>> switch? Typically when I don't want to have a user access the >>>>> system >>>>> anymore I don't delete the account or remove all their permissions >>>>> but >>>>> rather deactivate it. Permissions should always be available which >>>>> is >>>>> why I find a 'Activate Permissions' switch a bit redundant. I think >>>>> that will be more overall useful in general and and cause less >>>>> confusion. >>>>> >>>>> I was personally stuck for a long time writing my module when I >>>>> couldn't figure out why my permissions where not working with the >>>>> allow_access() function. I think the Administer switch causes >>>>> confusion >>>>> from a developer and user point of view. >>>>> >>>>> Best Regards, >>>>> Richard Sumilang >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.net email is sponsored by: eBay >>>> Get office equipment for less on eBay! >>>> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >>>> _______________________________________________ >>>> Phpwebsite-developers mailing list >>>> Php...@li... >>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >>>> >>> >>> >>> -- >>> Adam Morton >>> Developer - Electronic Student Services >>> http://phpwebsite.appstate.edu >>> Founder - Appalachian Linux Users Group >>> http://alug.appstate.edu >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: eBay >>> Get office equipment for less on eBay! >>> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >>> _______________________________________________ >>> Phpwebsite-developers mailing list >>> Php...@li... >>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >>> >> >> >> -- >> Steven Levin >> Electronic Student Services >> Appalachian State University >> Phone: 828.262.2431 >> PhpWebsite Development Team >> URL: http://phpwebsite.appstate.edu >> Email: st...@NO... >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: eBay >> Get office equipment for less on eBay! >> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: Matthew M. <ma...@tu...> - 2003-06-03 20:56:04
|
> So to cut right to the chase, when can we see it implemented ;-) Let me see how much work it is tomorrow. Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Richard S. <ri...@ri...> - 2003-06-03 21:10:42
|
Sounds great! This is very exciting and I look forward from hearing from you tomorrow :-) Best Regards, Richard Sumilang On Tuesday, June 3, 2003, at 01:55 PM, Matthew McNaney wrote: >> So to cut right to the chase, when can we see it implemented ;-) > > Let me see how much work it is tomorrow. > > Matthew McNaney > Internet Systems Architect > Electronic Student Services > Appalachian State University > Phone: 828-262-6493 > phpwebsite.appstate.edu > ess.appstate.edu > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: Eloi G. <el...@re...> - 2003-06-03 17:43:06
|
> I had a conversation with Brian and we came up with chaning the wording on > the checkbox and maybe the position of it in the form to "change" the > functionality of it. We could change it to "Activate Permissions" and if What do you mean, get change the "Admin" flag to "Activate Permissions"? That sounds great! I assume everyone would default to "true", right? -Eloi- |
|
From: R. S. B. <Ba...@Ba...> - 2003-06-10 13:25:48
|
I first created the folder, $webhome/images/menuman Placed 3 images in the new folder. Then entered the Control Panel | Site Content | Menu Manager | Edit ( for ID #1 under Current Menus ) | click on Settings | under Menu Indent click on Image Then select your images in the drop down menus for Default Image, Open Image, and Active Image. and then save your changes. Now you get broken links where ever the pics are.. It points to the right directories, but with no file name. <a href="http://mysite?&MMN_position=2:2"><img src="images/menuman/" alt="indent" border="0" /></a>  <a href="http://mysite?&MMN_position=2:2">Picard</a> Could someone verify this ?? Scott |
|
From: Steven L. <st...@tu...> - 2003-06-10 13:53:35
|
Scott, Yes this is a bug. If you would not mind submitting it to our sourceforge bug tracker I will fix it ASAP. Thanks, Steven > I first created the folder, $webhome/images/menuman > Placed 3 images in the new folder. > > Then entered the Control Panel | Site Content | > Menu Manager | Edit ( for ID #1 under Current Menus ) | click on Settings > | > under Menu Indent click on Image > > Then select your images in the drop down menus for Default Image, Open > Image, and Active Image. > > and then save your changes. > > Now you get broken links where ever the pics are.. > It points to the right directories, but with no file name. > > > <a href="http://mysite?&MMN_position=2:2"><img src="images/menuman/" > alt="indent" border="0" /></a>  > > > <a href="http://mysite?&MMN_position=2:2">Picard</a> > > Could someone verify this ?? > > Scott > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Steven Levin Electronic Student Services Appalachian State University Phone: 828.262.6740 PhpWebsite Development Team URL: http://phpwebsite.appstate.edu Email: st...@NO... |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X