On Apr 12, 2006, at 12:27 PM, Lance Lavandowska wrote:
I'm with Matt on this, I'd rather Roller didn't encourage summary feeds.

I hate partial feeds too.

Check my response to Matt. As before, the only way to get excerpted feeds is via the excerpts=true URL parameter.

However, I don't think Roller should enforce a policy here. In the future, we might want to allow sites to make partial feeds the default and to only serve fill content in response to a excerpts=false request -- but I'm *not* proposing that now

- Dave



On 4/12/06, Matt Raible <[EMAIL PROTECTED]> wrote:
It sounds good - but would we *have* to use it? I'd like an option to disable it and keep the current system. This seems like it might lead to shorter "summary" type RSS feeds, and I think those suck. I want a
full feed or I'll unsubscribe. ;-)

Matt

On 4/12/06, David M Johnson <[EMAIL PROTECTED]> wrote:
I'd like to get this into a Roller 2.3 release this month, so please
review and offer feedback.

-Dave


Proposal Entry Content

Add support for both a summary text and full content property for
each Roller weblog entry

All major weblog systems and common newsfeed formats now support the
notion of a both short summary text and full content for each weblog
entry. Roller users have used the Read-More plugin to emuluate
summary and content, but creating a summary by automatically
stripping HTML from and truncating the content is not really an
acceptable alternative. This proposal adds support for a new content
property on the WeblogEntryData object to hold the full content of
each blog entry, supporting the Atom content model and using the
conventional mappings to RSS (i.e. text/summary goes to <description>
and content goes to <content:encoded>).

http://rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_Entry_Content





Reply via email to