Bug #4339 [Asn->Csd]: Broken HTML in PEPr proposals

From: Date: Fri, 09 Sep 2005 14:33:15 +0000
Subject: Bug #4339 [Asn->Csd]: Broken HTML in PEPr proposals
References: 1  Groups: php.pear.webmaster 
Request: Send a blank email to pear-webmaster+get-4396@lists.php.net to get a copy of this message
Edit report at http://pear.php.net/bugs/bug.php?id=4339&edit=1 ID: 4339 Updated by: pierre.php@gmail.com Reported By: daniel dot oconnor at gmail dot com -Status: Assigned +Status: Closed Id: 4339 Type: Bug Package: Web Site PHP Version: Irrelevant Assigned To: dufuz New Comment: This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. was a wrong nl2br. Previous Comments: ------------------------------------------------------------------------ [2005-05-13 23:21:20] helgi at trance dot is Ok great, I'll look into this, iirc it does a silly thing like: bbcodeparser(nl2br(htmlentities())) or something, which probably is breaking it I guess. it's tho not a very pressing matter for me since text_wiki makes the problem go away ;-) Maybe I'll also just wait until text_wiki supports BBCode and fade BBCodeParser code from the site, but thanks for the notice and input, I'll for sure use the test data you gave me when I'll have a look at this. ------------------------------------------------------------------------ [2005-05-13 22:04:44] daniel dot oconnor at gmail dot com Ooops. Default, BBCode. Switching to Wiki makes the problem go away. ------------------------------------------------------------------------ [2005-05-13 21:21:46] helgi at trance dot is Actually I was asking what your proposal is congfigured to use, even tho you don't use any in the proposal it self, because proposals are always outputted in BBCode parser way or Text_Wiki, it's up 2 the propser to pick which way. Because of that I need to know which one your proposal is configured to so I can pinpoint the problem, tho I think it's the BBCode parser. ------------------------------------------------------------------------ [2005-05-13 20:14:52] daniel dot oconnor at gmail dot com No BBCode/special formating at all. Unformatted text: "Upcoming.org is a social event calendar, completely driven by people like you. Manage your events, share events with friends and family, and syndicate your calendar to your own site." Services_Upcoming is a package designed to operate with the existing web services present on Upcoming.org, to create, search through, and manipulate events. Currently, it fully supports all exposed web service functionality. Minor issues with documentation, error handling and installation exist, and unit tests need to be done. See: http://clockwerx.blogspot.com/2005/04/upcomingorg-web-services-client-for.html Currently under the GPL, but I can relicence it. Other issues: Upcoming.org is going to be doing a lot of things to their API, so this package might not be considered "stable" for some time. ------------------------------------------------------------------------ [2005-05-13 08:02:41] helgi at trance dot is Are you using Text_Wiki or BBCode format in the proposal ? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://pear.php.net/bugs/bug.php?id=4339 -- Edit this bug report at http://pear.php.net/bugs/bug.php?id=4339&edit=1

« previous php.pear.webmaster (#4396) next »