• Resolved pcvip

    (@pcvip)


    Hugh:

    If you look at this:

    http://s531852489.onlinehome.us/ssp.jpg

    You’ll see a problem I’m having with SSP. I’ve installed it, and it’s finding embedded .MP3 files in my existing WP posts … and linking them incorrectly by concatenating the file, the “0” character, and the string “audio/mpeg”.

    When I edit this to delete everything after “…mp3”, and update the post, the other items (duration, file size, etc.) get filled in, the post gets added to my feed, and iTunes eventually picks up the new item.

    Why is this happening and how can I mass replace all the erroneous entries to eliminate the “0audio/mpeg” ? That bad data isn’t actually anywhere in the database, so SSP is building it from other data its finding in the postmeta table.

    Thanks.

    https://wordpress.org/plugins/seriously-simple-podcasting/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Hugh Lashbrooke

    (@hlashbrooke)

    Could you please confirm that you are running the latest version (v1.9.8)? There is no reason that this should be happening in the latest release, so if you confirm that then I can look into it further.

    Thanks,
    Hugh

    Thread Starter pcvip

    (@pcvip)

    yessir 1.9.8

    btw: i’ve manuallly edited 8. here’s the itunes page: https://itunes.apple.com/us/podcast/the-wordpress-helpers/id992206449

    there are almost 150

    Plugin Contributor Hugh Lashbrooke

    (@hlashbrooke)

    So when you edit the field and then update the episode it saves the URL just fine?

    If that’s the case then there’s no further issue here in SSP. When that field is saved, it doesn’t do anything other saving the string that you provide to the episode meta field. So there is no additional processing or concatenation going on.

    Thread Starter pcvip

    (@pcvip)

    Hugh, I get that “it’s working as long as … ” qualifies as “issue resolved”. AND: new posts are picking up none of that silliness; I need to fill them in to make them work (which isn’t as god as magic, but I can’t argue with right?).

    My concern is that something in your software scanned the posts, SAW .mp3 files, and attempted to fill data in but got it wrong. And while that’s an intellectual puzzle that you might not be interested in solving the issue is “it goofed this up once, what’s to stop it from goofing something else up?”

    Also (to my original question, actually), since there is something in there that filled in the boxes but the concatenation was comprised of at least one string that simply doesn’t exist (I’ve pored over the database and especially the postmeta table), Shouldn’t we both care ?

    Just sayin’ …

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Bad mp3 concatenation’ is closed to new replies.