XML parse error after upgrading to pr15

zbooy · March 30, 2018 at 12:27 AM

Hello,

I have just tried to do the upgrade from pr14 to pr15 but without success.
I'm including a config file in my xml, like this:
<include url="list.xml" />
The included file is loaded from http://zbooy.pl/giga/list.xml and looks like this:

It's just a basic config file that worked just fine until today; now it stops with the XML parsing error.
The file passes XML validation, of course. If I omit the include, everything else is OK.

I have reverted krpano,js to pr14 and everything is working again. Any ideas?

zbooy

jeromebg · March 30, 2018 at 9:32 AM

Add krpano tags :

zbooy · March 30, 2018 at 11:15 AM

Thank you very much, this did the trick!

It is certainly stated in the docs:
<krpano>
This is the main / root element of a krpano xml file.
All further xml elements need to be defined within this element.

Although it seems this was not enforced until pr15 version.

zbooy

spacerywirtualne · March 30, 2018 at 11:44 AM

Hello zbooy

I recommend remove a dblclick.js plugin. It is blocked by adblock.

best regards
Piotr

klaus.krpano · March 30, 2018 at 10:08 PM

Hi,

that's related to this change in version 1.19-pr15:

Quote

Improved xml parsing error checking for all browsers.

Some browser were 'silently failing' on some invalid xml files - that means where was no error on the xml parsing, even if there should have been one. So to check such case there is now also a check for a <krpano> xml root element - and normally there should have been always one there ;-).

Quote from spacerywirtualne

I recommend remove a dblclick.js plugin. It is blocked by adblock.

Right, the name 'dblclick' is also used by some ad-scripts and therefore blocked by ad-blockers.
But simply renaming the file should already work.

Or better - use a xml-only solution for double-click support:
https://krpano.com/forum/wbb/inde…74482#post74482

That solution works also on touch-devices and avoids some browser-compatibility problems.

Best regards,
Klaus

zbooy · March 30, 2018 at 10:11 PM

Ah yes, now there is a native ondoubleclick event so no need for the plugin. Removed; thanks for the suggestion

Participate now!