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: Don S. <do...@se...> - 2003-01-14 21:34:34
|
Is Schedule something for calendar appointments or is it something like cron/at? Don. On Tue, 14 Jan 2003, Matthew McNaney wrote: > > Wait a sec. <confused frown> > > > > I thought you three were running the project. > > Adam and Steven felt out of the loop on the changes. I appologized to them > personally. I hope they are feeling better about it and I promised to get > right on any problems that arise. > > I will stop tinkering. > > Matt > > |
From: Michael C. <mi...@ca...> - 2003-01-14 20:36:07
|
Code, refactor, code some more... I've noticed that the phpWebSite RSS feed shows articles not approved yet. Michael |
From: Matthew M. <ma...@tu...> - 2003-01-14 19:45:36
|
> Wait a sec. <confused frown> > > I thought you three were running the project. Adam and Steven felt out of the loop on the changes. I appologized to them personally. I hope they are feeling better about it and I promised to get right on any problems that arise. I will stop tinkering. Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
From: Mike N. <mh...@us...> - 2003-01-14 19:36:38
|
On Tue, 2003-01-14 at 11:08, Don Seiler wrote: > In trying to port some documentation over to pagemaster, I noticed that I > have a lot of references to variables inside < and > chars, like "<pid>". > The problem is pagemaster is interpreting this as an attempted HTML tag > and stripping it out. I have a lot of different references so adding > every one to the allowed_tags var isn't reasonable. < and > get > altered by pagemaster so they literally display "<" or ">" > respectively. Don, PageMaster may need to be modified, so it doesn't convert & to & if & is followed by a ;. > Is there a way to get those chars to display? Unknown by me. -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Don S. <do...@se...> - 2003-01-14 19:08:48
|
In trying to port some documentation over to pagemaster, I noticed that I have a lot of references to variables inside < and > chars, like "<pid>". The problem is pagemaster is interpreting this as an attempted HTML tag and stripping it out. I have a lot of different references so adding every one to the allowed_tags var isn't reasonable. < and > get altered by pagemaster so they literally display "<" or ">" respectively. Is there a way to get those chars to display? Don. |
From: Eloi G. <el...@re...> - 2003-01-14 19:06:37
|
Wait a sec. <confused frown> I thought you three were running the project. |
From: Adam M. <ad...@tu...> - 2003-01-14 18:26:26
|
I am also concerned about the number of changes being made since the last release candidate. It seemed that the underlying code was finally stabalizing and becoming bug free. To replace this mostly stable code with new beta code is effectively negating this. Unfortunately I have little control over this issue. I only hope that the changes are stabalized quickly and the amount of editing I must do to my modules remains minimal. Adam --------------------------------------------------------------------- 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-01-14 17:27:54
|
I agree 100% we definately need someone to say "FEATURE FREEZE" so we can stablize what we have got and finally put out a FINAL version. I don't know what else to say since I do not have much control. I hope you will stick with us, your contributions to the development process have been much appreciated. -- Steven Levin Electronic Student Services Appalachian State University Phone: 828.262.2431 PhpWebsite Development Team URL: http://phpwebsite.appstate.edu Email: st...@NO... |
From: Matthew M. <ma...@tu...> - 2003-01-14 15:57:23
|
Joost, Much of the rewriting is done because once we say it is a FINAL release, we are severely limited in what we can change. In all cases it was warranted. For example, layout needed restructuring. It has been the same code for over a year. I have learned a lot since then and I want to apply that to the code. It was missing key components and the interface was sloppy. The location change for the layout.php file was something approved by the developers. As for approval, it had bugs and was kludgey. The new format doesn't require registration and should be easier to manage. Other than that, I would say we are very close to a final release. However, until we release the final code, I would not recommend those with tight deadlines to depend upon its delivery. I don't with to discourage you however. Remember that for every change, I have alter all my modules as well. So far, none have been very time consuming. Best regards, Matt ---- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
From: Don S. <do...@se...> - 2003-01-14 15:43:52
|
This is pretty much the sentiment I was trying to carry in my earlier email. I have no intention of going to another CMS, but I do need a doc management system and I sold my boss on PageMaster. Obviously now I have to play the waiting game. I hate to appear ungrateful since you guys are doing all the work, and a lot of the changes are for the better. From a software development point-of-view, just wondering if we'll see a feature freeze and only go into bug-fix mode. It would probably allow us to find bugs more reliably if new features weren't coming in every day (as Joost said). My 2 cents, Don. On Tue, 14 Jan 2003 joo...@bt... wrote: > First of all - I *really* like phpWebSite. I highly appreciate the effort and dedication of all involved. Above all, the concept is great. > Also, it's the university's project, and I respect their right to take the project forward in whichever way they see fit. > > I would like to express some concerns, though. > > For several months I have been following the development of phpWebsite. When I asked back in September/October (don't remember exactly) when it would be ready The reply was <<whenever there are no more bugs>> which seemed fair enough. > > I started to test the RC's as I would with an RC of any other piece of software. > > To my surprise, I have seen complete rewrites of large parts of phpWebSite between RC's -another major rewrite announced a few days ago - it seems there is no intention to actually go in <release mode> - just fix bugs and create a stable version - > not add functionality for a while. In my experience, when you don't do a feature freeze you will add each week the same amount of bugs as you are solving - and there will never be a release. > > For me the moment of truth is near for phpWebSite - I have to make a decision this week. My options are: > 1. Wait without an idea of a release date. You can see the difficulty of that. > 2. Take RC3, fix a few bugs, and go with that. It will certainly work but I will find myself on a 'mod island' - my mod's won't work for anyone else, and I cannot share my mods with anyone. > 3. Go for some other CMS. I had a quick look at some others already. None has the modular structure done properly like you guys have. > > Again I am really appreciating the effort and I am in no way trying to upset you (please don't be!) but I am facing a real challenge here and I thought the right thing for me to do was to raise the issue rather than silently create a fork or bail out altogether. That would be so sad. > > > Any thoughts or advise would be helpful. > > > Thanks! > > Joost > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
From: <joo...@bt...> - 2003-01-14 14:05:01
|
First of all - I *really* like phpWebSite. I highly appreciate the effort and dedication of all involved. Above all, the concept is great. Also, it's the university's project, and I respect their right to take the project forward in whichever way they see fit. I would like to express some concerns, though. For several months I have been following the development of phpWebsite. When I asked back in September/October (don't remember exactly) when it would be ready The reply was <<whenever there are no more bugs>> which seemed fair enough. I started to test the RC's as I would with an RC of any other piece of software. To my surprise, I have seen complete rewrites of large parts of phpWebSite between RC's -another major rewrite announced a few days ago - it seems there is no intention to actually go in <release mode> - just fix bugs and create a stable version - not add functionality for a while. In my experience, when you don't do a feature freeze you will add each week the same amount of bugs as you are solving - and there will never be a release. For me the moment of truth is near for phpWebSite - I have to make a decision this week. My options are: 1. Wait without an idea of a release date. You can see the difficulty of that. 2. Take RC3, fix a few bugs, and go with that. It will certainly work but I will find myself on a 'mod island' - my mod's won't work for anyone else, and I cannot share my mods with anyone. 3. Go for some other CMS. I had a quick look at some others already. None has the modular structure done properly like you guys have. Again I am really appreciating the effort and I am in no way trying to upset you (please don't be!) but I am facing a real challenge here and I thought the right thing for me to do was to raise the issue rather than silently create a fork or bail out altogether. That would be so sad. Any thoughts or advise would be helpful. Thanks! Joost |
From: Don S. <do...@se...> - 2003-01-14 03:33:09
|
I have an issue on my home webserver, which is behind a firewall. The firewall forwards port 80 to that webserver. Names being changed to protect the pr0n, the webservers name is rufus.xavier.sasparilla on the LAN, and that is what is in it's hostname file. However I'm also running one of those dynamic dns things so I can tinker from the outside, and that name is rxs.homelinux.org. I've entered rxs.homelinux.org into my local /etc/hosts file at home so I can just use that name home and abroad, and that is the name in my phpws config.php file. However when I use that outside name, my module icons are gone, and instead I have little red boxes. When I configure phpws with the internal name and use that, the icons are there. I've been tracing it through the moduleList function in the User class, but got stuck and/or lost. Obviously it's not the end of the world but it was odd nonetheless and I thought I'd pass it on. I've seen this behavior with RC3 and up to yesterday's CVS. Todays CVS is funky so I haven't tried. I can file this as a bug if you guys would like. I probably should be using the bug interface more anyway. Don. |
From: Matthew M. <ma...@tu...> - 2003-01-14 01:24:29
|
Update: Fixed the problem. Will commit in the morning. -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu > CVS is gablooey while I'll try to fix layout. > > Sorry :( > > -- > 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: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
From: Matthew M. <ma...@tu...> - 2003-01-13 22:42:49
|
> When will these changes go into effect? Probably this week. Matt |
From: Matthew M. <ma...@tu...> - 2003-01-13 22:38:46
|
CVS is gablooey while I'll try to fix layout. Sorry :( -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
From: Don S. <do...@se...> - 2003-01-13 20:30:27
|
When will these changes go into effect? I see the layout.php one was done today. Just wondering if they are supported now in CVS and I can adjust my module, or if I need to wait for changes or if parts of these changes are being postponed. Don. On Fri, 3 Jan 2003, Adam Morton wrote: > Hello all! > > I have one more proposal I would like to get out and hopefully implemented > before the stable release. Please read over it and let me know what you > think: > > Any directory in your module that is put there to "tie into" another > module should be named according to the other module. Case in point is > Boost. Right now we have a setup directory that is only used by Boost. > This should be renamed to 'boost'. Not only does it make more sense, it > also makes it easy to spot which modules are required by your module to > run. > > This naming convention should also apply to the config files in the config > directory. The altered file structure would look roughly like this: > > class => MyModule.php > conf => boost.php (currently mod_info.php) > layout.php (currently layout_info.php) > help.php (currently help_info.php) > docs => README.txt > INSTALL.txt > boost => install.sql > uninstall.sql > > See? Now you can tell which config files are used by which modules a > little easier, it allows for scalability as more and more modules are > added, and it sets the stage for some more enhancements to boost later on. > Of course those changes are another proposal all together :) > > Let me know what you all think! > > Cheers! > Adam > > --------------------------------------------------------------------- > 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:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
From: Mike N. <mh...@us...> - 2003-01-13 18:44:29
|
On Mon, 2003-01-13 at 04:54, Matthew McNaney wrote: > I forgot to mention. There is one other problem with incomplete links that > is causing problems with the validator. > > https://sourceforge.net/tracker/index.php?func=detail&aid=666271&group_id=15539&atid=115539 > > Once the solution is completed, we will update. Matt, Congratulations on phpWS 0.9x generating valid XHTML 1.0 Transitional pages. Very nice job. :-) -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Don S. <do...@se...> - 2003-01-13 18:40:13
|
I'm wondering how many more changes we will see. By now one might think that the changes would just be bug fixes before the release, but these are somewhat major changes. In addition to copying setup/layout_info.php to conf/layout.php, should I remove layout_info.php? Don. |
From: Mike N. <mh...@us...> - 2003-01-13 18:36:42
|
phpWS team, You may not be aware of this. Processing of trackers does affect your project rank on SourceForge. On Mon, 2003-01-13 at 10:17, Mike Noyes wrote: > phpWS team, > I suggest someone process (assign, close, comment on) the 36 open bug > reports on SourceForge. Is this task assigned to Ryan Cowan (cowanra, > Support Manager)? > > Bug reports > https://sourceforge.net/tracker/?func=browse&group_id=15539&atid=115539 > > Note: the 60 open feature requests need attention also. > > Feature requests > https://sourceforge.net/tracker/?atid=365539&group_id=15539&func=browse -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Don S. <do...@se...> - 2003-01-13 18:12:33
|
This appears to be fixed now in the latest CVS. Thanks, Don. On Thu, 9 Jan 2003, Don Seiler wrote: > Also the main page is blank when I told it to use an internal page for the > main page. The original pagemaster demo did show up fine. > > When I say "blank", I just mean the part where my page content would be. > All other phpws headers, footers, and menus are there. > > Don. > > On Thu, 9 Jan 2003, Don Seiler wrote: > > > I notice that, among others, pagemaster for 0.9.x removes <th>,<tt>, and > > <blockquote> tags. > > > > I looked around but I can't find any place to tell it waht to allow or > > deny. > > > > Have I goofed? > > > > Don. > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: > > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > > http://www.vasoftware.com > > _______________________________________________ > > Phpwebsite-developers mailing list > > Php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
From: Mike N. <mh...@us...> - 2003-01-13 18:12:28
|
phpWS team, I suggest someone process (assign, close, comment on) the 36 open bug reports on SourceForge. Is this task assigned to Ryan Cowan (cowanra, Support Manager)? Bug reports https://sourceforge.net/tracker/?func=browse&group_id=15539&atid=115539 Note: the 60 open feature requests need attention also. Feature requests https://sourceforge.net/tracker/?atid=365539&group_id=15539&func=browse -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Eloi G. <el...@re...> - 2003-01-13 17:51:00
|
> Are you trying to use it with a boxstyle that contains a footer tag? Heh heh. Sometimes the simple things in life elude me. <sheepish grin> May I suggest footers be included in all default themes? If they're not available for most themes (which will be based on the included ones), then module developers won't bother taking advantage of this feature. Eloi George |
From: Matthew M. <ma...@tu...> - 2003-01-13 16:34:23
|
Are you trying to use it with a boxstyle that contains a footer tag? Most do not. Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu > Speaking of Layout, reference in the documentation was made about > footers, but putting $GLOBALS["CNT_mymodule"]["footer"] = > "this is a footer"; > > in the code didn't output anything on the .rc3 installation. How's it > supposed to work? > > Eloi George > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
From: Eloi G. <el...@re...> - 2003-01-13 16:01:36
|
Speaking of Layout, reference in the documentation was made about footers, but putting $GLOBALS["CNT_mymodule"]["footer"] = "this is a footer"; in the code didn't output anything on the .rc3 installation. How's it supposed to work? Eloi George |
From: Matthew M. <ma...@tu...> - 2003-01-13 12:48:49
|
I forgot to mention. There is one other problem with incomplete links that is causing problems with the validator. https://sourceforge.net/tracker/index.php?func=detail&aid=666271&group_id=15539&atid=115539 Once the solution is completed, we will update. Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu > On Sat, 2003-01-11 at 10:00, Matthew McNaney wrote: >> I worked on the theme to get it compliant. >> >> Once it was, the problem went away :) > > Matt, > Congratulations on the fix. However, I'm still seeing 140 errors when > validating the site. I believe many of them could be corrected by > changing the php.ini arg_separator.output to &. > > -- > Mike Noyes <mhnoyes @ users.sourceforge.net> > http://sourceforge.net/users/mhnoyes/ > http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |