-
Notifications
You must be signed in to change notification settings - Fork 42
Methods of CoreExtensions expected in own writer extension #87
Comments
I think that's the same problem as deregistering an extension. |
Please look at #90 and my idea for an improvement. I think this should help also for you problem – remove core extension and add a custom extension. |
Thank's for the info. Fortunately I kept an old branch with my attempts. I modified the code: /** @var \Zend\Feed\Writer\StandaloneExtensionManager $em */
$em = \Zend\Feed\Writer\Writer::getExtensionManager();
$em->remove('ITunes\Renderer\Feed');
$em->remove('GooglePlayPodcast\Renderer\Feed');
$em->add(
'Webfeed\Renderer\Feed',
\Webfeed\Writer\Renderer\Feed::class
);
Writer::setExtensionManager($em);
Writer::registerExtension('Webfeed'); With the removal of |
@av3 |
This repository has been closed and moved to laminas/laminas-feed; a new issue has been opened at laminas/laminas-feed#5. |
Thank you for your writer example, froschdesign. I tested it and am getting an error message. This time I created a separate issue, because it's not related to the documentation ;)
I created an Entry class (
extends Extension\AbstractRenderer
) and registered it in my handler. But the output of my atom feed fails (using the export method). I get the error message:call_user_func_array() expects parameter 1 to be a valid callback, class 'Webfeed\Writer\Renderer\Entry' does not have a method 'getItunesAuthors'
I can see that
$authors = $this->getDataContainer()->getItunesAuthors();
ofWriter/Extension/ITunes/Renderer/Entry.php
is executed, before it fails. Why should my own Renderer need getItunesAuthors?I assume on reason is that
registerCoreExtensions()
is called in the AbstractFeed constructor. Unfortunately I can't see a method to unregister the extension. When removing iTunes in the registerCoreExtensions method, the methodgetPlayPodcastBlock
is expected. It would work if I remove everything except Atom.Is this an unexpected behavior or am I doing something wrong?
The text was updated successfully, but these errors were encountered: