ditchi56 wrote:I think you are unduly cynical.

Perhaps, though having seen so many seemingly unnecessary changes being made behind the scenes of WME (and now Livemap, which also appears to have bitten Waze's own coders in the arse), I can't help but be just a *tiny* bit cynical/sceptical as to the reasons behind them, nor can I help but wonder how good WME could be right now if all the effort spent on rolling out yet another UI redesign had been channeled into coding core functionality.

Mmm, been getting weird routing errors to the domain, although a trace to the server itself works fine. Will raise a ticket with my hosting co. if it hasn't stabilised by bedtime...

dknight212 wrote:Not sure they've done it again to you:

Actually, that's probably one of the same problems I fixed in the latest URO release - I'd forgotten WMEOD plays with the livemap link... I'm guessing you saw this in the beta?

Twister-UK wrote:Mmm, been getting weird routing errors to the domain, although a trace to the server itself works fine. Will raise a ticket with my hosting co. if it hasn't stabilised by bedtime...

The IP for my shared server was changed yesterday, so now we just have to wait for that change to propagate across the DNS servers... Everything should be up and runnng again "soon" (and hopefully that's a real-world soon as opposed to a Waze-type soon )

This is getting tedious... 24 hours after being told it'd take a couple of hours to resolve, routing to my domain is still borked, and a follow-up ticket has been raised. Oh well, at least they didn't say it'd be fixed "soon".

I'd been checking the routing via Virgin cable and EE mobile, plus via a handful of online traceroutes around the world, and all of them were failing in the same way, so whatever was causing the delay doesn't appear to have been my local DNS cache (which I'd wiped as part of this testing anyway...).

Anyhoo, whether it was the result of prodding my hosting company again or purely coincidental, routing now seems to be up again - I can reach my server both from my phone and from my work PC, and the online traceroutes are also able to find it OK. So fingers crossed we're back in business.

Now that the production WME is using the same codebase as the recent beta, 2.2 is required to allow the livemap link to be updated according to the current editing location...

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: https://chrome.google.com/webstore/deta ... mdbdnmcfei

2.3 restores operation in the latest WME Beta

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/137249
Chrome packaged version: https://chrome.google.com/webstore/deta ... mdbdnmcfei

It's that time of the year again... the OS have just released the latest update to their streetname dataset, so expect a corresponding WMEOD update "soon" (i.e. just as soon as I get the raw data downloaded, pummelled into shape, and copied onto my server)

WMEOD is a script I wrote to search the Ordnance Survey street and place name data for possible matches when a road segment is selected in WME. Every 6 months the OS release an updated copy of the street name data, and the latest update arrived at some point in the last few days... In order for WMEOD to use the data, it first needs to be processed to chop up the single UK-wide data file into smaller chunks that the script can handle, then uploaded to my server so the chunks can be accessed by the script.