On Mon, May 24, 2010 at 03:25, Philip Olson <phi...@roshambo.org> wrote: > >> >> I can't get the errors locally, Considering we already throw away a >> LOT of errors regarding xinclude when things go wrong >> (print_xml_errors()), I can only suggest excluding the warnings from >> the xinclude() call in configure.php. > > I don't remember exactly why these errors were hidden before, maybe Hannes > remembers as he committed them.
We don't care about xi:include errors. If they fail then we haven't lost anything - because the data didn't exist to begin with. IIRC we decided that the xi:fallback was useless because we didn't wan't to say "no inherited methods" (or something along those lines), so we simply ignored xi:include errors. The same thing applies to the new xi:includes, although I don't know why they generate different error string. -Hannes
