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: Mike W. <wi...@ce...> - 2003-03-16 04:00:18
|
Here is a good article that covers just about all the cache systems out there. http://www.nukethemes.de/printarticle208.html Mike |
From: Don S. <do...@se...> - 2003-03-14 22:20:03
|
Noyes is a CVS wizard. ph34r him. Don. On Fri, 14 Mar 2003 ad...@tu... wrote: > > OK I've finished modifying the CVSROOT/modules file on res and it works > great! No longer do you need the build_phpws.sh script! Simply use > either: > > cvs co phpwebsite-full > -or- > cvs co phpwebsite-core > > to get your entire phpwebsite installation. The full get absolutely > everything. The core co gets the core files, core modules, and just the > Default theme. On checkout a phpwebsite-full or phpwebsite-core directory > is created and phpwebsite is "built" inside that directory. > > Enjoy! > Adam > > |
From: Mike N. <mh...@us...> - 2003-03-14 21:07:31
|
On Fri, 2003-03-14 at 12:38, ad...@tu... wrote: > OK I've finished modifying the CVSROOT/modules file on res and it works > great! No longer do you need the build_phpws.sh script! Simply use > either: > > cvs co phpwebsite-full > -or- > cvs co phpwebsite-core > > to get your entire phpwebsite installation. The full get absolutely > everything. The core co gets the core files, core modules, and just the > Default theme. On checkout a phpwebsite-full or phpwebsite-core directory > is created and phpwebsite is "built" inside that directory. Adam, Very nice job. :-) BTW, what other modules are defined? -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Matthew M. <ma...@tu...> - 2003-03-14 20:46:34
|
For my modules: If any functions are only used once, you can just dump at the bottom of the file that uses it and remove the core-> from the front. Alert me when done and I'll clean up. Matt |
From: Matthew M. <ma...@tu...> - 2003-03-14 20:40:34
|
> > OK I've finished modifying the CVSROOT/modules file on res and it works > great! No longer do you need the build_phpws.sh script! Simply use > either: > > cvs co phpwebsite-full > -or- > cvs co phpwebsite-core > > to get your entire phpwebsite installation. The full get absolutely > everything. The core co gets the core files, core modules, and just the > Default theme. On checkout a phpwebsite-full or phpwebsite-core directory > is created and phpwebsite is "built" inside that directory. Good job. Thanks for setting this up for us. Matt |
From: <ad...@tu...> - 2003-03-14 20:34:15
|
OK I've finished modifying the CVSROOT/modules file on res and it works great! No longer do you need the build_phpws.sh script! Simply use either: cvs co phpwebsite-full -or- cvs co phpwebsite-core to get your entire phpwebsite installation. The full get absolutely everything. The core co gets the core files, core modules, and just the Default theme. On checkout a phpwebsite-full or phpwebsite-core directory is created and phpwebsite is "built" inside that directory. Enjoy! Adam -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
From: <ad...@tu...> - 2003-03-14 20:30:02
|
> Array.php: shove > shoveAssoc > XML_it > cmp > > Text.php: error_list > > If no one has any objection I would like to remove these functions just > for general clean-up purposes. (Trying to reduce memory limit) +1 to killing all of those. > Also there are functions which are only being used by one module. > > Array.php: swap (phatform) KEEP > Array.php: reindex (phatform) KEEP > Array.php: maxKey (layout) MOVE > Array.php: objectToArray (calendar) MOVE > Database.php: sqlFriendlyName (phatform) KEEP > Database.php: sqlImport (setup/boost specific) KEEP > Database.php: clock (calendar) MOVE > Database.php: alphabet (users) MOVE > WizardBag.php: whereami (comments) MOVE -- 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-03-14 20:15:36
|
Hello All, I was sifting through the core today and found a few functions that are no longer being used. Array.php: shove shoveAssoc XML_it cmp Text.php: error_list If no one has any objection I would like to remove these functions just for general clean-up purposes. (Trying to reduce memory limit) Also there are functions which are only being used by one module. Array.php: swap (phatform) reindex (phatform) maxKey (layout) objectToArray (calendar) Database.php: sqlFriendlyName (phatform) sqlImport (setup/boost specific) - I figure sqlImport and all the helper functions can be included with boost and setup (when they run) Form.php: clock (calendar) alphabet (users) WizardBag.php: whereami (comments) For these functions we should vote on whether they stay in the core, or be moved to the module where they are used. Thanks! -- 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-03-14 19:47:29
|
After reading up on cvshome.org I feel like I can get this working. I will take a crack at it now. Wish me luck and thanks for all the info again Mike :) Adam > On Fri, 2003-03-14 at 11:16, Mike Noyes wrote: >> Instead of using a script you may want to consider defining modules in >> CVSROOT. After modifying the modules file a checkout would look like: >> >> $ cvs co core m_announce m_pagemaster t_Cool t_clean >> >> >> C.1 The modules file >> http://www.cvshome.org/docs/manual/cvs_18.html#SEC157 >> >> Example **NOT TESTED** CVSROOT/modules: > > Adam, > Here is an extreme example of what is possible with CVSROOT/modules. > > modules -r 1.236 > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/CVSROOT/ > > -- > 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:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > 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: Mike N. <mh...@us...> - 2003-03-14 19:27:33
|
On Fri, 2003-03-14 at 11:16, Mike Noyes wrote: > Instead of using a script you may want to consider defining modules in > CVSROOT. After modifying the modules file a checkout would look like: > > $ cvs co core m_announce m_pagemaster t_Cool t_clean > > > C.1 The modules file > http://www.cvshome.org/docs/manual/cvs_18.html#SEC157 > > Example **NOT TESTED** CVSROOT/modules: Adam, Here is an extreme example of what is possible with CVSROOT/modules. modules -r 1.236 http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/CVSROOT/ -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Mike N. <mh...@us...> - 2003-03-14 19:16:10
|
On Fri, 2003-03-14 at 08:56, ad...@tu... wrote: > > I commited some changes to build_phpws.sh in the shellscripts repository. > Basically I was getting irritated at having to do a 'cvs update' in the > base dir then the mod dir then the themes dir. Now after you build your > development environment using the script you can use update, commit, and > edit from the base dir and it will get all the modules and themes as well. Adam, Instead of using a script you may want to consider defining modules in CVSROOT. After modifying the modules file a checkout would look like: $ cvs co core m_announce m_pagemaster t_Cool t_clean C.1 The modules file http://www.cvshome.org/docs/manual/cvs_18.html#SEC157 Example **NOT TESTED** CVSROOT/modules: c_approval -d phpwebsite/mod/approval approval c_branch -d phpwebsite/mod/branch branch c_debug -d phpwebsite/mod/debug debug c_boost -d phpwebsite/mod/boost boost c_help -d phpwebsite/mod/help help c_language -d phpwebsite/mod/language language c_layout -d phpwebsite/mod/layout layout c_modmaker -d phpwebsite/mod/modmaker modmaker c_search -d phpwebsite/mod/search search c_security -d phpwebsite/mod/security security c_users -d phpwebsite/mod/users users core &phpwebsite \ &c_approval \ &c_branch \ &c_debug \ &c_boost \ &c_help \ &c_language \ &c_layout \ &c_modmaker \ &c_search \ &c_security \ &c_users m_announce -d phpwebsite/mod/announce announce m_blockmaker -d phpwebsite/mod/blockmaker blockmaker m_calendar -d phpwebsite/mod/calendar calendar m_comments -d phpwebsite/mod/comments comments m_fatcat -d phpwebsite/mod/fatcat fatcat m_linkman -d phpwebsite/mod/linkman linkman m_menuman -d phpwebsite/mod/menuman menuman m_notes -d phpwebsite/mod/notes notes m_pagemaster -d phpwebsite/mod/pagemaster pagemaster m_phatform -d phpwebsite/mod/phatform phatform m_textpad -d phpwebsite/mod/textpad textpad t_AHP -d phpwebsite/themes/AHP AHP t_Cool -d phpwebsite/themes/Cool Cool t_Default -d phpwebsite/themes/Default t_Quick -d phpwebsite/themes/Quick Quick t_Smooth -d phpwebsite/themes/Smooth Smooth t_clean -d phpwebsite/themes/clean clean t_cowboy -d phpwebsite/themes/cowboy cowboy t_mainsite -d phpwebsite/themes/mainsite mainsite t_muggles -d phpwebsite/themes/muggles muggles t_shiny -d phpwebsite/themes/shiny shiny t_winxp -d phpwebsite/themes/winxp winxp -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: <ad...@tu...> - 2003-03-14 17:26:13
|
Mike, Thanks for all the info! It is very helpful. I will look into making the TAG changes in the 'ballz' script instead. That script is intended to create tarballs of the full phpwebsite install or any piece therein. Adding tag support to that script would make it more flexible and powerful. Adam > On Fri, 2003-03-14 at 09:02, Mike Noyes wrote: >> On Fri, 2003-03-14 at 08:33, ad...@tu... wrote: >> > And will the developer be protected from checking out from a >> particular >> > tag point and then later commiting their code and accidentally having >> old >> > code from that tag point overwrite new code that is most recent in >> cvs? >> >> A developer wont be able to use an export to commit changes. It's not a >> working copy. > > Adam, > Here are some additional resources that explain the 'benefits of/uses > for' tags. > > cvshome.org: "More about branching and tagging" > http://www.cvshome.org/docs/manual/cvs_4.html#SEC48 > > The Cederqvist Manual: "Branches" > http://www.gnu.org/manual/cvs/html_chapter/cvs_8.html#SEC50 > > Open Source Development with CVS: > "Marking A Moment In Time (Tags)" "Branches" > http://cvsbook.red-bean.com/cvsbook.html#Marking_A_Moment_In_Time__Tags_ > http://cvsbook.red-bean.com/cvsbook.html#Branches > > -- > 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:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > 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: Mike N. <mh...@us...> - 2003-03-14 17:17:32
|
On Fri, 2003-03-14 at 09:02, Mike Noyes wrote: > On Fri, 2003-03-14 at 08:33, ad...@tu... wrote: > > And will the developer be protected from checking out from a particular > > tag point and then later commiting their code and accidentally having old > > code from that tag point overwrite new code that is most recent in cvs? > > A developer wont be able to use an export to commit changes. It's not a > working copy. Adam, Here are some additional resources that explain the 'benefits of/uses for' tags. cvshome.org: "More about branching and tagging" http://www.cvshome.org/docs/manual/cvs_4.html#SEC48 The Cederqvist Manual: "Branches" http://www.gnu.org/manual/cvs/html_chapter/cvs_8.html#SEC50 Open Source Development with CVS: "Marking A Moment In Time (Tags)" "Branches" http://cvsbook.red-bean.com/cvsbook.html#Marking_A_Moment_In_Time__Tags_ http://cvsbook.red-bean.com/cvsbook.html#Branches -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Mike N. <mh...@us...> - 2003-03-14 17:01:47
|
On Fri, 2003-03-14 at 08:33, ad...@tu... wrote: > Bringing up old school stuff...I am updating some stuff in the > build_phpws.sh file and I was going to add your diff to the file. I just > have a couple of questions. Adam, I hope I'm able to answer them. :) > Is this command a checkout or an export? > > cvs $REMOTE -q ex -r"$TAG" phpwebsite export = exp = ex > If it's an export, I'm not sure this method will work in this particular > script since it is meant to build the most recent cvs copy of phpwebsite, > themes, and modules with the expectation that the developer will be > updating that code and later commit it. Then I misinterpreted the intent of the script. An export contains no CVS control files, and is not a functional working copy of the repository module. > And will the developer be protected from checking out from a particular > tag point and then later commiting their code and accidentally having old > code from that tag point overwrite new code that is most recent in cvs? A developer wont be able to use an export to commit changes. It's not a working copy. > Also what does the tag 'HEAD' mean? :) HEAD is a "symbolic tag" usually associated with the most recent version of all files in a repository module. The other way to export the most current files from a cvs module is to use date with timezone. The timezone is necessary because cvs assumes local TZ when performing operations. Obviously this can lead to exports that are up to 24 hours old. I use the following string for date exports: DATE=`date '+%Y-%m-%d %T %Z'` -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: <ad...@tu...> - 2003-03-14 16:53:04
|
I commited some changes to build_phpws.sh in the shellscripts repository. Basically I was getting irritated at having to do a 'cvs update' in the base dir then the mod dir then the themes dir. Now after you build your development environment using the script you can use update, commit, and edit from the base dir and it will get all the modules and themes as well. If you're working with an install created using the old build_phpws.sh, I would suggest rebuilding it using the new one updated today as it will make your life easier. Adam -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |
From: <ad...@tu...> - 2003-03-14 16:29:28
|
Mike, Bringing up old school stuff...I am updating some stuff in the build_phpws.sh file and I was going to add your diff to the file. I just have a couple of questions. Is this command a checkout or an export? cvs $REMOTE -q ex -r"$TAG" phpwebsite If it's an export, I'm not sure this method will work in this particular script since it is meant to build the most recent cvs copy of phpwebsite, themes, and modules with the expectation that the developer will be updating that code and later commit it. And will the developer be protected from checking out from a particular tag point and then later commiting their code and accidentally having old code from that tag point overwrite new code that is most recent in cvs? Also what does the tag 'HEAD' mean? :) Adam > Adam, > I have a diff for your shell script. Instead of checking out modules it > exports them based on tags. This will allow developers to work from > known tag points, and avoids the unnecessary CVS directory clutter > checkout creates. > > > $ diff -u ~/leaf/phpwebsite/build_phpws.sh ~/bin/build_phpws.sh > --- /home/mhnoyes/leaf/phpwebsite/build_phpws.sh Mon Feb 24 09:22:19 > 2003+++ /home/mhnoyes/bin/build_phpws.sh Mon Feb 24 11:00:25 2003 > @@ -27,25 +27,28 @@ > # Themes to check out > THEMES="AHP clean Default gax mainsite shiny winxp" > > +# Tag to retrieve from repository > +TAG=HEAD > + > ################################################ > # END SETTINGS: Do not edit beyond this line!! # > ################################################ > > # Grab the phpwebsite core and core modules > -cvs $REMOTE co phpwebsite > +cvs $REMOTE -q ex -r"$TAG" phpwebsite > for i in $CORE_MODULES; do > - cvs $REMOTE co $i > + cvs $REMOTE -q ex -r"$TAG" $i > mv $i phpwebsite/mod/ > done > > # Grab any extra modules the user wants > for i in $OTHER_MODULES; do > - cvs $REMOTE co $i > + cvs $REMOTE -q ex -r"$TAG" $i > mv $i phpwebsite/mod/ > done > > # Check out all themes and pick each one out individually > -cvs $REMOTE co themes > +cvs $REMOTE -q ex -r"$TAG" themes > for i in $THEMES; do > mv themes/$i phpwebsite/themes/ > done > > > -- > 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:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > 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: spiggy t. <th...@me...> - 2003-03-13 18:26:57
|
i have been using this for almost a year or so with no problems. and any reduction to response time cant be bad :) but i believe mike is right; i does require access to php.ini. paivi |
From: Mike N. <mh...@us...> - 2003-03-13 16:57:12
|
On Thu, 2003-03-13 at 08:06, Matthew McNaney wrote: > This was posted on sourceforge forums. Anyone have any experience with it? > > http://www.php-accelerator.co.uk/ Matt, I hope I'm wrong, but this extension apparently requires access to php.ini to install. extension_dir directive is PHP_INI_SYSTEM http://www.php-accelerator.co.uk/releases/1.3.2/INSTALL 1. Add the following line to your php.ini file, e.g. near the extensions section. Set the correct path to where you installed the accelerator library. /usr/local/lib is a typical directory to use. ; PHP Accelerator extension zend_extension="/path/to/php_accelerator_1.3.2.so" -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ |
From: Matthew M. <ma...@tu...> - 2003-03-13 16:02:41
|
This was posted on sourceforge forums. Anyone have any experience with it? http://www.php-accelerator.co.uk/ 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-03-12 20:23:37
|
I added a new function to the PHPWS_File class today called 'rmdir'. It will remove a directory and all it's contents and does not rely on the system being a unix-based environment. As folks get a chance, update anywhere you are removing directories using system("rm -rf $dir") and use PHPWS_File::rmdir($dir) instead. Also anywhere you are creating directories using system("mkdir $dir"), use the PHP provided mkdir($dir) instead. This will help to ensure phpws running smoothly in multiple environments. 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-03-12 19:21:56
|
http://www.horde.org/papers/kongress2002-design_patterns/ -- Steven Levin Electronic Student Services Appalachian State University Phone: 828.262.2431 PhpWebsite Development Team URL: http://phpwebsite.appstate.edu Email: st...@NO... |
From: Jeremy A. <ja...@tu...> - 2003-03-12 19:00:16
|
The pear package under the downloads section has been updated. I also did a fresh cvs daily build so they should be up to date with the pear change. > > Just so everyone knows, the requirements for phpwebsite are being updated. > Version 1.1 of HTML_Template_IT was released today (woot Pierre!). It > addresses some issues we were having with the template system. I have > updated some core code to stop using our own fixes to these issues and > those changes will get commited sometime today. If you're running a cvs > version of phpwebsite, I would suggest you update your IT package to the > latest version before updating your cvs copy. You can download it here: > > HTML_Template_IT: > http://pear.php.net/package-info.php?pacid=108 > > 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:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Jeremy Agee phpWebSite Development Team (http://phpwebsite.appstate.edu) Appalachian State University SF.net id: jagee or 94756 |
From: Don S. <do...@se...> - 2003-03-12 18:01:38
|
Ah looks good. Thanks, Don. On Wed, 12 Mar 2003 ad...@tu... wrote: > > I'm pretty sure Jeremy set that up. If it is setup, the tarballs can be > found at: > > http://phpwebsite.appstate.edu/downloads/daily-cvs/ > > Adam > > > Do you guys still provide nightly cvs snapshots of your code? My > > employer's MIS team fixed a networking issue I was having but in doing so > > cut off my external CVS access through our firewall. :p > > > > Don. > > > > On Wed, 12 Mar 2003 ad...@tu... wrote: > > > >> > >> Just so everyone knows, the requirements for phpwebsite are being > >> updated. > >> Version 1.1 of HTML_Template_IT was released today (woot Pierre!). It > >> addresses some issues we were having with the template system. I have > >> updated some core code to stop using our own fixes to these issues and > >> those changes will get commited sometime today. If you're running a cvs > >> version of phpwebsite, I would suggest you update your IT package to the > >> latest version before updating your cvs copy. You can download it here: > >> > >> HTML_Template_IT: > >> http://pear.php.net/package-info.php?pacid=108 > >> > >> 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:Crypto Challenge is now open! > >> Get cracking and register here for some mind boggling fun and > >> the chance of winning an Apple iPod: > >> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > >> _______________________________________________ > >> Phpwebsite-developers mailing list > >> Php...@li... > >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > >> > >> > >> > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by:Crypto Challenge is now open! > > Get cracking and register here for some mind boggling fun and > > the chance of winning an Apple iPod: > > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > > _______________________________________________ > > 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:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
From: <ad...@tu...> - 2003-03-12 17:58:09
|
I'm pretty sure Jeremy set that up. If it is setup, the tarballs can be found at: http://phpwebsite.appstate.edu/downloads/daily-cvs/ Adam > Do you guys still provide nightly cvs snapshots of your code? My > employer's MIS team fixed a networking issue I was having but in doing so > cut off my external CVS access through our firewall. :p > > Don. > > On Wed, 12 Mar 2003 ad...@tu... wrote: > >> >> Just so everyone knows, the requirements for phpwebsite are being >> updated. >> Version 1.1 of HTML_Template_IT was released today (woot Pierre!). It >> addresses some issues we were having with the template system. I have >> updated some core code to stop using our own fixes to these issues and >> those changes will get commited sometime today. If you're running a cvs >> version of phpwebsite, I would suggest you update your IT package to the >> latest version before updating your cvs copy. You can download it here: >> >> HTML_Template_IT: >> http://pear.php.net/package-info.php?pacid=108 >> >> 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:Crypto Challenge is now open! >> Get cracking and register here for some mind boggling fun and >> the chance of winning an Apple iPod: >> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> >> >> > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > 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-03-12 17:17:39
|
Do you guys still provide nightly cvs snapshots of your code? My employer's MIS team fixed a networking issue I was having but in doing so cut off my external CVS access through our firewall. :p Don. On Wed, 12 Mar 2003 ad...@tu... wrote: > > Just so everyone knows, the requirements for phpwebsite are being updated. > Version 1.1 of HTML_Template_IT was released today (woot Pierre!). It > addresses some issues we were having with the template system. I have > updated some core code to stop using our own fixes to these issues and > those changes will get commited sometime today. If you're running a cvs > version of phpwebsite, I would suggest you update your IT package to the > latest version before updating your cvs copy. You can download it here: > > HTML_Template_IT: > http://pear.php.net/package-info.php?pacid=108 > > 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:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |