Wedge

*nods* I have been bitten by that in the past, though normally it's been solved by the main script in the head tag and the specific invocation in the body after the tag already exists.

JS is, really, not my speciality. I can wield it well enough but I don't like it enough to wrangle the finer points. I want it to 'just work', though it is *much* better than it used to be.

I have to admit I did wonder about wrapping it in document.ready() or equivalent but as it seemed to work, I didn't pay it much attention.

Mind you, given that most of the JS I've done for ages has been working with Nao's event handling in Wedge, I tend to forget that somewhat...

There are probably several reasons, related to the number/types/severity of side effects of ibuprofen vs paracetamol, users' reaction to it etc. I just went with it because it was cheaper than paracetamol given that I could get generic ibuprofen vs only branded paracetamol. *shrug*

The importers aren't such a pain to test, generally, and with it there's really only so much that can be done - take the server time offset, factor in the user's own offset and look it up against a list of 'most likely' candidates, and with any luck it'll turn out OK.

I've taken ibuprofen, and I may still be a touch dehydrated though I've had a lot to drink since yesterday afternoon, will have more though to see if it helps.

Also, actually, there will still be an issue with users who come from other systems, but I may be able to fix that by extending the importer, we'll have to see.

That's because I didn't add on the facility to select timezone on registration, which is the next thing I'm doing, or will be doing once this bloody headache shifts.

Once you select it on registration, there really isn't so much of a problem ;)

The default is UTC Dublin if it has nothing else at all to work with, and there's a bug where if you save it, it may reshow UTC Dublin on the next page load even if it isn't using that actual timezone itself.

Works in IE8, though the background's a bit broken. Really, though, if you look in IE, you'll see other JavaScript errors on the page that affect it.

Not sure offhand why it doesn't work in Safari Mobile, but I'd imagine it's related to JavaScript errors again (try turning on Developer Mode there)