Thanks for the thoughtful reply, Ryan. I don't mean to just bitch about SimplePie, although I'm sure that's how it came off -- SP really is a great project. And in fact the sanitization I complained about is not happening in SimplePie: it's definitely Drupal that's killing the data somewhere along the way.
It's interesting to hear that the custom tag data is already available in the [data] object of... the parser? I definitely did a print_r on the item objects, and thought I probably would've done the same for the parser. Perhaps I forgot to. It's definitely not available in the item object, though, which seems like the logical place for it.
In any case, I do have to stick by my complaint about the variability of the data structures returned by the custom-tag-grabbing routine, particularly when retrieving an item with nested subelements. Check out how you access an FLV included by the widely-supported MediaRSS namespace:
Thanks for the thoughtful
Thanks for the thoughtful reply, Ryan. I don't mean to just bitch about SimplePie, although I'm sure that's how it came off -- SP really is a great project. And in fact the sanitization I complained about is not happening in SimplePie: it's definitely Drupal that's killing the data somewhere along the way.
It's interesting to hear that the custom tag data is already available in the [data] object of... the parser? I definitely did a print_r on the item objects, and thought I probably would've done the same for the parser. Perhaps I forgot to. It's definitely not available in the item object, though, which seems like the logical place for it.
In any case, I do have to stick by my complaint about the variability of the data structures returned by the custom-tag-grabbing routine, particularly when retrieving an item with nested subelements. Check out how you access an FLV included by the widely-supported MediaRSS namespace:
$item[0]['child']['http://search.yahoo.com/mrss/']['content'][0]['attribs']['']['url']
Using an empty string to index an array is pretty awful. Ick.