The feed on MobileMe is no longer available as the service is closed. You needed to add the 'itunes:new-feed-url' tag to the old feed in order to change iTunes to the new URL, but this is no longer possible.
You have only two courses of action: you should first check that the current feed works OK by subscribing to it manually from the 'Advanced' menu in iTunes and making sure it appears in the 'Podcasts' section and downloads the latest episode.
1. Email Support at podcasts 'at' apple.com and explain the situation and ask them to change the Store to using the new feed. Give them the ID number and both feed URLs. I can't promise they will do this, though they have for some other people so you may be in luck.
2. Failing that you will have to submit the podcast as a new one: you will have to change the title slightly or you will be told it has already been submitted.
Thanks. This seems like it's going to be quite a production I fear. My first and main problem is that I don't have a new feed to subscribe to. The podcasts are held here: http://www.thetrap.co.uk/Podcast/Podcast.html and here: http://www.thetrap.co.uk/Event_Horizon_Crescent/Event_Horizon_Crescent.html
but i think I need an 'RSS' feed don't I and that doesn't seem to there on the new site. Am I being thick?
Web should create the RSS files automatically - there are links to them on the sites - and they should be at
(two separate podcasts) but there are no files at these addresses. The first thing to do is to check that these checkboxes are enabled in the Inspector:
though I would have thought the fact there are links to the feed would mean that these boxed were checked.
Then you should do a Publish all files from iWeb, using the FTP option in the publish pane. (If you had simply copied the pages over from MobileMe, that could cause problems; you need always to publish from iWeb).
If that doesn't do any good you have some ongoing problem in iWeb and the best place to ask would be in the iWeb Forum.
Thanks Roger. Unfortunately, despite those both being ticked and me publishing directly from iWeb using the FTP option it's still showing nothing at either of those links. Am wandering over to the iWeb section to see if anyone there has any smart ideas. Thanks so much for your help though, you are something of a guru, sir!
Found it. The feeds are at
Somehow a redundant 'web' folder has got into the link on the page - I can't say how that has happened.
One last step I need for this. Apple have now redirected my feed to those addresses which is great. However, at that address, the links to the files are wrong. For example, if I click on Trap Sodcast 65, it give me a 404 not found at: http://thetrap.co.uk/web/Media/Trap%20Sodcast%2065.mp3
However, again, by removing the word 'web' I find the right file which is actually at: http://thetrap.co.uk/Media/Trap%20Sodcast%2065.mp3
I guess I'm asking if you know how I can get those links in the feed to point to the right addresses (the ones without the 'web')
Since you can't amend the feed directly in iWeb this is a bit problematic. You need to set iWeb to get the URLs correct when it creates the feed. Probably you can do this by going to the publishing page and making sure that the 'Website URL' section has the correct URL entered in it - presumably the URL of the home page - and re-publishing.
Hmm, the site url in the publishing page is just http://thetrap.co.uk
'Web' is the 'Site name' which seemed to get added when I moved from MobileMe to the new place so I have no idea how to take it out of the podcast urls.
Perhaps there is a way I can move my site to something other than iWeb that would be easier to use but would also publish to the same url? I guess there's no way to edit the RSS feed with another piece of software while using iWeb huh?
You can't exactly move the site to RapidWeaver - you would have to recreate it from the ground up. In the process all the links should work correctly. Though I have to say neither RW nor iWeb are ideal for podcast creation because of the relatively limited options, though both do work.
iWeb ought to be able to get this right: there is an issue somewhere in your publishing process but I can't say where it is. Hopefuly someone who uses it more will be able to pinpoint the problem.