Damnit! Libsyn screwed up so Wordpress didn't generate the enclosure. That means that feedburner didn't pick up the enclosure from WordPress. I can't find a way to get Wordpress to regenerate the feed properly. Working on it.
Libsyn has its issues. I await a worthy competitor to whom I would rather give my money. We're using them at best as a stop-gap solution to our growing bandwidth and storage concerns.
Direct your complaints to shit-ass libsyn. This never happened when we hosted the files on our own server. I think what happens is when we click "publish" in WordPress it checks to see if there are any mp3 links. If it finds any it looks to see if they are real links. Because libsyn is crappy those links sometimes 404. Therefore WordPress to not create the enclosure. I must then create the enclosure myself, manually. At least that's the current theory. I'll just have to get into a habit of checking every single night.
Oooooooooh. So obvious. I'll test that tonight. The problem here is that we want the enclosure to point to the redirect, not to the file behind it. Libsyn likes to move files around, and the redirect is the only way to make links to our mp3s that always work.
I love the way you guys have a problem and can't fix it, then somebody googles it and comes up with a result right after you two talk about using google to find results for people problems.
Yeah, that had occured to me, it was just that it happenned again, and then you said it was 'so obvious' after the google post. Meh. Maybe I'm too tired to be reading tonight.
Comments