Needed is proper parsing of the source RSS to generate the end date and time for individual schedule items to allow mapping.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | feeds_cablecast-2204997-fix-for-parsing.patch | 4.33 KB | limako |
Needed is proper parsing of the source RSS to generate the end date and time for individual schedule items to allow mapping.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | feeds_cablecast-2204997-fix-for-parsing.patch | 4.33 KB | limako |
Comments
Comment #1
limako commentedHere's code that munges the values from the tightrope server into values that can be imported using feeds.
Comment #2
kreynen commentedSTeve,
FIRST, THANKS FOR THE PATCH!
Now some process feedback. Issues rarely go from from Active -> Fixed. It really isn't fixed until the code gets committed and then the process is to include this issue # in the commit and give you credit for the fix. That's what this info on your Drupal.org user profile page is about...
When you submit a patch for an active issue, the status should really go to Needs Review. Ideally several people other than the person maintaining the module will offer feedback, but with a community media specific module like this that has a small potential audience, I'll likely do the review and skip the "Reviewed and Tested by the Community" (RTBC) step.
Getting to the RTBC is really the goal to all commits.
Comment #3
limako commentedThanks. I'm just now learning how this all works.
Comment #5
limako commentedFixed in alpha1.