rragan Posted February 23, 2017 Report Share Posted February 23, 2017 i did a cache title search with Cachly and imported it into Geosphere. The import failed with the error shown in attachment. I then recreated the list of caches in Geosphere and imported them into Cachly to see how the error is handled. It fails in the same way but there is no information to let me know the cache with the bad text so I can avoid it. Showing the problem entry helps a lot. Better yet would be to report the offending entry and continue the import with the next cache. The way you process the XML may prevent doing this. Curiously, I can load the cache in both apps and export ok. Only the import fails. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted February 23, 2017 Report Share Posted February 23, 2017 Excellent suggestion about adding additional error information in the error message. Here is what it will look like: 6 hours ago, rragan said: Better yet would be to report the offending entry and continue the import with the next cache. The way you process the XML may prevent doing this. Curiously, I can load the cache in both apps and export ok. Only the import fails. It wouldn't be easy to skip just that cache as the XML Parser is what bails on error. This is an XML spec error with invalid characters, so it only applies to XML and doesn't affect anything when normally viewing the cache in Cachly. Quote Link to comment Share on other sites More sharing options...
thebruce0 Posted February 23, 2017 Report Share Posted February 23, 2017 Yes it would be tedious to fix problem characters in an xml as you'd have to edit it to something else, then parse it again. It could happen any number of times until the parser successfully loads the entire file. It'd be nice if it were possible to skip invalid character errors, but that opens a whole can of development worms Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted February 23, 2017 Report Share Posted February 23, 2017 2 hours ago, thebruce0 said: It'd be nice if it were possible to skip invalid character errors, but that opens a whole can of development worms My take on this is to fix the errors as they come in from users so that it isn't an issue for all other users. There are many invalid characters that we currently clean before exporting to XML, so reports like this are extremely useful. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted February 23, 2017 Report Share Posted February 23, 2017 Finally fix the parsing error in that cache. The problem was an invisible unicode character, 0x1f. Hooray for invisible things. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.