Quote from: rthrash at May 21, 2008, 09:47 AM
Thank you Soshite ... we’ll start testing soon on this end ... wow what a log of updates! 
Most of these were mainly misspellings, or unforeseen issues like the rare UTF-8 stuff. Only a few were critical ones (basically the ones pixelchutes posted xd).
Thank goodness there wasn’t nothing that completely brought down the script (well, save that user corrupting issue, if you happened to have a user put specific stuff in there).
EDIT: I forgot to mention that I am planning on using that JS IE fix pixelchutes posted in the Bug Reports topic in the final v1.3.1 release. IIRC, that was solely an IE fix, so I’ll need to make up documentation to apply it just for that browser. The "normal" JS file was fine for other browsers, right, or was pixel’s JS for every browser?
Also, I’ll be adding documentation on a rare absolute lang path issue (where the user needs to direct WLPE to the the file directly, instead of through MODx) that will stop the lang strings from appear at all, as well as a workaround to get checkboxes to control images (until v1.4.0 is released, where Scotty will add HTML capability for form fields) --- this is useful in getting badges, achievements, etc. for your WLPE install. Lastly, I’ll have documentation reminding people about which form fields needs to passed in when you have a "minimal" form (such as just a checkbox for certain data, outside of the normal profile editor) --- else WLPE "nukes" everything --- although I think pixelchutes might have fixed this bug, so I’ll have to test and see if that’s still the case.