we actually use in production, this mostly consists of the "new style" support
for raw data passthrough, but does not fix the actual problem (which is dealing
with url "double" encoding/decoding - or rather the loss of information about
that) yet...
Will fix that and sync up exactly with the production code for MW 1.19 soon...
user preferences in MW pos 1.18 got moved to a seperate table and only stuff
that is _NOT_ default should be stored there. Despite what the documentation
says actually having data left in user_options is harmful and will break
random functionality like preference handling