Space doesn’t matter, except when it does.<\/p>\n
The other day Koha bug 11308<\/a> was filed reporting a problem with the public catalog search RSS feed. This affected just the new Bootstrap theme.<\/p>\n The bug report noted that when clicking on the RSS feed icon, the page rendered “not like an rss feed should”. That means different things to different web browsers, but we can use an RSS feed validation service like validator.w3.org<\/a> to see what feed parsers are likely to think.<\/p>\n Before the bug was fixed, the W3C validator reported this:<\/p>\n This feed does not validate. Of course, at first glance, the XML declaration looks just fine — the key bit is that it is starting at the second<\/em> line of the response.<\/p>\n Space matters — XML requires that if an XML declaration is present, it must be the very first thing in the document.<\/p>\n Let’s take a look at the patch, written by Chris Cormack, that fixes the bug:<\/p>\n This patch moves the But why should importing a TT module add a blank line? By default, Template Toolkit will include all of the whitespace present in the template. Since there is a newline after the Awkward, when spaces matter.<\/p>\n
\nline 2, column 0: XML parsing error: :2:0: XML or text declaration not at start of entity [help]
\n<?xml version=’1.0′ encoding=’utf-8′ ?><\/p><\/blockquote>\n\r\n--- a\/koha-tmpl\/opac-tmpl\/bootstrap\/en\/modules\/opac-opensearch.tt\r\n+++ b\/koha-tmpl\/opac-tmpl\/bootstrap\/en\/modules\/opac-opensearch.tt\r\n@@ -1,5 +1,5 @@\r\n-[% USE Koha %]\r\n \r\n+[% USE Koha %]\r\n [% IF ( opensearchdescription ) %]\r\n
[% USE Koha %]<\/code> Template Toolkit directive from before the XML declaration to after it. [% USE Koha %]<\/code> loads a custom Template Toolkit module called “Koha”; further down in the template there is a use of Koha.Preference()<\/code> to check the value of a system preference.<\/p>\n[% USE Koha %]<\/code> directive, that newline is included in the response.<\/p>\n