Menu
▾
▴
#70 can't load saved data
I'm using 0.3 beta 3 and can not load saved scoreboard, teams, pages or all data that I have saved. When I try to load them or merge the I get
"Problem accessing /LoadXml/merge. Reason:
Error on line 1: Premature end of file."
The scoreboard seems to lag if I've been using it for a lot of scrimmages and need to reset everything. So being unable to reload data it's a lot of work to rebuild everything.
thanks Bill Larkin "Mr. Wizard Fort Myers Derby Girls"
Discussion
Anonymous
Can you attach one of the saved docs that you get an error while loading?
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
here's a copy of the file. I found it seems to be a problems with firefox chrome seemed to work tonight. What of the memory leak reported in chrome.
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
I had this happen just last weekend after pre setting everything prior to the bout. I have a master xml with all my teams, logos and graphics etc. before each bout I use this file then delete what I don't want and save it to my bout folder.
I had to completely close Firefox and the exe then re open using chrome and make the adjustments and save.
Once this is done, chrome can be closed and ff reopened and it will be set perfectly. I'm thinking it may be something java related?
I have found also that the refresh on chrome isn't really consistent and ff works a lot more reliably.
Prince Harming
Perth Roller Derby
Last edit: Anonymous 2013-03-18
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
yes that's what I found too. thanks
Has this been happening with Chrome? If so, have you tried Firefox? I have found a bug (since mid-Jan 2013) that has been causing widespread problems when using Chrome with the scoreboard. It's detailed in [bugs:#72]
Related
Bugs: #72
Sorry, I did find where this was happening. I assume you were using Firefox? It seems to handle form.submit() differently than Chrome; the code was clearing out the input:file element immediately after submit(), which worked in chrome (or at least it used to), but in firefox it looks like the actual submit() is delayed, and it no longer has any file to upload. I changed the code to simply not clear the input:file element so it now appears to work in Firefox. It will be in the next 0.3.0-beta release (which hopefully should be very soon, as soon as I can fix bug 72).