Hi Karl, you don't need to register any additional namespace. I already implemented all you need to access <content:encoded> text as ZF-2140 <http://framework.zend.com/issues/browse/ZF-2140> describes. The final result is exactly what you would expect, as this test file describes http://framework.zend.com/fisheye/browse/Zend_Framework/trunk/tests/Zend/Feed/Entry/RssTest.php?r=8659
You can call $item->content() to get the content of the <content:encoded> tag. Simone On Tue, Apr 1, 2008 at 3:57 PM, Karl Katzke <[EMAIL PROTECTED]> wrote: > Hi, Simone. > > The problem is that $item->content doesn't appear. Upon further reading, > it seems that Content is a namespace, and Encoded is the actual attribute. > There's a line at the start of my RSS feed that says > > <rss version="2.0" > xmlns:content="http://purl.org/rss/1.0/modules/content/" > > > Now, I'm new to this RSS feed stuff. Would I just need to use the > Zend_Feed::registerNamespace function? > > Thanks, > Karl Katzke > > > On Tue, Apr 1, 2008 at 4:33 AM, Simone Carletti <[EMAIL PROTECTED]> wrote: > > > Hi Karl, > > > > as stated in the coding standard, the right version is saveXml and > > getDOM. > > I'm going to open a ticket for this issue. > > > > About the second question, you have access to a <content:encoded> > > element via *content* statement. > > > > $item->content (attribute-style) > > > > or > > > > $item->content() (method-style) > > > > > > Simone > > > > > > On Tue, Apr 1, 2008 at 1:24 AM, Karl Katzke <[EMAIL PROTECTED]> wrote: > > > > > Zend_Feed is a giant leap forward in feed parsing. It's made what I'm > > > working on now -easy-. > > > > > > That being said, I've got two quibbles. Minor one first. > > > > > > Function capitalization: In Zend_Feed_Element, there's getDOM() and > > > saveXml(). Guys, do me a favor and pick ONE capitalization standard and > > > stick with it... > > > > > > Second quibble: I can't find any support, except for going all the way > > > down to the DOMElement, for accessing an element with a name like > > > "<content:encoded>". This is the way my Wordpress blog passes the full > > > content in RSS. ( http://www.karlkatzke.com/feed ) Is there something > > > I'm just not missing because we don't have great tools for introspection > > > into what, exactly, these darned classes contain? (Or, could someone > > > suggest > > > a better way for me to see what-all a Feed_Element actually contains?) > > > > > > Thanks, > > > Karl Katzke > > > > > > > >
