Ask your WordPress questions! Pay money and get answers fast! (more info)

Problem with Feedburner and wp WordPress

  • SOLVED

Hi,
this orignal feed has some problems and I need help to understand what is wrong:
http://www.idtraveller.com/?feed=rss2&wpmfeedkey=1;dd389e0cd36b07e445d38e7a51f5870b

"The URL does not appear to reference a valid XML file.
This feed does not validate.
• line 1, column 0: XML parsing error: <unknown>:1:0: no element found"

What do I need to do?

Thanks
Charlotte

Answers (5)

2013-09-26

Eric P. answers:

Do you have a feed.php or feed.html (or any feed.*) in your site root directory? If yes, remove or rename it to something that doesn't get served for /feed/ (bad.feed.*, for example).

Is there a feed directory in your site root director? If yes, remove it.

If you are using a cache plugin, disable it. Some cache plugins leave things even when you disable them. If you were using W3 cache, there's more to removing it than just disabling it.

Try disabling all plugins. Does the feed url ( http://www.idtraveller.com/feed/ ) work with plugins disabled? Then re-enable plugins one at a time until it stops. Most likely, the plugin you enable that kills the feed is the issue.

If it doesn't work with all plugins disabled, then try one of the "default" themes. If the feed works with the default theme, but not with your "premium" theme, the problem is in the them.


Eric P. comments:

BTW, I checked your feed URL. It's blank. It contains no data at all.


Charlotte Raboff comments:

I have this file in my root directory:

wp-feed.php
<?php
/**
* Redirects to the default feed
* This file is deprecated and only exists for backwards compatibility
*
* @package WordPress
*/

require( './wp-load.php' );
wp_redirect( get_bloginfo( get_default_feed() . '_url' ), 301 );
exit;
?>
<em>Shall I remove this file?</em>

I check all plugins and deleted some but I have a membership plugin that I can´t delete but I don´t thinks is because of that. I can´t either change to another theme because of the membership plugin and all settings...


Eric P. comments:

That wp-feed.php isn't the problem. That just redirects calls to wp-feed.php to the actual feed URL. Here's what happens:


$ wget 'http://www.idtraveller.com/wp-feed.php'
--2013-09-27 10:44:35-- http://www.idtraveller.com/wp-feed.php
Resolving www.idtraveller.com... 62.20.1.160
Connecting to www.idtraveller.com|62.20.1.160|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.idtraveller.com/feed/ [following]
--2013-09-27 10:44:43-- http://www.idtraveller.com/feed/
Connecting to www.idtraveller.com|62.20.1.160|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0 [text/html]
Saving to: `wp-feed.php'

[ <=> ] 0 --.-K/s in 0s

2013-09-27 10:44:45 (0.00 B/s) - `wp-feed.php' saved [0/0]


The issue is that http://www.idtraveller.com/feed/ is an empty result (zero bytes).


Charlotte Raboff comments:

Ok, thanks... But what shall I do?


Eric P. comments:

I'm sending you my email in a private message. If you want, I'll install your theme on a test site and see if it kills the feed there.


Eric P. comments:

BTW, I get the same zero byte result going directly to the feed URL's:


$ wget 'http://www.idtraveller.com/feed'
--2013-09-27 10:58:52-- http://www.idtraveller.com/feed
Resolving www.idtraveller.com... 62.20.1.160
Connecting to www.idtraveller.com|62.20.1.160|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0 [text/html]
Saving to: `feed'

[ <=> ] 0 --.-K/s in 0s

2013-09-27 10:58:59 (0.00 B/s) - `feed' saved [0/0]

Something is completely killing your feed URL. There's nothing in the feed at all.

2013-09-26

Arnav Joy answers:

can you check your functions.php file , it should contain any extra space above and below the file.


Charlotte Raboff comments:

the functions.php file looks like this:

<?php
/**
* This file calls the init.php file, but only
* if the child theme hasn't called it first.
*
* This method allows the child theme to load
* the framework so it can use the framework
* components immediately.
*
* @package Genesis
*
**/

require_once(TEMPLATEPATH.'/lib/init.php');
//add_action('wp_head', 'echo_wp_query');
function echo_wp_query() {
global $wp_query;
print_r($wp_query);
}


Charlotte Raboff comments:

What shall I do with the functions.php file?

2013-09-26

Navjot Singh answers:

Try disabling each plugin one by one and keep checking. You may find if any plugin is causing the trouble. Or you can try shifting to your default theme and check if the error is still there.

2013-09-26

Balanean Corneliu answers:

If you have get this error after some update make this:
That XML error is occuring on the first line of whatever file the feed generator is trying to use, so try replacing files. Save your theme and any other files you've changed and do your upgrade over again. For other person it was worked this solution.


Balanean Corneliu comments:

Do you have a file named feed.php in the main blog folder?

feed.php belongs in the wp-includes folder, not in the main blog folder.

It sounds like you have some misplaced files if you find the feed.php in main blog folder.


Balanean Corneliu comments:

If you have W3 Cache plugin dezactivate for a second and test, that can giving you this problems.

2013-09-26

Francisco Javier Carazo Gil answers:

I have had also this problem and at the end I tried with: http://wordpress.org/plugins/fix-my-feed-rss-repair/ but I was afraid about this plugin editing my files at the end and at the start.

Finally, I did it and all work:http://wejn.org/stuff/wejnswpwhitespacefix.php.html


Charlotte Raboff comments:

I got this error when I tried to activate the plugin:

Warning: copy(/home/d8737/public_html/fix.php) [function.copy]: failed to open stream: Permission denied in /home/d8737/public_html/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php on line 27
There was an error activating the plugin


Francisco Javier Carazo Gil comments:

Try to set the permission of directories to: 777 (or almost to any permission which have execution bit activated).


Charlotte Raboff comments:

It was already on 777.


Francisco Javier Carazo Gil comments:

Have you tried doing this? http://wejn.org/stuff/wejnswpwhitespacefix.php.html