New issue 28 by nicole.mordecai: Posters do not survive snapshots
http://code.google.com/p/openwonderland/issues/detail?id=28
What steps will reproduce the problem?
1.Create a poster
2.Create a snapshot
3.Restore world from snapshot - poster will not appear
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
I tried this in an empty world and the posters reappeared just fine,
including text.
What server and version was this?
Comment #2 on issue 28 by jonathankap: Posters do not survive snapshots
http://code.google.com/p/openwonderland/issues/detail?id=28
Confirmed that this worked after updating the server. Possibly due to an
old version
of the module.
Comment #3 on issue 28 by jonathan...@gmail.com: Posters do not survive
snapshots
http://code.google.com/p/openwonderland/issues/detail?id=28
Reopening the bug:
https://groups.google.com/d/topic/openwonderland/UyhNfUwCG98/discussion
To reproduce the problem :
- Create HTML poster with accents in the content
- Create a snapshot
- Restore world from snapshot - poster will not appear
This bug seems to apply to to the snapshotting of any cell containing
non-ascii characters. For example, create any cell and give it an object
name that contains a non-ascii character. If you try to snapshot the cell
it appears to silently fail.
I have been investigating this issue - so far there does not seem to be a
problem with International characters in the content - HOWEVER if the
object is named with international characters or with some special
characters the object will not be reloaded from the snapshot. The file
with the content is there, but cannot be read. The Darkstar server reports
500 error and there is a URISyntaxException error in the web server log.
Can you post the stack trace from the web server? It sounds like something
needs to be URI encoded.
I think the URL encoding code isn't handling international characters
right. Maybe try replacing the call to encodeSpaces() here:
With:
urlPart = new URI(null, null, urlPart, null).toASCIIString();
If that doesn't work, the encodeSpaces() method could use a regular
expression that replaces all non-ascii characters with "_" or something.
I have done a bit of digging here too and it seems to me that there is also
a problem at writing time.
I create a poster in world, modify the name property to contain a
accentuated character, and when I create the snapshot, the poster is not
persisted inside /wfs/snapshots/timestampxxx/world-wfs
If I copy a Poster.xml file into that same folder and then change the name
to an accentuated character with a text editor, the file exists when the
snapshot is restored (in the object properties the name appears funny, but
it's there).
This seems to be different to Bob's error with the wall card, where the
filename is not handled properly. In my case it is the name attribute in
the xml file that has the international characters, as opposed to being in
the file name, and the problem (or the main one) is at writing time.
I have done a bit of digging here too and it seems to me that there is also
a problem at writing time.
I create a poster in world, modify the name property to contain a
accentuated character, and when I create the snapshot, the poster is not
persisted inside /wfs/snapshots/timestampxxx/world-wfs
If I copy a Poster.xml file into that same folder and then change the name
element in the xml file to an accentuated character with a text editor, the
Jose - I have seen this as well but with special characters that are
illegal in file names. What OS were you working with?
Jonathan - your suggested fix works for my test case where the file is
present in the snapshot directory but was unable to be retrieved due to the
encoding problem. Will continue investigating what Jose is reporting.
Hey Bob, those tests were done in Linux.
Comment #15 on issue 28 by jonathan...@gmail.com: Posters do not survive
snapshots
http://code.google.com/p/openwonderland/issues/detail?id=28
Bob to try to reproduce