I have followed the steps from the video. Here is where I am: http://www.purtle.com/rssfeeddemo

The feed title appears. But, I don't see any of the Apple RSS data in the source for that page. I might be doing something wrong or have something set incorrectly. I created a content type called "foo" like in the video. I only have one field that I added, which is the "Audio" field like in the video. I assume that I create the new podcast content by publishing a new "Foo" node. Nothing is appearing to change on the rss feed.

Can someone please point me in the right direction?
jeff@purtle.com

Comments

Rob_Feature’s picture

Status: Active » Postponed (maintainer needs more info)

The link you posted was dead. However, most likely, you didn't add any ID3 information to your audio file before uploading. There is currently no way in this setup to add ID3 info during the node creation process (that's an additional module we're considering building), so it all should be done when creating your MP3 (which is really where it should be done anyway).

I'm going to mark this as "needs more info"...please add some details as to what is missing. Is it creating a feed with an enclosure file? That's all that this module seeks to do at this point.

jeffpurtle’s picture

Sorry. I moved it to http://www.purtle.com/podfeed
What is strange is that in Safari I see two items. In Firefox I don't see either item. In iTunes I don't see either item. When I add the feed to Feedburner it doesn't show either item. My feed at Feedburner is http://feeds.feedburner.com/PurtlePodcast

I tried using Feedburner because it didn't look like the FFPC module included all the iTunes tags like Explicit Language, Copyright, etc.. I thought I could add it with Feedburner, but can't get it to work.

I have tried to refresh all the above pages and get the same result. What is strange is that Safari adds a bunch of extra Java (or something like that) when you view the source.

My goal is to have a web based way of uploading various kinds of media (i.e mov, mp3, aac, pdf) that will all play in iTunes. I think FFPC will all me to do that. But, I don't know if I really need to use Feedburner to add the additional info. or not. I want to get statistics like Feedburner does and I want my podcast promoted as widely as possible.

I would almost be willing to pay someone to help me with this if it's under $100.

Jeff

Rob_Feature’s picture

@jeff_purtle

Well, step one will be to find out why the feed isn't outputting. If feedburner isn't seeing the feed (which it's not) something in the drupal setup is incorrect. Can you do a screencast video or upload some screenshots of your Views setting which is outputting the feed? It's possible that your view isn't setup properly.

The other possibility (that I've run into when I forget) is to make sure anonymous views have permissions to view filefields or other parts of your node. If they can't then your feed won't output anything. This could be the reason for browsers showing different results (if you're logged into your site in one and not in another).

It's most definitely a drupal/views setup problem, so I'd start with those ideas.

As for adding all the iTunes stuff, FFPC doesn't add anything to your ID3 tags. All of that should be done when actually creating your MP3 file. If you convert using iTunes you can add all this info to each episode and it will then output with your FFPC field. I want to create an add on module that allows you to add/change these tags right in Drupal, but we haven't done that yet.

If, after all this, you'd still like paid help, I can most likely login to your site and fix it for $75 (assuming it's a simple setup issue). Just use my contact form if you need that.

jeffpurtle’s picture

I had it working great until today. Your suggestion about permissions was the answer. I also used Feedburner to add in more of the iTunes tags and track the feed.

However, I did an update on CCK and Views and then it all stopped working. I am not sure what to do to fix it. I did update.php. I also went back to the beginning and even uninstalled CCK, View, Filefield and FFPC and started over. What happens is that FFPC does not appear when I am trying to add it to the View I am creating. It shows as installed and checked off in the Modules on my site. I checked the permissions and everything looks ok. I am a little baffled. I thought I understood this.

Jeff

Rob_Feature’s picture

Component: Miscellaneous » Code

@suydam
Is there a reason that this might not work with an update of Views? I'm not sure why it wouldn't, but I suppose it's possible that they changed something in the update. Any thoughts?

Rob_Feature’s picture

Title: More details for creating the content type for this » Not Compatible with Views RC2 and RC3
Assigned: Unassigned » Rob_Feature
Category: support » bug
Status: Postponed (maintainer needs more info) » Active

It appears that FFPC breaks in Views RC2 and RC3. We're investigating the issue and an updated will be posted if that's the case and we can get it worked out.

designerbrent’s picture

Version: 6.x-0.1 » 6.x-0.2

Does the 6.x-0.2 version fix this?

Rob_Feature’s picture

@designerbrent
No, not totally. It's a stopgap that requires you to name your CCK filefield a particular thing (see the release notes). A real fix to this will be coming in a matter of a week or so. Stay tuned....

designerbrent’s picture

@bobchristenson

Ok.. so at least it can work... if I make sure to set everything up correctly. Gotcha.

Thanks for all this work on making audio handling so flexible.

Rob_Feature’s picture

Version: 6.x-0.2 » 6.x-0.3
Priority: Normal » Critical

Standby...a new version 6.x-0.4 should sort out all the issues since the ViewsAPI changes broke the module. Watch for it on the project page. An 'official' release won't be available until the ViewsAPI is officially out of beta.

mfer’s picture

Assigned: Rob_Feature » mfer

Commited a changed that should work with the views api as of Views 2 RC 3. I'll mark this fixed when suydam has had a chance to confirm it's working correctly.

Rob_Feature’s picture

Status: Active » Fixed

Fixed in version 6.x-0.5! Horray!

Anonymous’s picture

Status: Fixed » Closed (fixed)

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