I have followed instructions and everything went smoothly - great video. The only problem I am having is the feed aspect. It creates the path for my feed but there is never any content. Why would this be? Could it be that the feed needs time to grab the file (a lot of time)?

Any suggestions would helpful.

Comments

Rob_Feature’s picture

Title: RSS Feed » No file in RSS output
Component: User interface » Documentation
Assigned: cole.m.french » Rob_Feature

This will be a documentation issue because the method for adding the field to the feed has changed in 0.4 due to changes in the Views API.

So, unfortunately, the answer right now is: Standby. As soon as we have this sorted out, we'll let everyone know.

Rob_Feature’s picture

Status: Active » Fixed

Fixed in version 6.x-0.5! Horray!

lefnire’s picture

Version: 6.x-0.4 » 6.x-0.5
Status: Fixed » Active

I'm still having this issue. ffpc 6.x-0.5, views 6.x-2.0-rc4. take a look at http://ocdevel.com/podcast/feed. the weird thing is that you can view-source and see the feed, it must just be excluding some xml bit somewhere.

Rob_Feature’s picture

Status: Active » Postponed (maintainer needs more info)

Can you upload a screenshot or even better a screencast of your Views setup? I have a feeling something may be incorrect in your setup.

Have you checked all your permissions to make sure those nodes/content are allowed to be viewed by unauthenticated users (including the filefield)? I've seen this happen when permissions don't allow the feed to be viewed.

If it's not that, my second guess is all the crazy markup I'm seeing in your XML. I'm wondering if maybe something there is stopping the feed from showing. More info please!

lefnire’s picture

good call, it was all of the above :) (fixed permissions displayed broken rss, fixed markup to resolve the rest). And of course, awesome videocast. watched them all, extremely valuable and definitely going to get coverage in my podcast.

lefnire’s picture

Status: Postponed (maintainer needs more info) » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.