collective.portlet.feedmixer 1.2dev-r68204

Installing without buildout

First install feedparser. You can install this in either the system python path or in the lib/python directory of your Zope instance. If you have setuptools installed you can do this using easy_install:

easy_install FeedParser

If you do not have setuptools you can install it manually using the setup.py script in the feedparser source. If you want to install feedparser inside your Zope instance instead of system wide you can its ‘’–prefix=’’ option to install in the ‘’lib/python’’ directory of your Zope instance.

Next you need to install this package. This can also be done by installing it in either your system path packages or in the lib/python directory of your Zope instance. As with feedparser you can do this using either easy_install or via the setup.py script.

After installing the package it needs to be registered in your Zope instance. This can be done by putting a collective.portlet.feedmixer-configure.zcml file in the etc/pakage-includes directory with this content:

<include package="collective.portlet.feedmixer" />

or, alternatively, you can add that line to the configure.zcml in a package or Product that is already registered.

Installing with buildout

If you are using buildout to manage your instance installing collective.portlet.feedmixer is even simpler. You can install it by adding it to the eggs line for your instance:

[instance]
eggs = collective.portlet.feedmixer
zcml = collective.portlet.feedmixer

The last line tells buildout to generate a zcml snippet that tells Zope to configure collective.portlet.feedmixer.

If another package depends on the feedmixer egg or includes its zcml directly you do not need to specify anything in the buildout configuration: buildout will detect this automatically.

After updating the configuration you need to run the ‘’bin/buildout’’, which will take care of updating your system.

1.2 - 2008-07-10

• Fix the “More …” link of the portlet. We have to store the path to the context of the portlet assignment, because plone[.app].portlets doesn’t expose it. This workaround was taken from ely.portlets.image. This will only work for newly created feedmixer portlets, existing ones will still create wrong urls in subfolders. [fschulze]

• Added french translation and made some i18n fixes. [glenfant]

1.1 - 2007-11-28

• Correct caching of mixed feed entries: caching per instance instead of per request meant we would never update our feed as long as the ZODB did not expire the assignment. Instead to cache per request and using the list of feed_urls of the assignment. [wichert]

• Fix typo in the portletBottomLeft CSS class name. [daftdog]

1.0 - 2007-11-05

• Initial release.