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: Verdon V. <ve...@gm...> - 2007-09-09 19:19:41
|
I've got something wierd going on. Actually, I just checked and the editor was set to fckeditor on the new install, and I got the small text areas, no editor, no warnings. When I actually went to my page and changed the editor pref to none, the text areas are OK. Simple editor gives me large text areas that scale to my window size. tinymce doesn't seem to be working though the text areas are fine (always has in the past but is a little flaky). YUI seems OK at a glance. On 9-Sep-07, at 2:39 PM, Shaun Murray wrote: > > On 9 Sep 2007, at 14:45, Verdon Vaillancourt wrote: >> >> One problem I have observed (I'm using Safari 2.0.4 on MacOS 10.4.10 >> - all current) is something that had been fixed in the past and has >> seemed to have creeped back in. That is when using no editor (which >> is what it defaulted to) the text area fields in some mods are so >> small as to be near unusable, roughly 20 cols x 2 rows. This is >> happening in blog, webpages, calander create schedule and add event. >> Filecabinet and signup seem to be OK. >> > > A better default for Safari 2.x would probably be the Simple WYSIWYG > editor than nothing. > > > Shaun > aegis design - http://www.aegisdesign.co.uk > aegis hosting - http://www.aegishosting.co.uk > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: Shaun M. <sh...@ae...> - 2007-09-09 18:39:47
|
On 9 Sep 2007, at 14:45, Verdon Vaillancourt wrote: > > One problem I have observed (I'm using Safari 2.0.4 on MacOS 10.4.10 > - all current) is something that had been fixed in the past and has > seemed to have creeped back in. That is when using no editor (which > is what it defaulted to) the text area fields in some mods are so > small as to be near unusable, roughly 20 cols x 2 rows. This is > happening in blog, webpages, calander create schedule and add event. > Filecabinet and signup seem to be OK. > A better default for Safari 2.x would probably be the Simple WYSIWYG editor than nothing. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: Verdon V. <ve...@gm...> - 2007-09-09 13:46:24
|
Hi Matt, I've only had a chance for a quick look so far. I didn't have anything I wanted to try an upgrade on, but I did a new install. Everything boosted OK. I've installed a number of mods and have done a quick bit of poking around. If I get a chance later this afternoon, I'll do some more. One problem I have observed (I'm using Safari 2.0.4 on MacOS 10.4.10 - all current) is something that had been fixed in the past and has seemed to have creeped back in. That is when using no editor (which is what it defaulted to) the text area fields in some mods are so small as to be near unusable, roughly 20 cols x 2 rows. This is happening in blog, webpages, calander create schedule and add event. Filecabinet and signup seem to be OK. I'll let you know if I get a chance to look further, later in the day... chores are calling :) rgds, verdon On 7-Sep-07, at 2:24 PM, matt wrote: > The following modules are getting new packages: > > Blog > Boost > Branch > Calendar > Categories > Control Panel > Core > File Cabinet > Layout > Menu > MiniAdmin > Page Smith > Related > RSS > Search > Signup > Users > Web Pages > > Some updates are very minor. Some (Core, Blog) have major > improvements. > Because there are so many changes, I will create a 1.3.1 distro soon. > > If you have time this weekend, please test a subversion export. > > Thanks, > Matt > > -- > Matthew McNaney > Electronic Student Services > Appalachian State University > Ext. 6493 > http://ess.appstate.edu > http://phpwebsite.appstate.edu > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: matt <ma...@tu...> - 2007-09-07 18:30:28
|
The following modules are getting new packages: Blog Boost Branch Calendar Categories Control Panel Core File Cabinet Layout Menu MiniAdmin Page Smith Related RSS Search Signup Users Web Pages Some updates are very minor. Some (Core, Blog) have major improvements. Because there are so many changes, I will create a 1.3.1 distro soon. If you have time this weekend, please test a subversion export. Thanks, Matt -- Matthew McNaney Electronic Student Services Appalachian State University Ext. 6493 http://ess.appstate.edu http://phpwebsite.appstate.edu |
|
From: Shaun M. <sh...@ae...> - 2007-09-01 09:37:45
|
On 31 Aug 2007, at 22:11, Verdon Vaillancourt wrote: > > I know the current svn version of phpws is compliant, but > unfortunately, the majority of these sites have too many > customizations, in some cases even to core, in others, here there and > everywhere in various mods like users and pagemaster and so on, to > make a full upgrade in that manner. If I have to, I will, but it > would be very, very painful ;-) > If they're useful generally we could always stick your mods into 0.11. > Is there any wisdom out there, as to what the bare minimum changes > required to get a 0.10.1 or 0.10.2 site php5 ready? Is it really that > many changes, or just a few scattered around? > There's actually very few changes needed for php5. Most of the problems are fixed by simply taking the core Item, Manager and List classes from 0.11 svn. I think that's all that will change in 0.11's core of importance. I back ported the core/Text.php parseOutput() changes from 1.x into 0.x a while back but wasn't happy with the speed of it despite the added functionality so I went looking for another parser. The PEAR BBCode parser subsequently has been picked up by someone else again and I've got that to try out. There's a new ImgLibrary too but that only affects phpwsBB and possibly Article though it's just bug fixes. Any mod that uses get_class() may have the same issues as the core Item/Manager/List classes. Just convert the returned data to lowercase before comparing. Apart from that there was probably a few $this reassigns but I think those were sorted in 0.10.2 anyway. At the back of my back burner there was a list of other changes I was trying to get in for 0.11 but "great artists ship" at some point. I'd really love to hammer the cross session contamination issues in announce, comment and pagemaster that I know of too. The other thing that would be useful from the University is to fix the daily build script which hasn't worked since December when we moved from CVS to SVN I think. I'm also wondering about MySQL 5.0 and 5.1 compatibility, particularly on Windows. IIRC the Language module with it's _EN suffix on the English language table causes issues on some file systems and versions of MySQL. > > ps. And I don't even want to talk about the dozen or so phpws 8.x > sites on the server. Those cheapos are going to have to cough up or > go somewhere else ;-) I've got one site on 0.8x still. It seems to run fine on php5 as long as you leave globals on for it. I've left them on 0.8x mostly because I stripped down the control panel in that to about four items. 0.10.x and 1.x would instantly confuse them. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: <ma...@tu...> - 2007-09-01 01:33:38
|
Hey Verdon, > Is there any wisdom out there, as to what the bare minimum changes > required to get a 0.10.1 or 0.10.2 site php5 ready? Is it really that > many changes, or just a few scattered around? As far as I know, 0.11.0 is ready for php 5. Personally the only module I have tinkered with is Calendar and I'm pretty sure it is ready for 5 as well. You may want to just run one site under 0.11.0 for a week and see if anything pops up. I can probably help you with anything that pops up. Matt |
|
From: Verdon V. <ve...@gm...> - 2007-08-31 21:17:03
|
Doh! I should have been clearer, I'm talking about the svn phpws 0.11.x. I have no intention of moving these sites to phpws 1.x, though my new stuff is using that. I just want the bare minimum to get my older 0.10.x sites php5 ready. On 31-Aug-07, at 5:11 PM, Verdon Vaillancourt wrote: > I know the current svn version of phpws is compliant, but > unfortunately, the majority of these sites have too many > customizations, in some cases even to core, in others, here there and > everywhere in various mods like users and pagemaster and so on, to > make a full upgrade in that manner. If I have to, I will, but it > would be very, very painful ;-) |
|
From: Verdon V. <ve...@gm...> - 2007-08-31 21:11:32
|
Hi all, I have large number of phpws sites, many/most heavily customized, in various 0.10.x flavours. I may even have a couple of 0.9.x versions, but I think I have all of them up to 0.10.x. I want to start strategizing for getting php5 ready. I know the current svn version of phpws is compliant, but unfortunately, the majority of these sites have too many customizations, in some cases even to core, in others, here there and everywhere in various mods like users and pagemaster and so on, to make a full upgrade in that manner. If I have to, I will, but it would be very, very painful ;-) Is there any wisdom out there, as to what the bare minimum changes required to get a 0.10.1 or 0.10.2 site php5 ready? Is it really that many changes, or just a few scattered around? Thanks for any advice, verdon ps. And I don't even want to talk about the dozen or so phpws 8.x sites on the server. Those cheapos are going to have to cough up or go somewhere else ;-) |
|
From: Verdon V. <ve...@ve...> - 2007-08-22 13:48:31
|
I pretty much echo what Shaun says. My main server will be php4 for a while yet, but I'm not waiting til next August to migrate to php 5. It will be gradual this winter. I have a lot more 0.10.x sites to contend with (mostly heavily customized) and even a few 0.8.x sites. I may keep a php4 server up for a little while longer, for a few clients who refuse to upgrade and realize they will be moved to an unsupported obsolete server. verdon On 22-Aug-07, at 9:32 AM, Shaun Murray wrote: > From a commercial standpoint as a hosting company, I don't see how > I'll be supporting PHP4 much past the end of the year when main > development ends and as such I've been asking some of my larger > customers to make sure their applications are ready for PHP5. I've a > spare testing server now and I've been gradually moving people. > > I'd think that most hosting companies would be of a similar thinking > rather than waiting for next August when security fixes stop. > > I've maybe a dozen sites on phpWebSite 0.10.2 still which I'm > gradually moving on to 0.11 (which is php5 compatible as far as my > testing has gone). Most rely on phpWebSite 0.x features and modules > so they aren't moving to 1.x. I should really pick up development > pace on that but other projects are taking precedence. > > I think it would be safe to make phpWebSite 1.x PHP5 only personally > and I'd imagine the cleaner object model would make developing for it > a lot easier. Recently I was looking through other php frameworks > (CodeIgniter, Zend and Symfony) and came to the conclusion that php4 > support just wasn't worth it. I ended up with Symfony btw for that > project. http://www.symfony-project.com > > > > > > On 22 Aug 2007, at 13:57, matt wrote: > >> PHP.net has announced the end of support for PHP 4. >> >> http://www.php.net/ >> >> We are unable to fully commit to PHP 5 at the university. I am >> wondering >> however how the community feels about discontinuing support for PHP >> 4 in >> phpWebSite 1.x. This would not happen anytime soon but I believe we >> should consider a timeline. >> >> What do you think? >> >> Matt >> >> -- >> Matthew McNaney >> Electronic Student Services >> Appalachian State University >> Ext. 6493 >> http://ess.appstate.edu >> http://phpwebsite.appstate.edu >> >> >> --------------------------------------------------------------------- >> - >> --- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a >> browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > Shaun > aegis design - http://www.aegisdesign.co.uk > aegis hosting - http://www.aegishosting.co.uk > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: Shaun M. <sh...@ae...> - 2007-08-22 13:32:24
|
From a commercial standpoint as a hosting company, I don't see how I'll be supporting PHP4 much past the end of the year when main development ends and as such I've been asking some of my larger customers to make sure their applications are ready for PHP5. I've a spare testing server now and I've been gradually moving people. I'd think that most hosting companies would be of a similar thinking rather than waiting for next August when security fixes stop. I've maybe a dozen sites on phpWebSite 0.10.2 still which I'm gradually moving on to 0.11 (which is php5 compatible as far as my testing has gone). Most rely on phpWebSite 0.x features and modules so they aren't moving to 1.x. I should really pick up development pace on that but other projects are taking precedence. I think it would be safe to make phpWebSite 1.x PHP5 only personally and I'd imagine the cleaner object model would make developing for it a lot easier. Recently I was looking through other php frameworks (CodeIgniter, Zend and Symfony) and came to the conclusion that php4 support just wasn't worth it. I ended up with Symfony btw for that project. http://www.symfony-project.com On 22 Aug 2007, at 13:57, matt wrote: > PHP.net has announced the end of support for PHP 4. > > http://www.php.net/ > > We are unable to fully commit to PHP 5 at the university. I am > wondering > however how the community feels about discontinuing support for PHP > 4 in > phpWebSite 1.x. This would not happen anytime soon but I believe we > should consider a timeline. > > What do you think? > > Matt > > -- > Matthew McNaney > Electronic Student Services > Appalachian State University > Ext. 6493 > http://ess.appstate.edu > http://phpwebsite.appstate.edu > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: matt <ma...@tu...> - 2007-08-22 12:59:15
|
PHP.net has announced the end of support for PHP 4. http://www.php.net/ We are unable to fully commit to PHP 5 at the university. I am wondering however how the community feels about discontinuing support for PHP 4 in phpWebSite 1.x. This would not happen anytime soon but I believe we should consider a timeline. What do you think? Matt -- Matthew McNaney Electronic Student Services Appalachian State University Ext. 6493 http://ess.appstate.edu http://phpwebsite.appstate.edu |
|
From: Brian W. B. <br...@ap...> - 2007-08-17 17:50:12
|
Shaun, > Came across another wysiwyg editor today from Yahoo! > > http://developer.yahoo.com/yui/editor/ Looks nice! Thanks for sharing this. Kind Regards, Brian -- Brian W. Brown Director, Electronic Student Services Room 269, John Thomas Hall Appalachian State University Boone, NC 28608 Office: 828-262-7124 http://ess.appstate.edu/ http://phpwebsite.appstate.edu/ |
|
From: Shaun M. <sh...@ae...> - 2007-08-17 17:30:34
|
Came across another wysiwyg editor today from Yahoo! http://developer.yahoo.com/yui/editor/ They're actively supporting Safari too, which is more than can be said for some of the other 'cross platform' editors. It's got a nice image editor built in. BSD licence as part of the YUI toolkit. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: <ma...@tu...> - 2007-08-10 18:41:15
|
Whew :) Thanks for bringing it up. I changed the code pretty close to release so it would have been easy to miss. > Awesome. Thanks Matt... That did the job! > > verdon > > On 10-Aug-07, at 1:43 PM, ma...@tu... wrote: > >> An oversight. I left a $this in a static function and it is picking >> up the >> form object. >> >> Please download the subversion copy of Text.php and see if that >> fixes it. >> >> Matt >> >>> Hi, >>> >>> I updated 4 sites to 1.3 yesterday. The first went well and so I >>> updated the rest with a little less testing, and discover now that 3 >>> of the 4 are actually having errors in any/all edit screens. >>> >>> The error is 'PHP Fatal error: Call to undefined method: >>> form_textarea->decode_entities() in /home/user/public_html/core/ >>> class/ >>> Text.php on line 54' >>> >>> The error is produced as soon as an edit screen is requested. All 4 >>> sites were updated from 1.2. One site works fine, the other three >>> error. I can't think of any differences in the sites that would >>> account for this. >>> >>> Apache 1.3 >>> PHP Version 4.4.7 >>> MySQL 4.1.22 >>> >>> I'm not sure where to start looking. Any ideas? >>> >>> Thanks, >>> verdon >>> >>> >>> --------------------------------------------------------------------- >>> ---- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a >>> browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> Phpwebsite-developers mailing list >>> Php...@li... >>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >>> >> >> >> ---------------------------------------------------------------------- >> --- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a >> browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
|
From: Verdon V. <ve...@gm...> - 2007-08-10 18:20:21
|
Awesome. Thanks Matt... That did the job! verdon On 10-Aug-07, at 1:43 PM, ma...@tu... wrote: > An oversight. I left a $this in a static function and it is picking > up the > form object. > > Please download the subversion copy of Text.php and see if that > fixes it. > > Matt > >> Hi, >> >> I updated 4 sites to 1.3 yesterday. The first went well and so I >> updated the rest with a little less testing, and discover now that 3 >> of the 4 are actually having errors in any/all edit screens. >> >> The error is 'PHP Fatal error: Call to undefined method: >> form_textarea->decode_entities() in /home/user/public_html/core/ >> class/ >> Text.php on line 54' >> >> The error is produced as soon as an edit screen is requested. All 4 >> sites were updated from 1.2. One site works fine, the other three >> error. I can't think of any differences in the sites that would >> account for this. >> >> Apache 1.3 >> PHP Version 4.4.7 >> MySQL 4.1.22 >> >> I'm not sure where to start looking. Any ideas? >> >> Thanks, >> verdon >> >> >> --------------------------------------------------------------------- >> ---- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a >> browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: <ma...@tu...> - 2007-08-10 17:50:15
|
An oversight. I left a $this in a static function and it is picking up the form object. Please download the subversion copy of Text.php and see if that fixes it. Matt > Hi, > > I updated 4 sites to 1.3 yesterday. The first went well and so I > updated the rest with a little less testing, and discover now that 3 > of the 4 are actually having errors in any/all edit screens. > > The error is 'PHP Fatal error: Call to undefined method: > form_textarea->decode_entities() in /home/user/public_html/core/class/ > Text.php on line 54' > > The error is produced as soon as an edit screen is requested. All 4 > sites were updated from 1.2. One site works fine, the other three > error. I can't think of any differences in the sites that would > account for this. > > Apache 1.3 > PHP Version 4.4.7 > MySQL 4.1.22 > > I'm not sure where to start looking. Any ideas? > > Thanks, > verdon > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
|
From: Verdon V. <ve...@gm...> - 2007-08-10 12:58:09
|
Hi, I updated 4 sites to 1.3 yesterday. The first went well and so I updated the rest with a little less testing, and discover now that 3 of the 4 are actually having errors in any/all edit screens. The error is 'PHP Fatal error: Call to undefined method: form_textarea->decode_entities() in /home/user/public_html/core/class/ Text.php on line 54' The error is produced as soon as an edit screen is requested. All 4 sites were updated from 1.2. One site works fine, the other three error. I can't think of any differences in the sites that would account for this. Apache 1.3 PHP Version 4.4.7 MySQL 4.1.22 I'm not sure where to start looking. Any ideas? Thanks, verdon |
|
From: Verdon V. <ve...@ve...> - 2007-08-08 14:17:11
|
Hi Matt, Sorry I haven't been able to make time to test this RC, but I did want to tell you that I appreciate the information and updates. Very best regards, verdon On 8-Aug-07, at 9:52 AM, matt wrote: > Hello, > > Closing in on a 1.3 stable release. Stuff keeps popping up to fix. |
|
From: matt <ma...@tu...> - 2007-08-08 14:00:23
|
Hello, Closing in on a 1.3 stable release. Stuff keeps popping up to fix. A recent post complained of a problem with text parsing. They had a link that looked like so: <a href="mailto:ollie">Ollie</a> The problem is that smilies are getting created inside tags. The ":o" portion looks like the surprise smilie and it messed up the link. While starting the fix I noticed that Text still had the $use_smilies parameter. Since the bb filtering has been moved outside the class, I removed it. After doing this I came to a few decisions. Since bb encoding is such a small portion of the site, parseOutput will NOT observe text filters by default. Most admins are using the wysiwyg tools anyway. You can enable filtering by calling parseOutput with the third parameter as true. This used to be the aforementioned smilie parameter, so Comments still works fine. My other decision is to include the pear bb filter Shaun mentioned the other day. The default filter is still bb but I added a commented line above it to enable pear instead. Thanks, Matt -- Matthew McNaney Electronic Student Services Appalachian State University Ext. 6493 http://ess.appstate.edu http://phpwebsite.appstate.edu |
|
From: matt <ma...@tu...> - 2007-08-01 18:05:23
|
Let me know how it goes. Since the text filters are modular, we can at least make it a choice. Matt Shaun Murray wrote: > Just spotted that http://pear.php.net/package/HTML_BBCodeParser/ has > finally been picked up and is receiving some love. > > I've been using a port of the 1.x code in 0.11's core/Text.php but I > may just give the PEAR package another go. Anyone else tried? > > Shaun > aegis design - http://www.aegisdesign.co.uk > aegis hosting - http://www.aegishosting.co.uk > -- Matthew McNaney Electronic Student Services Appalachian State University Ext. 6493 http://ess.appstate.edu http://phpwebsite.appstate.edu |
|
From: Shaun M. <sh...@ae...> - 2007-08-01 13:15:19
|
Just spotted that http://pear.php.net/package/HTML_BBCodeParser/ has finally been picked up and is receiving some love. I've been using a port of the 1.x code in 0.11's core/Text.php but I may just give the PEAR package another go. Anyone else tried? Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: matt <ma...@tu...> - 2007-07-26 14:44:18
|
Good day, There are some problems with File Cabinet. The update wasn't creating directories properly. It also had some problems with its multimedia table creation. I should have a new release later today. Thanks, Matt -- Matthew McNaney Electronic Student Services Appalachian State University Ext. 6493 http://ess.appstate.edu http://phpwebsite.appstate.edu |
|
From: <ma...@tu...> - 2007-07-25 23:50:12
|
1.2.0 first. I have carved big chunks out of the upgrade scripts because they were in such flux. If it is a problem, I can restore the old updates from 1.1.0 on. Matt > Matt, > When upgrading to 1.3.0, can we upgrade from 1.1.0 or do we need to > upgrade to 1.2.0 first? I admit I've fallen a bit behind lately. > > Thanks, > Greg > > On 7/25/07, matt <ma...@tu...> wrote: >> Ok folks here it is: >> >> http://phpwebsite.appstate.edu/downloads/rc/phpwebsite_1_3_0_RC1.tar.gz >> >> I am going to begin testing on it. This a direct subversion export so >> you can go that route instead. >> >> Please email me with your findings or drop by the IRC channel. >> >> Thanks, >> Matt >> >> -- >> Matthew McNaney >> Electronic Student Services >> Appalachian State University >> Ext. 6493 >> http://ess.appstate.edu >> http://phpwebsite.appstate.edu >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
|
From: Gregory M. <gre...@gm...> - 2007-07-25 21:04:50
|
Matt, When upgrading to 1.3.0, can we upgrade from 1.1.0 or do we need to upgrade to 1.2.0 first? I admit I've fallen a bit behind lately. Thanks, Greg On 7/25/07, matt <ma...@tu...> wrote: > Ok folks here it is: > > http://phpwebsite.appstate.edu/downloads/rc/phpwebsite_1_3_0_RC1.tar.gz > > I am going to begin testing on it. This a direct subversion export so > you can go that route instead. > > Please email me with your findings or drop by the IRC channel. > > Thanks, > Matt > > -- > Matthew McNaney > Electronic Student Services > Appalachian State University > Ext. 6493 > http://ess.appstate.edu > http://phpwebsite.appstate.edu > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
|
From: matt <ma...@tu...> - 2007-07-25 19:54:35
|
Ok folks here it is: http://phpwebsite.appstate.edu/downloads/rc/phpwebsite_1_3_0_RC1.tar.gz I am going to begin testing on it. This a direct subversion export so you can go that route instead. Please email me with your findings or drop by the IRC channel. Thanks, Matt -- Matthew McNaney Electronic Student Services Appalachian State University Ext. 6493 http://ess.appstate.edu http://phpwebsite.appstate.edu |
5 messages has been excluded from this view by a project administrator.
