Postponed (maintainer needs more info)
Project:
XML sitemap
Version:
7.x-2.1
Component:
Other
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Jan 2015 at 13:06 UTC
Updated:
30 May 2016 at 08:57 UTC
Jump to comment: Most recent
Comments
Comment #1
dave reidIt usually means you have some PHP file getting included that has an empty line before the opening PHP tag like the following:
Search for this and you'll find the cause. It's not the fault of XML sitemap module itself.
Comment #2
nick.thorley commentedDave Reid
I read something similar but drupal has a masssive amount of php code and files and its like trying to find a needle in a haystack. Are you able to provide any suggestions of a command or method where I could at least narrow the issue down to a module or even better file. Bar going through each php file I cant see another way
Nick
Comment #3
dave reidhttp://stackoverflow.com/questions/1943727/find-all-files-with-blank-or-... is the biggest help
Comment #4
jlea9378 commentedI encountered this same problem as well. I believe the problem was a bunch of blank lines at the end of my theme template.php.
Comment #5
gunnm commentedjlea9378 - you are a genius (not to belittle the other contributors on this page, but your comment is a life saver)! I've struggled with this problem for the past few hours, and the issue was indeed due to an empty line in my theme template.php. In my case the opening line was blank - removing the blank line solved the problem.
As a side point it is worth noting that as this is a relatively infrequent issue, it makes sense that it is not linked to a php issue with a common drupal module. Theme templates are an obvious variable between users.
Comment #6
michaellenahan commentedThis excellent comment in the helped me to track down the problem on my site:
https://www.drupal.org/node/175137#comment-1526410
In your module.inc file (in the includes folder) add this after the drupal_load function in the module_load_all function
print $module.'|';
Reload the site in your browser. You will see a long list of modules.
Focus on the module which starts the second line in the list - in my case that was the module that was causing the problem.
Comment #7
alexander.nachev commentedLovely :))). This helped me out find the damn SPACE in front of <?php that broke my xml. Thank you so much!!!