Post edited 8:02 pm – 21 September, 2009 by webservant
Mark,
Don't know if this is related to the other issue, but I am no longer able to subscribe to any RSS feeds. In FireFox, I get "Feed Failed to Load" and in IE I get,
"A string literal was not closed.
Line: 28 Character: 19
<enclosure url="
Rich
Rich Brown Webmaster, Aisquith Presbyterian Church Parkville, Maryland, USA sermons.aisquith.org
Thanks for the bug report. Sorry it's yet another problem for you.
If you can view the source of the podcast, you'll see the problem. It's stopping partway through.
Can you help me determine the cause? Can you edit your most recent sermon ("A led community"), and temporarily delete the URL attachment. Then try the podcast again and let me know how you get on. If it doesn't work, can you view the source and see if the same thing happens, or something else.
Thanks for the bug report. Sorry it's yet another problem for you.
If you can view the source of the podcast, you'll see the problem. It's stopping partway through.
Can you help me determine the cause? Can you edit your most recent sermon ("A led community"), and temporarily delete the URL attachment. Then try the podcast again and let me know how you get on. If it doesn't work, can you view the source and see if the same thing happens, or something else.
Thanks, I appreciate your patience.
Mark – I just deleted the url attachment as you suggested, attempted to subscribe, and the same thing happens.
Rich Brown Webmaster, Aisquith Presbyterian Church Parkville, Maryland, USA sermons.aisquith.org
OK, thanks. I need to know what error message is being created when this problem occurs.
If you have error logs on your server, can you look for recent errors with podcast.php, and tell me what they are.
If you don't have logs, could you add the line
(define 'WP_DEBUG', true);
to your wp-config.php file? (There are some instructions here.) Then try the podcast, view the source, and let me know of any errors you see.
Adding WP_DEBUG may show up minor errors on your site that you're not aware of. That's to be expected, so remove the line from wp-config once you have the information you need.
Unfortunately, the first minor error with audio player is preventing the real error with Sermon Browser from displaying. Sorry to be a pain, but could you temporarily disable AudioPlayer, then add WP_DEBUG back, then let me know the new error with the podcast. Once you've done that you can remove the WP_DEBUG and re-activate AudioPlayer. Thanks.