Menu
▾
▴
phpwebsite-developers
|
From: Shaun M. <sh...@ae...> - 2006-02-17 12:46:09
|
Are we going to do a 0.10.3 release and if so when? If you're following the Changelog, there's been a lot of changes since 0.10.2, mostly added by myself getting as many patches that make sense or are easy enough to add from Sourceforge submissions. Thanks everyone for those. I'd like to get one more change in so that Menu Manager has the same module/page allow system as Block Maker got last week. Should get that in in the next few days. Also, phpwsBB needs a bit more work after the v1.0.4 beta I announced last week and adding that in to a 0.10.3 release would seem like a good idea. That might take a while as I'd like to back port the BBCode parser from fallout into phpwebsite 0.10.3 and ditch the PEAR BBCode class, which has fallen way out of date and contains numerous bugs. If someone else would like to pick up that task, then all the better. The wysiwyg javascript code could do with an update too. Browsers have progressed quite a bit since it was written and IE, Firefox, Safari (which was always the laggard) and Opera all have pretty good javascript and DOM now for better inline editing at the cursor instead of adding to the end of the textarea. Alongside BBCode revisions, it'd be a good update, particularly for the forum mod. I'm no Javascript wizz though. Are there any other patches, bugs or RFEs that either need to go in or that would be great additions? Wendall - phpwsRSSFeeds converting international characters to HTMLEntities/XML is a major one for me and currently the module won't install from a scratch 0.10.2 install because it's installed before Menuman in the install sequence. You have to Boost it afterwards. Changelog - http://res.stddev.appstate.edu/cvs/phpwebsite/docs/CHANGELOG.txt? rev=HEAD&content-type=text/vnd.viewcvs-markup (Everything from 24 October 2005 on is for the next release) Looking ahead, I'm presuming we'll have a 0.10.4 release, but more than likely, that will be more maintenance led as more and more devs move over to Fallout and modules get converted or replaced. I'm sure the two will coexist for some time until it's as painless a process as possible to upgrade. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: Matthew M. <ma...@tu...> - 2006-02-17 13:11:54
|
On Fri, 2006-02-17 at 12:45 +0000, Shaun Murray wrote: > Are we going to do a 0.10.3 release and if so when? Yes we can release 0.10.3 when you are ready. > The wysiwyg javascript code could do with an update too. I agree but someone else will need to code this. I don't want to back port the Fallout system. > Are there any other patches, bugs or RFEs that either need to go in > or that would be great additions? None that I am aware of here at the university. I am very grateful for the work you folks have done tightening up 0.10.x. Since you are steering the ship, just let me or Kevin know when you think an update is ready for release. -- Matthew McNaney Electronic Student Services Appalachian State University http://phpwebsite.appstate.edu |
|
From: Shaun M. <sh...@ae...> - 2006-02-17 13:40:24
|
On 17 Feb 2006, at 13:08, Matthew McNaney wrote: > On Fri, 2006-02-17 at 12:45 +0000, Shaun Murray wrote: >> Are we going to do a 0.10.3 release and if so when? > > Yes we can release 0.10.3 when you are ready. When we're ready it is then. Or more likely, when phpwsBB is ready for me at least. > >> The wysiwyg javascript code could do with an update too. > > I agree but someone else will need to code this. I don't want to back > port the Fallout system. > Nothing that complex. Just fix the cursor positioning so tags get inserted where the cursor is and the page doesn't jump. I think all the current browsers can now support detecting the cursor position in a textarea now. Back porting the BBcode parser into parseInput() parseOutput() I think is moderately important though. phpwsBB, Wiki and maybe some others fall on the basis of bugs in the current implementation. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: Verdon V. <ve...@ve...> - 2006-02-17 13:42:26
|
On 17-Feb-06, at 8:08 AM, Matthew McNaney wrote: > On Fri, 2006-02-17 at 12:45 +0000, Shaun Murray wrote: >> Are there any other patches, bugs or RFEs that either need to go in >> or that would be great additions? > > None that I am aware of here at the university. > There is one that I just discovered recently and haven't put a bug ticket in for yet, as I hadn't had time to decide what recommendation to make... The issue is... When EZform::saveImage() is used in conjunction with PHPWS_File::makeThumbnail() to resize the original image and overwrite it on upload -- as is used in a couple of my modules, as well as my already committed patch to Announcements, and possibly others -- there can be an unexpected result if the image being uploaded has an uppercase extension. This happens because EZform::saveImage() essentially leaves the filename alone while PHPWS_File::makeThumbnail() converts the extension to lowercase. The end result is that 'Image.JPG' gets passed to the image data array that is saved to the db, while the actual final resized image on the server is named 'Image.jpg', leading to problems on a case-sensitive filesystem. My suggestion would be to do something like have EZform::saveImage() convert filenames to lowercase, or some such thing, and I'm willing to do it. I just have been too busy and haven't had much time to do more than a cursory evaluation of the cause/effect. best regards, verdon |
|
From: Shaun M. <sh...@ae...> - 2006-02-17 13:52:20
|
On 17 Feb 2006, at 13:42, Verdon Vaillancourt wrote: > > When EZform::saveImage() is used in conjunction with > PHPWS_File::makeThumbnail() to resize the original image and > overwrite it on upload -- as is used in a couple of my modules, as > well as my already committed patch to Announcements, and possibly > others -- there can be an unexpected result if the image being > uploaded has an uppercase extension. This happens because > EZform::saveImage() essentially leaves the filename alone while > PHPWS_File::makeThumbnail() converts the extension to lowercase. > The end result is that 'Image.JPG' gets passed to the image data > array that is saved to the db, while the actual final resized image > on the server is named 'Image.jpg', leading to problems on a case- > sensitive filesystem. > > My suggestion would be to do something like have EZform::saveImage > () convert filenames to lowercase, or some such thing, and I'm > willing to do it. I just have been too busy and haven't had much > time to do more than a cursory evaluation of the cause/effect. There was a similar issue with photoalbum a while back which would let through filenames with illegal characters for the file system. eg. on a Mac you can pretty much have anything including quotes, international characters and spaces but not so on Linux. I added in a function to convert the filename to a safe filename based on some code from php.net. Maybe have a look at that and see if it could be expanded. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: Verdon V. <ve...@ve...> - 2006-02-17 14:22:38
|
On 17-Feb-06, at 8:52 AM, Shaun Murray wrote: > > On 17 Feb 2006, at 13:42, Verdon Vaillancourt wrote: >> >> When EZform::saveImage() is used in conjunction with >> PHPWS_File::makeThumbnail() to resize the original image and >> overwrite it on upload -- as is used in a couple of my modules, as >> well as my already committed patch to Announcements, and possibly >> others -- there can be an unexpected result if the image being >> uploaded has an uppercase extension. This happens because >> EZform::saveImage() essentially leaves the filename alone while >> PHPWS_File::makeThumbnail() converts the extension to lowercase. The >> end result is that 'Image.JPG' gets passed to the image data array >> that is saved to the db, while the actual final resized image on the >> server is named 'Image.jpg', leading to problems on a case-sensitive >> filesystem. >> >> My suggestion would be to do something like have EZform::saveImage() >> convert filenames to lowercase, or some such thing, and I'm willing >> to do it. I just have been too busy and haven't had much time to do >> more than a cursory evaluation of the cause/effect. > > There was a similar issue with photoalbum a while back which would let > through filenames with illegal characters for the file system. eg. on > a Mac you can pretty much have anything including quotes, > international characters and spaces but not so on Linux. I added in a > function to convert the filename to a safe filename based on some code > from php.net. Maybe have a look at that and see if it could be > expanded. > Ya, I was glancing at that filename to safe bit, and thinking along those lines too. I am mighty busy, so don't wait for me if you want to go, but I will try to have a look at EZform::saveImage() this weekend and see if it can't be tweaked a bit. verdon |
|
From: Verdon V. <ve...@gm...> - 2006-02-17 14:09:07
|
On 17-Feb-06, at 8:52 AM, Shaun Murray wrote: > > On 17 Feb 2006, at 13:42, Verdon Vaillancourt wrote: >> >> When EZform::saveImage() is used in conjunction with >> PHPWS_File::makeThumbnail() to resize the original image and >> overwrite it on upload -- as is used in a couple of my modules, as >> well as my already committed patch to Announcements, and possibly >> others -- there can be an unexpected result if the image being >> uploaded has an uppercase extension. This happens because >> EZform::saveImage() essentially leaves the filename alone while >> PHPWS_File::makeThumbnail() converts the extension to lowercase. The >> end result is that 'Image.JPG' gets passed to the image data array >> that is saved to the db, while the actual final resized image on the >> server is named 'Image.jpg', leading to problems on a case-sensitive >> filesystem. >> >> My suggestion would be to do something like have EZform::saveImage() >> convert filenames to lowercase, or some such thing, and I'm willing >> to do it. I just have been too busy and haven't had much time to do >> more than a cursory evaluation of the cause/effect. > > There was a similar issue with photoalbum a while back which would let > through filenames with illegal characters for the file system. eg. on > a Mac you can pretty much have anything including quotes, > international characters and spaces but not so on Linux. I added in a > function to convert the filename to a safe filename based on some code > from php.net. Maybe have a look at that and see if it could be > expanded. > Ya, I was glancing at that filename to safe bit, and thinking along those lines too. I am mighty busy, so don't wait for me if you want to go, but I will try to have a look at EZform::saveImage() this weekend and see if it can't be tweaked a bit. verdon |
|
From: Greg M. <drk...@co...> - 2006-02-17 14:13:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shaun Murray wrote: > Are we going to do a 0.10.3 release and if so when? > > Are there any other patches, bugs or RFEs that either need to go in or > that would be great additions? I'd like to submit patches for the some of the .txt files before the 0.10.3 release. I'll have them ready over this weekend. I now have an extensive list of FAQ questions http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=User_FAQ . The original INSTALL.txt has morphed into this page http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=PhpWebSite_Installation . Other install areas are covered here too http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=Installation_Guide . Most all of my responses in the forums are here look at this page. It has already been written. I am hoping people might see links in the .txt files and find their answer there--I did say hope. ;-) I haven't decide yet which is easier programming or writing documentation. I find it amazing that after a year's time I am still trying to revise documentation into some cohesive manuscript. Gasp! I haven't really moved on to 1.0.0 pages like I wanted to last November. The wiki has almost hit 150,00 page views at this point http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=Special:Statistics . Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFD9dn/xyxe5L6mr7IRAnTZAJwMjZScn/VBB0hfgKDM3W9srd5VBACdEOLD XW27qYhvVdegfVRWebJskio= =JD1C -----END PGP SIGNATURE----- |
|
From: Verdon V. <ve...@ve...> - 2006-02-17 14:22:47
|
On 17-Feb-06, at 9:13 AM, Greg Morgan wrote: > I haven't decide yet which is easier programming or writing > documentation. ... LOL. Programming for sure :) I've got a friend who makes a very good living writing software manuals. I wouldn't want his job for the world! |
|
From: Shaun M. <sh...@ae...> - 2006-02-17 14:31:05
|
On 17 Feb 2006, at 14:13, Greg Morgan wrote: > The wiki has almost hit 150,00 page views at this point > http://phpwebsite-comm.sourceforge.net/wiki/index.php? > title=Special:Statistics How about we link to the wiki in the text you get on the main page of a new installation? I almost always tell people where to go (ahem) after I've done an install for them. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: Greg M. <drk...@co...> - 2006-02-17 21:28:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shaun Murray wrote: > > On 17 Feb 2006, at 14:13, Greg Morgan wrote: > >> The wiki has almost hit 150,00 page views at this point >> http://phpwebsite-comm.sourceforge.net/wiki/index.php? >> title=Special:Statistics > > > How about we link to the wiki in the text you get on the main page of a > new installation? I almost always tell people where to go (ahem) after > I've done an install for them. Well that sounds good too. But wouldn't the Default theme have to be modified to display the link? In a core only installation all that you have on the front page is the copyright at the bottom of the Default theme or are you thinking of another place to put a link? I thought I'd test what is in CVS. Are the files tagged for the next release yet? Are there any plans to run a few release candidates, etc? I would be happy to run some tests on php5 and provide any feedback if that would help? Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFD9j/ixyxe5L6mr7IRAtieAJ4nH4PUQKK7iEwp34UnPV212reaJQCfaZHa V9U8/TKbHyvQ/JgWaN/vsX4= =PclN -----END PGP SIGNATURE----- |
|
From: Shaun M. <sh...@ae...> - 2006-02-18 01:59:26
|
On 17 Feb 2006, at 21:28, Greg Morgan wrote: > Shaun Murray wrote: >> >> On 17 Feb 2006, at 14:13, Greg Morgan wrote: >> >>> The wiki has almost hit 150,00 page views at this point >>> http://phpwebsite-comm.sourceforge.net/wiki/index.php? >>> title=Special:Statistics >> >> >> How about we link to the wiki in the text you get on the main page >> of a >> new installation? I almost always tell people where to go (ahem) >> after >> I've done an install for them. > > Well that sounds good too. But wouldn't the Default theme have to be > modified to display the link? In a core only installation all that > you > have on the front page is the copyright at the bottom of the Default > theme or are you thinking of another place to put a link? > No. Put it in the pagemaster install sql where we've got a link to the phpwebsite-comm already for themes. > I thought I'd test what is in CVS. Are the files tagged for the next > release yet? Are there any plans to run a few release candidates, > etc? > I would be happy to run some tests on php5 and provide any > feedback if > that would help? > Not yet, probably and yes it would although I think we're still at a php5 impasse with PEAR. Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: Greg M. <drk...@co...> - 2006-02-18 07:34:25
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shaun Murray wrote: >> I thought I'd test what is in CVS. Are the files tagged for the next >> release yet? Are there any plans to run a few release candidates, etc? >> I would be happy to run some tests on php5 and provide any feedback if >> that would help? >> > > Not yet, probably and yes it would although I think we're still at a > php5 impasse with PEAR. Here's two forum posts that just came in: I believe this one is a php 5 issue on MS Windows with all the modules installed https://sourceforge.net/forum/message.php?msg_id=3582968 . I can get 10.2 to install on 5 if I don't boost calendar. This guy left phpinfo.php available. I have not had time to try and investigate this error "Fatal error: Call to a member function on a non-object" https://sourceforge.net/forum/message.php?msg_id=3582482 . I used to think that this was a php 5 issue too but his web hosting company is running php 4.4.2 http://jonathanhall205.co.uk/PHPSITE/setup/phpinfo.php . It appears more users are running into this version of php and there's some problem with the current version of phpWebSite. Do you know if this kind-of error has been addressed. I asked Jon to provide more info on how he installed phpWebSite in this environment. Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFD9s36xyxe5L6mr7IRAv3aAKCGNGu2BwSlSGbu2TGE+uVyh7kQIgCfciMj m15Rqzdb+1TOLSMpoT0cDeM= =Cfue -----END PGP SIGNATURE----- |
|
From: Shaun M. <sh...@ae...> - 2006-02-18 13:25:41
|
On 18 Feb 2006, at 07:34, Greg Morgan wrote: > This guy left phpinfo.php available. I have not had time to try and > investigate this error "Fatal error: Call to a member function on a > non-object" https://sourceforge.net/forum/message.php?msg_id=3582482 . > I used to think that this was a php 5 issue too but his web hosting > company is running php 4.4.2 > http://jonathanhall205.co.uk/PHPSITE/setup/phpinfo.php . It appears > more users are running into this version of php and there's some > problem > with the current version of phpWebSite. Do you know if this kind-of > error has been addressed. I asked Jon to provide more info on how he > installed phpWebSite in this environment. PHP 4.4 introduced a bunch of errors you'd normally only get in PHP5 which is why I've stuck with PHP 4.3.11 on my servers. 4.4 breaks too many 3rd party scripts. We'll have to get that working though. Anyone running the latest v4.4 want to step forward for testing purposes? Shaun aegis design - http://www.aegisdesign.co.uk aegis hosting - http://www.aegishosting.co.uk |
|
From: Verdon V. <ve...@gm...> - 2006-02-17 14:19:20
|
On 17-Feb-06, at 9:13 AM, Greg Morgan wrote: > I haven't decide yet which is easier programming or writing > documentation. ... LOL. Programming for sure :) I've got a friend who makes a very good living writing software manuals. I wouldn't want his job for the world! |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X