#41 — BadRequest Error if enclosure already exists
by Domen KoÅ¾ar — last modified Dec 27, 2011 10:12 PM
|Submitted by||Domen KoÅ¾ar|
|Submitted on||Nov 25, 2011|
|Responsible||Maurits van Rees|
If enclosure already exists, invokeFactory will return BadRequest error since it expects unique id
Added by Maurits van Rees on Dec 27, 2011 05:38 PMThat would be strange. When updating an existing feed item, feedfeeder calls the replaceItem method of the folder, which removes the existing item and adds a fresh one. This fresh one of course does not contain any enclosures.
Responsible manager: (UNASSIGNED) → maurits
Are you using any patches?
Or are you just guessing that this happens in theory? I got confused myself anyway, as I wondered during testing where the previous enclosure had gone. :-)
Added by Domen KoÅ¾ar on Dec 27, 2011 08:27 PMThis only happened once and since it was on production, I didn't have time to investigate what exactly went wrong. Cronjob just started failing.
What was happening was that invokeFactory could not create enclosure. If I remember correctly this happened due to two posts having the same signature for enclosure. Is that possible to conflict?
Added by Maurits van Rees on Dec 27, 2011 10:00 PMNo, that works fine. I have just tested it.
Issue state: Unconfirmed → Resolved
But when one entry has two enclosures that have the same href, then this BadRequest error will occur.
Fixed in r247577.
Added by Domen KoÅ¾ar on Dec 27, 2011 10:09 PMThanks!
Added by Maurits van Rees on Dec 27, 2011 10:12 PM2.0.7 has been released with this fix.
Target release: None → 2.0.7
No responses can be added.
If you can, please log in before submitting a reaction.