A new WME version was released. Here is a list of what’s inside:
Walking Trails - ENABLED
This will allow you to connect walking segments to a drivable segments with a “phantom” node without affecting routing negatively. You can start connecting them but are not yet fully supported in routing.
New Turn UI - ENABLED
This new turn UI should be a click saver, easier to use especially for new users and will help us to add additional functionality in the future.
New Permission system - ENABLED
User rank 1 will be able to change a max of 30 street names within per day
Updating primary/alternative street name is both counted. Changing both is counted as 2.
User Rank 2 will be able to delete a max of 10 segments within per day
Deleting your own segments is not limited, but still counted toward the total limit of 10. For example, the user deletes 5 segments other owns, now deletes 5 segments he owns. He can continue deleting his segments but not others.
Search Component:
*Improvements in the search component
*Search results on venues search displays venue names w/o cities - FIXED
*Translations allowing to change the order of HN,Street,City,State,Country in dropdown display mode
Alternate street name selection list is in ALL CAPS - FIXED
Warning on switch to HN mode after undoing all changes - FIXED
Segment editable in HN interface - FIXED
RPP can be saved as area - FIXED
Edit restrictions when selecting several segments - FIXED
WME freezes when trying to add a new segment after split - FIXED
Segment editor doesn’t appear in practice mode - FIXED
TIO can’t be modified on junctions with small angles - FIXED
Map comment messages invisible to lower rank editors - FIXED
Named segment shows as Unnamed (after performing specific steps) - FIXED
Thai translations - ENABLED
Update Translations
This release includes a refactor in the way that the front end and back end interact with each other. There are a few things to look out for here:
Please make sure to update your browser to the latest version.
We are looking into possible issues on Internet Explorer.
Please note that this WME release may well “break” a large number of scripts.
Script authors almost certainly need to make some internal changes to their scripts.
If your favourite script fails with the new version of WME, by all means politely inform the script author on the relevant topic.
Glodenox has created a “shim” script that will probably resurrect scripts that are failing at the moment. You can read more details and find that script here.
There seems to be a problem accessing WME via Firefox since this update - it starts to load, then something kicks in a few seconds later and redirects to https://www.waze.com/500.html. This happens even in a private window with no scripts running. Using Chrome on the same PC/network connection, WME loads just fine.
I’m not sure this is the change the release notes are referring to - it’s only been a few days since we were given an assurance that the Waze object would be retained for a while longer to give us time to fix our scripts, and it does indeed still appear to all be present and correct in this release.
Correct - the Waze object has not yet been removed - we were told we would have two months in order to get all scripts updated for this major change.
That being said, there were some behind the scenes changes and several functions were removed so there could be scripts negatively affected (Magic is one that is affected, not sure of others yet).
Yes, the last few beta releases have required the latest version of Firefox. Since I was on the ESR version (52.6), WME was broken for me as well. I downloaded the latest non-ESR version (58.0) and WME works on it. Whatever broke WME on older versions of Firefox has also broken it on Edge.
Ah, that’d be the problem then - using ESR on my work PC, but I usually don’t use the beta editor here so I hadn’t already noticed there was a conflict between the latest WME code and ESR…
And once again a new incomplete feature is being released to the PRODUCTION WME… :roll:
Why on earth did you think it was a good idea to release a function that RUINS the routing?
Great work with the new Turn UI! Much easier to edit turns now, especially since hovering wasn’t the most accurate thing. Even works great without having to worry about angles.
I know elsewhere senior editors have complained about junior editors not being able to see some settings since they can’t change them. It looks like that has bled over to closures - junior editors can no longer even select the closures tab if the segment is locked above their rank. We’re moving backward with this concept.
When removing RTCs, WME still shows the RTC is in place until you do a soft refresh. I also am having trouble deleting multiple closures(on a single segment) at once. If I hit the delete closures and apply to all option, it only deletes one closure.
If you’re using URO+ to provide the delete all button, this functionality is currently broken due to the individual closures not being correctly removed by WME itself, and if you’re using some other script to provide the same functionality, it wouldn’t surprise me if it’s also struggling to cope with this incorrect WME behaviour…
