collective.atomrss
Package extends Plone syndication for using Atom RSS by default.
“The Atom syntax was specifically designed to allow elements to be reused outside the context of an Atom feed document” wikipedia
It added some field as events date, image (for news) and leadimage (for event) into rss content feed. This package also add content text into rss feed What this package do : * Added content into rss items feed, by default, render_body is set to True in FeedSettings * Added image (for News Item), leadimage (for Event) in content items * Use only Atom as default view in FeedSettings
It also package added event startdate, enddate, location, organizer, type into feed items as explain in http://web.resource.org/rss/1.0/modules/event/
How it works
This package : * adapts IFeedSettings for changing default value of rss feed. * override atom.xml browserview for adding news image and event informations.
Installation
To install collective.atomrss you simply add collective.atomrss to the list of eggs in your buildout, run buildout and restart Plone. Then, install collective.atomrss using the Add-ons control panel. Changelog =========
0.1.13 (2018-01-08)
Enclose text of an object in details tag. [bsuttor]
0.1.12 (2017-12-12)
Accept html content for address. [bsuttor]
0.1.11 (2017-12-04)
Fix event location. [bsuttor]
0.1.10 (2017-04-27)
Fix at event date. [bsuttor]
0.1.9 (2017-04-27)
Formated date for event start and end. [bsuttor]
0.1.8 (2017-03-24)
Do not try to see an image on file. [bsuttor]
0.1.7 (2017-02-21)
Use enclosure media type for lead image. [bsuttor]
0.1.6 (2016-11-16)
Fix event rss. [bsuttor]
0.1.5 (2016-04-25)
Add dexterity support. [bsuttor]
Lint README file [bsuttor]
0.1.4 (2015-05-12)
Modifications to get events’ startdate and enddate into RSS feeds. [cboulanger]
0.1.2 (2015-03-12)
Do use override.zcml, for settings adapter. [bsuttor]
0.1 (2015-03-05)
Package created using mr.bob [bsuttor]
2 maintainers
Metadata
2 maintainers
Release files for collective.atomrss 0.1.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.atomrss-0.1.13.tar.gz | 19.5 kB | Without provenance | Details for collective.atomrss-0.1.13.tar.gz |
Release files / collective.atomrss-0.1.13.tar.gz
| Download URL | collective.atomrss-0.1.13.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8df91a1ccce08209ddf71a09092d82841fa504471d3a782e30a906c7656026b0
|
|
BLAKE2b-256 checksum How to use checksums |
b2135a9dca80d68820a2f7af726f28880dd924cdb0c1eda654536822438b532d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.atomrss 0.1.13
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
