Sie sind nicht angemeldet.

1

Montag, 24. Dezember 2012, 14:06

XML parsing failed for HTML5 after encrypting

Hello,

"XML parsing failed" error shows when loading vtour in HTML5 mode after xml file is encrypted with Encryption Tool in krpano Protect Tool 1.0.8.15 (build 2012-10-05). In FLASH mode with encrypted xml file vtour works fine! In HTML5 and FLASH mode with non-encrypted xml file vtour also works well!!
Please help, how to resolve this issue?

Kind regards!

2

Montag, 24. Dezember 2012, 18:37

No encryption for HTML5.

3

Montag, 24. Dezember 2012, 19:34

No encryption for HTML5.

Thank you for the reply!

Until now, I've thought that's the only way to protect xml for HTML5. So there's no xml protection in HTML5?

Beiträge: 1 857

Beruf: Virtual Tours - Photography - Krpano developer

  • Nachricht senden

4

Montag, 24. Dezember 2012, 22:02

Encryption works fine to HTML5, you just need to use the HTML5 compatible type.
Click the right checkbox.
KRPano Developer: Portfolio ::Gigapixel Tagging Solutions - Porfolio 2 :: Facebook :: Twitter :: reddit.com/r/VirtualTour

5

Montag, 24. Dezember 2012, 22:10

Encryption works fine to HTML5, you just need to use the HTML5 compatible type.
Click the right checkbox.
If you mean "Use HTML5/Javascript compatible encryption (xml, swf, js files only)" by the right checkbox it doesn't help in my case also!

Beiträge: 1 857

Beruf: Virtual Tours - Photography - Krpano developer

  • Nachricht senden

6

Dienstag, 25. Dezember 2012, 01:17

Then use valid xml. Google xml validator or open the xml with firefox.
KRPano Developer: Portfolio ::Gigapixel Tagging Solutions - Porfolio 2 :: Facebook :: Twitter :: reddit.com/r/VirtualTour

7

Dienstag, 25. Dezember 2012, 09:18

Then use valid xml. Google xml validator or open the xml with firefox.
These are the results from the "http://schneegans.de/sv/" XML Schema Validator:

--------------------------------------------------------------------------------------------------
XML Schema Validator
Location:
Redirect:
Well-formed:YesValid:NoHTTP status code:
HTTP Content Type:
HTTP encoding:
XML encoding:utf-8Used encoding:utf-8Public Identifier:
System Identifier:
Validated as:

  • No schema was found.
  • Your document lacks a namespace declaration such as '<html xmlns="http://www.w3.org/1999/xhtml">' on the document element.
  • Only well-formedness constraints will be checked, while validity constraints will be ignored.
--------------------------------------------------------------------------------------------------

Now, does anybody know is schema supposed to be found and what is that thing about lacking a namespace declaration on the document element?

8

Dienstag, 25. Dezember 2012, 10:32

!! I've found out that encrypting "tour.xml" file from "...\krpano-1.0.8.15-2012-10-05\examples\virtual-tours\demotour-weingut" also reproduces the same error when loading in HTML5 !!

You can all download "krpano Viewer 1.0.8.15" from "http://www.krpano.com/download/download.php?file=krpano10815" so please check it!

Beiträge: 1 857

Beruf: Virtual Tours - Photography - Krpano developer

  • Nachricht senden

9

Mittwoch, 26. Dezember 2012, 17:09

I'm unable to duplicate your results. The encrypted version works perfectly for me.

To find out what you're doing wrong, you'll need to show your steps or provide a link to your project.

My steps were..

open krpano Protect Tool.exe
Click encryption tool tab
Check box Use HTML5...
Add files
navigate to tour.xml for the tour you mentioned.
open tour_html5.html in safari.
KRPano Developer: Portfolio ::Gigapixel Tagging Solutions - Porfolio 2 :: Facebook :: Twitter :: reddit.com/r/VirtualTour

10

Donnerstag, 27. Dezember 2012, 12:42

I'm unable to duplicate your results. The encrypted version works perfectly for me.

To find out what you're doing wrong, you'll need to show your steps or provide a link to your project.

My steps were..

open krpano Protect Tool.exe
Click encryption tool tab
Check box Use HTML5...
Add files
navigate to tour.xml for the tour you mentioned.
open tour_html5.html in safari.
Hi!

Great, you gave me a clue! It works only in Safari!!
In the latest versions of Firefox and Google Chrome it does not!
See what I was doing and the error in the Firefox <https://www.dropbox.com/sh/yxd8k0507thj550/rUaajTRlgX>

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »macfac« (27. Dezember 2012, 12:54)


Beiträge: 1 857

Beruf: Virtual Tours - Photography - Krpano developer

  • Nachricht senden

11

Donnerstag, 27. Dezember 2012, 16:03

The html5 part doesn't even work in Firefox, so don't worry about it there.
It's a good note for Klaus anyway because it's a strange error. Also the error will dissappear, if you set the user agent to IPAD for example. Then you get to see the html5 display but fail to render properly.
KRPano Developer: Portfolio ::Gigapixel Tagging Solutions - Porfolio 2 :: Facebook :: Twitter :: reddit.com/r/VirtualTour

12

Freitag, 28. Dezember 2012, 10:30

Dear sachagriffin,

Thank you very much for your help! *thumbsup*

If I was a Mac user, not Windows user, than Safari would be my default Internet browser and I wouldn't even notice this error. Anyway, in my case, HTML5 works fine in Firefox if "tour.xml" file is not encrypted. I also hope that Klaus is now aware about this issue.

Kind regards!

Beiträge: 1 857

Beruf: Virtual Tours - Photography - Krpano developer

  • Nachricht senden

13

Freitag, 28. Dezember 2012, 20:08

You're absolutely right. I just updated FF to the latest version and html5 works fine but will not decode encrypted xml properly.
KRPano Developer: Portfolio ::Gigapixel Tagging Solutions - Porfolio 2 :: Facebook :: Twitter :: reddit.com/r/VirtualTour

14

Samstag, 29. Dezember 2012, 14:17

Hi,
Anyway, in my case, HTML5 works fine in Firefox if "tour.xml" file is not encrypted. I also hope that Klaus is now aware about this issue.
Yes - I'm already aware about that problem, there were also some other posts about that.

The problem is a Firefox-limitations - when the content of an xml element is larger than 4096 byte (easy for encrypted xml files where everything is stored inside one xml element), then the Firefox Browser internally splits-up this element into several smaller ones.

The next krpano release already contains an internal workaround for this case.

Best regards,
Klaus

Ähnliche Themen