Menu
▾
▴
phpwebsite-developers — For our development team.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(1) |
Mar
(265) |
Apr
(166) |
May
(25) |
Jun
(17) |
Jul
(20) |
Aug
(47) |
Sep
(6) |
Oct
(14) |
Nov
(66) |
Dec
(64) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(109) |
Feb
(64) |
Mar
(34) |
Apr
(23) |
May
(64) |
Jun
(9) |
Jul
(13) |
Aug
(6) |
Sep
(33) |
Oct
(272) |
Nov
(67) |
Dec
(75) |
| 2003 |
Jan
(264) |
Feb
(244) |
Mar
(171) |
Apr
(119) |
May
(54) |
Jun
(93) |
Jul
(51) |
Aug
(48) |
Sep
(14) |
Oct
(49) |
Nov
(47) |
Dec
(15) |
| 2004 |
Jan
(13) |
Feb
(27) |
Mar
(18) |
Apr
(44) |
May
(35) |
Jun
(24) |
Jul
(39) |
Aug
(142) |
Sep
(35) |
Oct
(34) |
Nov
(49) |
Dec
(24) |
| 2005 |
Jan
(60) |
Feb
(71) |
Mar
(19) |
Apr
(27) |
May
(68) |
Jun
(4) |
Jul
(30) |
Aug
(10) |
Sep
(23) |
Oct
(24) |
Nov
(13) |
Dec
(6) |
| 2006 |
Jan
(4) |
Feb
(46) |
Mar
(64) |
Apr
(18) |
May
(16) |
Jun
(37) |
Jul
(7) |
Aug
(19) |
Sep
(9) |
Oct
(8) |
Nov
(3) |
Dec
(23) |
| 2007 |
Jan
(25) |
Feb
(21) |
Mar
(32) |
Apr
(36) |
May
(12) |
Jun
(1) |
Jul
(7) |
Aug
(15) |
Sep
(13) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
(3) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(2) |
Aug
(7) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
|
| 2009 |
Jan
(7) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: <ad...@tu...> - 2003-06-11 13:48:50
|
Ryan, I see your logic here. We are going to be doing re-writes of several modules for the 0.9.3 release so they use the Item/Manager classes. During this re-write would be the best time to try and implement something like this. It would require working out several issues before any implementation could happen. Here's a few I can think of off the top of my head: FatCat would need a module to specify which categories it should create, easy part. You would then need a method for selecting items from the category without creating confusion to the user, a little harder. Then, once the item has been selected, you must make the page, event, or link aware of the categorized item it uses, again not too bad just tricky. Then, you would need to take into account a categorized item that gets deleted. This could be the worse of it. You would have to traverse the items using the deleted categorized item and either remove it or set it to hidden or something. > Since my group has a great deal of interest in the Pagemaster module due > to its importance in our use of the system, I have put considerable > thought into it. > > One of the thoughts that I had was in regard to the Categorizer. Firstly, > I am considering expanding Pagemaster's ability to add images to a page. > Obviously if people are allowed to upload their own images each time they > want to add one to a page, it could lead to severe file duplication on the > server. My thought is to use the document manager to upload the images > and handle them. Here's where my thought regarding the Categorizer comes > into play. > > Say that the categorizer comes with some specific categories (i.e. > Pagemaster->Images, Pagemaster->Links, etc), to which administrators, > wishing to create a portfolio of images for use in the Pagemaster module, > could add their images. Then in the pagemaster module, when a page > creator is trying to add an image to their page, they get a portfolio of > images made up of all the images in Pagemaster->Images. > > This would work for other modules as well: Menuman->Links, > Calendar->Images, etc. > > It seems to me, and please correct me if I'm wrong, that so far the > categorizer module has been used to group items together within a module > for relevance. All sports related pages/announcements are distinct from > all science related pages/announcements/etc. The reason I think this > would be most beneficial is that it would take that distinction and allow > it to be of use in the functionality of other modules (which is something > that I don't see it being used for yet). Plus I don't see it as being too > much of a change in code as much as a change in the way other modules use > the categorizer. > > > These are just my meandorings, but I was curious what the developer comm. > thought about it. Let me know if I jumped around too much and need to > explain anything better... I tend to ramble :) > > > Thanks, > > > Ryan Roland > > Application Developer > Information Technology Department > Division of Recreational Sports > Indiana University > > rmr...@in... > > > > ------------------------------------------------------- > 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 > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: <ad...@tu...> - 2003-06-11 13:31:43
|
Richard, You've got me looking closer at the search function in pagemaster now. :) I think I will add a page_id column to the section table so the section will know it's parent. Then it should be possible to pull all search results using only 2 queries as opposed to N+1 queries. I will make sure there is an update in the update.php file for pagemaster and release it with a patch release we have planned for sometime this week. I hope this will help you out as well as all our users who rely on heavy searching of pages. Adam > I was looking at the search module, (specifically with regard to the > Pagemaster module) and I noticed that the search performed in Pagemaster > loops through all pages and sections (with a query PER section). That > means if you have N sections in your entire site, that the search performs > exactly N+1 individual queries to the database. > > I'm working on a possible replacement for the current pagemaster search > function, and the only stumbling block is that I get sections, but can't > easily determine their parent pages from them. I'm sure this difficulty > is why the current scheme was used, but I'm trying to get to where there > are AT MOST N+2 queries issued to the DB (and that's only if every single > section has a match to the search criteria). > > Currently I'm looking at trying to use the 'section_order' field in the > pages table to determine if a given section is in a page, so I ask if > anyone can tell me now if that is a dead end or not. > > Any recommendations would be appreciated. > > > Thanks, > > > Ryan Roland > > Application Developer > Information Technology Department > Division of Recreational Sports > Indiana University > > rmr...@in... > > > > ------------------------------------------------------- > 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 > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: <ad...@tu...> - 2003-06-11 13:26:28
|
George, There are a couple of things you can do in this situation. One, you can create a link to the user side and put it in an existing tab. Just make sure you set admin=0 in your link definition in controlpanel.php and it will show up for general users. Two, you could create a Jobs tab on install and move your admin and user links to this tab. This may be a better solution since it will be more intuitive to your users. Just remember your admin link needs admin=1 and your user link needs admin=0. Hope this helps. Adam > Hi, > > I'm working on my module, jobman, in CVS using the latest phpwebsite-full > CVS as a testing environment. Jobman has an administrative interface > where > jobs get listed, added, deleted, and edited. But it also has an interface > for users, who can simply view the list as well as details of individual > jobs in the list. When I install jobman in the current CVS with the new > controlpanel.php file, the admin access works fine with an icon, name and > description. But how do users call up the list? > > Some modules put their user interface in My Settings, but that makes no > sense for a list of jobs. Is a menu item or an embedded link somewhere > the > only way for a user (not an admin) to access the list of jobs? The old > Modules interface provided a list of modules accessible to users, > including > content modules as well as settings modules. But the Control Panel (a) > doesn't do that and (b) doesn't sound right doing it. We're talking about > content, not control. > > Thanks for any feedback! > > George > ______________________________________ > George Brackett, Principal > George Brackett Associates > 617 413 4316 / gbr...@lu... > http://www.luceatlux.com/gba/ > > > > > ------------------------------------------------------- > 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 > -- 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-11 08:41:28
|
The Dev Utils module for PHP WebSite has been created to speed up development by worrying less about general code and more about your application. This module was developed in version 0.9.2 and would probably most likely work best in 0.9.2. Be sure to leave me your questions, comments, some money, or "i love you" messages at ri...@ri... http://www.richard-sumilang.com/devUtils.zip |
|
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... |
|
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: Matthew M. <ma...@tu...> - 2003-06-06 12:40:51
|
> phpwsBB is a native bulletin board module for the phpWebSite content > manage system, version 0.9.2 or later. Congrats Don. Not only is a great achievement but we can know post a link for the people that continuously hammer us with the question :) Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Matthew M. <ma...@tu...> - 2003-06-06 12:18:31
|
> This feature was done in 9.1 in the CVS but I don't see it in 9.2??? > >>> One thing that I would like to see in PageMaster would be the ability >>> to set a page title. I am getting the title of the page at the top of my browser. Are you saying you would prefer to set the separately or it is just not working for you? Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Steven L. <st...@tu...> - 2003-06-06 12:16:40
|
New help was added to blockmaker for 0.9.2. You just need to go into help and load blockmaker help. The reason it did not do this automatically was to avoid overwiting help that may have been updated by others. Steven > Just upgraded a site from 0.9.1 to 0.9.2. When I go to the blockmaker > control panel I get this notice at the top of the page: > > show_link could not locate a help label 'list_blocks' for the 'blockmaker' > module.show_link could not locate a help label 'create_block' for the > 'blockmaker' module. > > I can stil do everything that I need to, but the site admins will probably > be freaked at first. > > FYI. > > Don. > > > ------------------------------------------------------- > 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... |
|
From: <ad...@tu...> - 2003-06-06 12:14:07
|
The page title is set when you create the page and you can edit it at any time. It's in the same form as the category selection and page template selection. When a user views the page it shows up in the head of the document as well. Let me know if you still have trouble finding it, the interface will drastically improve with the re-write. Adam > This feature was done in 9.1 in the CVS but I don't see it in 9.2??? > > On Thursday, April 17, 2003, at 06:32 AM, Matthew McNaney wrote: > >>> One thing that I would like to see in PageMaster would be the ability >>> to set a page title. Page titles help your site rating in search >>> engines and are part of what search engines search for. I propose a >>> title field should be added to PageMaster! :-) >> >> This is in the CVS copy now, as is the ability to categorize pages and >> set >> up page templates. >> >> Matt >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> >> > > > > ------------------------------------------------------- > 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 > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
|
From: Don S. <do...@se...> - 2003-06-06 04:33:40
|
Just upgraded a site from 0.9.1 to 0.9.2. When I go to the blockmaker control panel I get this notice at the top of the page: show_link could not locate a help label 'list_blocks' for the 'blockmaker' module.show_link could not locate a help label 'create_block' for the 'blockmaker' module. I can stil do everything that I need to, but the site admins will probably be freaked at first. FYI. Don. |
|
From: Don S. <do...@se...> - 2003-06-06 03:38:11
|
phpwsBB is a native bulletin board module for the phpWebSite content manage system, version 0.9.2 or later. Today we release version 0.1.0 of phpwsBB. Features include anonymous posting, message editing and deletion for registered users, thread locking and message forking for admins, and ... well that's probably it. Be sure you have the latest version of phpWebSite installed (http://phpwebsite.appstate.edu) and then download it from http://phpwsbb.sourceforge.net. |
|
From: Richard S. <ri...@ri...> - 2003-06-06 02:08:48
|
This feature was done in 9.1 in the CVS but I don't see it in 9.2??? On Thursday, April 17, 2003, at 06:32 AM, Matthew McNaney wrote: >> One thing that I would like to see in PageMaster would be the ability >> to set a page title. Page titles help your site rating in search >> engines and are part of what search engines search for. I propose a >> title field should be added to PageMaster! :-) > > This is in the CVS copy now, as is the ability to categorize pages and > set > up page templates. > > Matt > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |
|
From: Don S. <do...@se...> - 2003-06-04 22:17:27
|
I'm getting close to finishing the first release for a native bulletin board module. It requires phpws 0.9.2 or CVS. https://sourceforge.net/project/showfiles.php?group_id=81360&release_id=163595 Don. |
|
From: Roland, R. M <rmr...@in...> - 2003-06-04 18:26:34
|
Since my group has a great deal of interest in the Pagemaster module due = to its importance in our use of the system, I have put considerable = thought into it. =20 One of the thoughts that I had was in regard to the Categorizer. = Firstly, I am considering expanding Pagemaster's ability to add images = to a page. Obviously if people are allowed to upload their own images = each time they want to add one to a page, it could lead to severe file = duplication on the server. My thought is to use the document manager to = upload the images and handle them. Here's where my thought regarding = the Categorizer comes into play. =20 Say that the categorizer comes with some specific categories (i.e. = Pagemaster->Images, Pagemaster->Links, etc), to which administrators, = wishing to create a portfolio of images for use in the Pagemaster = module, could add their images. Then in the pagemaster module, when a = page creator is trying to add an image to their page, they get a = portfolio of images made up of all the images in Pagemaster->Images.=20 This would work for other modules as well: Menuman->Links, = Calendar->Images, etc. It seems to me, and please correct me if I'm wrong, that so far the = categorizer module has been used to group items together within a module = for relevance. All sports related pages/announcements are distinct from = all science related pages/announcements/etc. The reason I think this = would be most beneficial is that it would take that distinction and = allow it to be of use in the functionality of other modules (which is = something that I don't see it being used for yet). Plus I don't see it = as being too much of a change in code as much as a change in the way = other modules use the categorizer. These are just my meandorings, but I was curious what the developer = comm. thought about it. Let me know if I jumped around too much and = need to explain anything better... I tend to ramble :) Thanks, Ryan Roland Application Developer Information Technology Department Division of Recreational Sports Indiana University rmr...@in... |
|
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: 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 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: 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: 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: <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: 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: 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: 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: <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 |
5 messages has been excluded from this view by a project administrator.
