Support » Plugin: PowerPress Podcasting plugin by Blubrry » How to resolve XML error in feed?

  • Resolved westerngeomancy

    (@westerngeomancy)


    My XML feed has stopped working, it shows “error on line 306 at column 39: attributes construct error”

    I have tried clearing the cache and disabling all plugins except Powerpress, but I can’t get it to resolve itself and I can’t see any way to refresh or edit the XML.

    I’m a bit stumped as to what to try next?

    The page I need help with: [log in to see the link]

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support Shawn Thorpe

    (@shawnogordo)

    Based on what’s displayed there, it looks like some weird code was added to the media enclosure tag pointing to this media file:
    http://adventuresindowsing.com/wp-content/uploads/AdventuresInDowsing-52--2017-12-02.mp3

    Go to the Post within your WordPress site that links to that media file. Remove the Podcast Episode attached to that Post, click the Update button, and create a new Podcast Episode on that Post linking to the same media file. Hopefully, doing so will create a new enclosure tag without the bad code.

    Thread Starter westerngeomancy

    (@westerngeomancy)

    OK, so I removed the podcast episode from the post, updated the post, cleared the cache, then viewed post and was still able to play the episode.

    I then tried changing the file name and re-uploading the episode, attached to post and verified, but when I view post it now doesn’t play.

    Castfeed validator is now returning this error: “rror parsing XML. is invalid XML, likely due to invalid characters. XML error: > required at line 313, column 39. Did not finish feed tests.”

    Thread Starter westerngeomancy

    (@westerngeomancy)

    Oops, my bad – I’d made an error in the file name when I changed it. That’s working now, but the feed is still having the same problem.

    Plugin Support Shawn Thorpe

    (@shawnogordo)

    Line 313 in your podcast RSS feed is being generated by this post on your WordPress site:
    https://adventuresindowsing.com/aid052-ned-wolf-nandias-copper/

    Line 313 contains this:
    <itunes:subtitle>American dowser and author Ned Wolf joins us from Flagstaff, Arizona to talk about his work as a healer and his new dowsing-related children’s books “The Nandia Trilogy”. Plus, the latest dowsing news, and Grahame has a bit of a rant (56 mins,</itunes:subtitle>

    If your Podcast Episode is showing anything in the Subtitle field (found by clicking the More Settings link inside the Episode Info tab), completely clear it out and update the Post.

    Thread Starter westerngeomancy

    (@westerngeomancy)

    If your Podcast Episode is showing anything in the Subtitle field (found by clicking the More Settings link inside the Episode Info tab), completely clear it out and update the Post

    There is nothing in the subtitle field, or any of the other fields in the advanced section, other than the default ‘Type – Full(default)’ and ‘Block – No’ fields. I never go into that when posting.

    Thread Starter westerngeomancy

    (@westerngeomancy)

    I have just gone through every post and have checked and updated the details and links on every episode to make sure they are working, but I’m still getting the ‘error on line 315’ message.

    This is really frustrating – is there a way to manually edit the feed? I’m sure that I’d have sorted this out by now if that was possible.

    Plugin Author Angelo Mandato

    (@amandato)

    Hello @westerngeomancy,

    Looking deep at the episode with the issue, i see it has a URL for an image: http://adventuresindowsing.com/wp-content/plugins/podpress/images/vpreview_center.png This image is in a folder called “podpress”, which makes me think that you migrated from PodPress to PowerPress at some point. Can you tell me how long ago this was?

    It appears how ever the data is stored it got messed up in some way stored in the database. PowerPress can convert PodPress data but it still cannot if it got corrupted in some way. I am doing some tests with the full value to see if we can add logic to fix the error.

    One fix is to go into PowerPress menu > tools, there is an option there to import PodPress to PowerPress format. This may fix this issue.

    Thanks,
    Angelo

    Thread Starter westerngeomancy

    (@westerngeomancy)

    Hi Angelo,

    It was a couple of years ago that I migrated from Podpress – I can’t remember exactly.

    This problem only occurred recently, I think when I increased the server storage space. I’m wondering if it’s something to do with an old site backup file?

    Looking at the import options you suggest, I tried importing Podpress settings, which seemed to have no effect.

    Then I looked at importing Podpress episodes, which is returning 2 warnings:
    ‘We found blog posts that have 2 media files. You will need to create 1 more Custom Feed in order to continue..’, and
    ‘We found blog posts that have 2 media files.You will need to create 1 Podcast Channels to continue.’

    Each episode is now showing 2 files, of which File #1 seems to be the one it wants to import. I haven’t done this yet as I’m not entirely clear what the best course of action is at this point!

    Plugin Author Angelo Mandato

    (@amandato)

    Hello @westerngeomancy,

    Okay if these episodes were from PodPress that explains part of the issue. I looked at the episode formatting how it is saved in the database in the older versions of PodPress, the PowerPress import would not work with them due to using the enclosure (instead of the “podPressMedia” field). The weird thing is that these episodes podpress made are normally stored in a field called “podPressMedia”, and it appears they may have been renamed to “enclosure”.

    Options:
    1. very advanced: If you can backup your post_meta table, you could first backup the table, then do a QUERY where you rename the column name where it currently = ‘enclosure’ to ‘podPressMedia’. This is rather advanced and I do not recommend this method if you are not comfortable with SQL queries. Once these columns are renamed, the PowerPress import PodPress option should pull the episode data. I can write a query for you if that would help.

    2. Manual edit: each one and fix them. You will need to show the option to edit the “custom fields” for posts then delete the enclosure then save the post, then use the episode box in powepress to re-enter it. This would be the most painful.

    3. Share your blog posts in an export: If you are willing to share an export of your “published” blog posts, please email the the WordPress export to cio [at] blubrry dot com (will not need pages, media, comments, revisions, etc.. just the published posts). Export is found in the WordPress left menu: Tools > Export. Over the weekend I will add code to the PodPress import for this situation and use your episodes as test data in my dev environment.

    The export would also help me identify other possible issues and that the data is saved to the database post_meta table correctly.

    I am also trying to get older versions of PodPress to work to re-create the data but at the moment I am not having much luck due to the newer versions of WordPress’ PHP version requirements.

    Thanks,
    Angelo

    Thread Starter westerngeomancy

    (@westerngeomancy)

    Angelo,
    Option 1 is beyond me!
    Option 2 sounds like a lot of work!

    I have therefore gone with option 3, and have emailed you the post feed as you suggest.

    Many thanks for your help on this.

    Plugin Author Angelo Mandato

    (@amandato)

    Hello @westerngeomancy,

    I still did not see an email from you. Double check the attachment is not more than 10MB, perhaps that is why it was blocked. If you can give me the part after your @ in your email address i can search my spam folder as well.

    Thanks,
    Angelo

    Plugin Author Angelo Mandato

    (@amandato)

    Hello @westerngeomancy,

    Never mind, found your email. Sorry about that. Working on testing it now.

    Thanks,
    Angelo

    Thread Starter westerngeomancy

    (@westerngeomancy)

    Angelo, your fix has worked! Thanks ever so much for your help.

    Plugin Author Angelo Mandato

    (@amandato)

    Awesome!

    If you have a moment, we would greatly appreciate a review for our plugin and the support we provide. Thanks again for being patient with us to figure out the issue!

    Thanks,
    Angelo

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘How to resolve XML error in feed?’ is closed to new replies.