Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.15
Bug #17744 Empty changelog causes fatal error in setChangelogentry
Submitted: 2010-08-19 04:42 UTC
From: doconnor Assigned: dufuz
Status: Closed Package: PEAR
PHP Version: 5.2.12 OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 35 - 3 = ?

 
 [2010-08-19 04:42 UTC] doconnor (Daniel O'Connor)
Description: ------------ Fatal error: Cannot use string offset as an array in C:\php\PEAR\PEAR\PackageFil e\v2\rw.php on line 1575 Test script: --------------- See PFM_cli on Bug #17741 http://svn.php.net/viewvc/pear/packages/Net_Socket/trunk/package.xml?view=co&revision=284180&content-type=text%2Fplain is the particular badly formed package.xml

Comments

 [2010-08-19 04:47 UTC] doconnor (Daniel O'Connor)
Looks like the way PEAR_PackageFile_v2_rw::setChangelogEntry() is invoked, vs the state of $this->_packageInfo['changelog']['release'][0] Given a node of: "<changelog />" It gets parsed into a blank string, rather than an array()
 [2011-03-10 06:45 UTC] dufuz (Helgi Þormar Þorbjörnsson)
-Package: PEAR_PackageFileManager +Package: PEAR -Assigned To: +Assigned To: dufuz
Moving to PEAR it self; Question is if we make the XSD enforce this more, e.g. no empty changelog like that or if we just try to deal with it internally. The XML Parser is parsing properly as <changelog /> is just an empty string (e.g. <changelog></changelog>)
 [2011-03-20 08:59 UTC] dufuz (Helgi Þormar Þorbjörnsson)
-Summary: Fatal error: Cannot use string offset as an array in C:\php\PEAR\PEAR\PackageFi +Summary: Empty changelog causes fatal error in setChangelogentry -Status: Assigned +Status: Closed
This bug has been fixed in SVN. 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.