#183 — Ensure all feed content lists are by effective date
by
FairSay
—
last modified
Apr 27, 2009 01:50 PM
| State | Rejected |
|---|---|
| Version: | 1.7 |
| Area | Functionality |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | FairSay |
| Submitted on | Apr 21, 2009 |
| Responsible |
—
|
| Target release: |
—
|
At present, if a blog post is edited, its listing in the blog listing remains the same (by effective date if it exists and otherwise by the published date). However the feeds seem to list in order by the modified date - meaning any editing of a post makes it pop back up to the top of the feed.
What should happen is that the positionj in the feed remains unchanged unless the effoective date is changed as happens already with the blog post listing (non-feeds).
What should happen is that the positionj in the feed remains unchanged unless the effoective date is changed as happens already with the blog post listing (non-feeds).
Added by
FairSay
on
Apr 21, 2009 09:55 PM
Seem this might be the same as http://plone.org/products/quills/issues/177 ?
Added by
Jan Hackel
on
Apr 23, 2009 08:41 AM
I suppose so. Did you try trunk? It contains a fix. I have not had the time to check it.
Added by
FairSay
on
Apr 27, 2009 10:25 AM
The fix in trunk (http://svn.plone.org/[…]/) has solved the issue for RDF, ATOM and RSS.The only thing is that is is still listed as version 0.1 - should this be changed?
Added by
Jan Hackel
on
Apr 27, 2009 12:00 PM
The version numbers of GenericSetup profiles are a rather delicate topic that not even the core developers seem to get (see http://n2.nabble.com/Some-c[…]-to-ZopeSkel-td2561549.html). I think it should reflect the package version. I will prepare a new release of fatsyndication.
Issue state:
Unconfirmed
→
Rejected
Closing then as a duplicate of issue #177.
Added by
Jan Hackel
on
Apr 27, 2009 01:50 PM
Just released Products.fatsyndication 1.0.0.
No responses can be added.
If you can, please log in before submitting a reaction.