Posted 9 months ago #
Our feed is http://victoryfort.org/?feed=podcast
Feed Validator says:
This feed does not validate.
line 1, column 0: XML parsing error: <unknown>:1:0: no element found
In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.
Feeds should not be served with the "text/html" media type
It used to work. Now it won't work with iTunes and podcast aggregators. HELP! Thanks!
That is an unusual problem and it is hard say what the couse of it is since the there is no output when you open this feed URL.
But it is save to say that it is a problem which occurs only under certain circumstances. It does not occur in many other blogs (This is the first report).
Have you modified the settings of the blog or a plugin recently?
Have you installed or updated other plugins? (maybe security plugins or plugins which influence the Permalinks)
Please control the podPress settings on the iTunes/Feed settings page section podPress Feeds:
Does the podPress Feed with the slug name "podcast" exist?
Is it marked as an active feed?
Tim
Posted 9 months ago #
Thank you for the quick response!
To answer your questions:
I haven't modified the settings of the blog or a plugin recently. Not that I remember, anyway.
I set the feed slug name to be "podcast". Should I be creating the feed elsewhere?
Yes, it's marked as an active feed.
What do you recommend that I do?
Thank you so much!
Thank you for your answers.
Only to be more sure that this is no Permalink problem, please save the Permalink settings of your blog once more.
Furthermore it is still difficult to say what is wrong because this is no known problem and there is no error message. It would be great if you could look for a log file on the server of your which contains PHP error messages. You may ask your hosting provider where you can find such a file (or if there is such a file.).
But there is maybe a further way to retrieve a error message which could help me. You could set temporarily a debug switch in the wp-config.php file.
Copy this line:
define('WP_DEBUG', true);in the wp-config.php file and open the podcast feed URL in a web browser. Maybe you will get an error message instead of a blank page.
Please post the error message here (or if it is more than 15 lines then in a pastebin.)
You can read more about this here: http://codex.wordpress.org/Editing_wp-config.php#Debug
Posted 9 months ago #
Hello, I tried the WP_debug in wp-config, and this is the error message:
Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home1/victorz9/public_html/wp-includes/functions.php on line 3382
Posted 9 months ago #
I also tried replacing our current podpress installation to version 8.8. The XML becomes valid, but does not reflect any of our podcasts. Also, the display_podcast tag doesn't work. And when I upgrade to 8.8.10.11 again, the XML becomes invalid again.
Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home1/victorz9/public_html/wp-includes/functions.php on line 3382
That is a surprising error message. It points to a file which is part of WP. But in the wp-includes/functions.php of the current WP version (3.2.1) is no call of function get_settings. I thinks that maybe the last WP upgrade was not complete.
That is nothing you can do without editing some entries in the data base of your blog. Because this:I also tried replacing our current podpress installation to version 8.8.
happens if you do anyway.The XML becomes valid, but does not reflect any of our podcasts. Also, the display_podcast tag doesn't work.
And when I upgrade to 8.8.10.11 again ...
Please, upgrade to 8.8.10.12. .11 had a bug which may not be related to this XML problem which you have mentioned but it solves definitely a different and serious problem.
Please, post the error messages which the feed validator (e.g. http://validator.w3.org/feed) gives you.
I have validated your RSS feed again some minutes ago and all looked fine. What is your current setup? (WP version? podPress version?)
Posted 9 months ago #
Hi, it worked after I disabled all plugins. I reactivated them one by one to see which conflicted with podpress, but they are now all reactivated, and nothing is conflicting with podpress yet. This is good news, I guess, but I don't like NOT knowing what went wrong.
Oh well. I'll post another inquiry if something goes wrong again. I hope it doesn't!
WordPress: 3.2.1
Podpress: 8.8.10.11
Will upgrade soon.
Thanks so much for your time.
Sarah
You must log in to post.
