Bug found – will be solved in next release.
[code]1.4.3.6
Fix: Bug with popups in Firefox
Update: these highlights are now available to all users:
- Roundabouts which may cause issues
- Unconfirmed turns
- U-Turns
- Reverse Connection
- Dead-end loops
[/code]
Am I correct in understanding that the “Split road” function is available from Rank 1?
Is there any chance we could get that bumped up to Rank 3 editors (or higher) only? In NA, we’ve tended towards unsplitting roads and we’re constantly having to correct newbies that think a curb between the two directions is enough to have a split road – if it was easily done through a script, we’d have a lot of work to undo!
Thanks!
^^^ it’s not that kind of splitting. Maybe cutting (into 2) is a better description for it.
It adds a node in the middle. 
send from my SGS4, using Tapatalk
Thanks… I guess I should have tried it first.
Perhaps we could get it renamed? I know this is nitpicky, but a “split road” is one that divides a two-way street into two one-way streets.
So how should I rename it ? 
“Divide segment”
“Add junction node”
“Halve segment”
all work in my mind, and don’t confuse the “split” road.
‘Cut segment’ or ‘add node’ comes to my mind.
send from my SGS4, using Tapatalk
1.4.3.7
Fix: False positive alerts in internal debugger
Update: "split road" renamed to "cut segment" to avoid confusion
TypeError: Cannot read property 'attributes' of undefined
at WMETB_TriTab (chrome-extension://ihebciailciabdiknfomleeccodkdejn/scripts/WME_Toolbox.min.js:1:28200)
at Object.WMETB_NewPopupCheck (chrome-extension://ihebciailciabdiknfomleeccodkdejn/scripts/WME_Toolbox.min.js:1:70829)
at Object.OpenLayers.Events.OpenLayers.Class.triggerEvent (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:91:5046)
at Object.Waze.SelectionManager.OpenLayers.Class.itemsSelected (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:20:30562)
at Object.OpenLayers.Events.OpenLayers.Class.triggerEvent (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:91:5046)
at Object.Waze.Control.SelectHighlightFeature.OpenLayers.Class.select (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:16:4940)
at Object.Waze.Control.SelectHighlightFeature.OpenLayers.Class.clickFeature (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:16:2918)
at Object.OpenLayers.Handler.OpenLayers.Class.callback (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:187:982)
at Object.OpenLayers.Handler.Feature.OpenLayers.Class.triggerCallback (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:279:2439)
at Object.OpenLayers.Handler.Feature.OpenLayers.Class.handle (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:279:1964)|https://www.waze.com/editor/?zoom=7&lon=-121.1012&lat=38.71912&layers=2021&env=usa|dbraughlr|4|Chrome 35
TypeError: Cannot read property 'consecutive' of undefined
at Object.WMETB_NewPopupCheck (chrome-extension://ihebciailciabdiknfomleeccodkdejn/scripts/WME_Toolbox.min.js:1:70856)
at Object.OpenLayers.Events.OpenLayers.Class.triggerEvent (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:91:5046)
at Object.Waze.SelectionManager.OpenLayers.Class.itemsSelected (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:20:30562)
at Object.OpenLayers.Events.OpenLayers.Class.triggerEvent (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:91:5046)
at Object.Waze.Control.SelectHighlightFeature.OpenLayers.Class.select (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:16:4940)
at Object.Waze.Control.SelectHighlightFeature.OpenLayers.Class.clickFeature (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:16:2918)
at Object.OpenLayers.Handler.OpenLayers.Class.callback (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:187:982)
at Object.OpenLayers.Handler.Feature.OpenLayers.Class.triggerCallback (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:279:2439)
at Object.OpenLayers.Handler.Feature.OpenLayers.Class.handle (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:279:1964)
at Object.OpenLayers.Handler.Feature.OpenLayers.Class.click (https://www.waze.com/assets-editor/javascripts/OL-7c8a3b7f.js:279:1070)|https://www.waze.com/editor/?zoom=7&lon=-121.1012&lat=38.71912&layers=2021&env=usa|dbraughlr|4|Chrome 35
I had to prohibit the page from popping up more errors.
1.4.3.7
Autofix unconfirmed turns: It should stop changes after 150 accumulated changes to enable the user to save those 150 and align with the 150 max credited changes per save. Then the user can select that operation again to capture another 150 max until they are all fixed.
Autofix reverse connections: I have seen cases where at zoom level 100m/500ft the button says there are none to fix (but you can see them on the screen). Then zoom in to 100m/200ft and it fixes them. It is not the same as when you zoom out to 200m/1000ft when you get the message you cannot use this function at this zoom level. I cannot find an example to permalink yet that has not already been fixed now.
When did that came in? Or is it L6 only and not visible to me?
EDIT: found it already on oyyodams.com (toolbox 1.3.3.9 as an L6 job)
Hi,
This bug occured on a roundabout, but I don’t see any roundabout here: https://www.waze.com/editor/?zoom=7&lon=-121.1012&lat=38.71912&layers=453&env=usa
Can you tell me how it happened exactly ?
1.4.3.8
Update/Fix: Highlight segments with or without house numbers is now based on data sent by WME. Internal computing is deprecated and not accepted by Firefox anymore.
There should be no more alert with Firefox using house number highlight. If some segments that should be highlighted are not, and reverse, it’s a bug of WME that doesn’t send the good data.
Bug report: Openstreetmap permalink doesn’t work.
The OSM url contains /?lat=<ok>&lon=<ok>&zoom=NaN&layers=M (both beta and stable versions).
With <ok> I mean the proper values.
In WME I’m here while trying: https://www.waze.com/editor/?env=row&lon=12.42948&lat=43.87115&layers=389&zoom=8
Thanks again for this wonderful tool!
Thanks. It’ll be fixed in next release.
False positive bug:
If you have “Highlighter City” script installed, Toolbox reports a false positive bug. The bug comes from “Highlighter City” and is reported here: https://www.waze.com/forum/viewtopic.php?f=819&t=78774&start=30
I just got this error
TypeError: Cannot read property 'last' of null|TypeError: Cannot read property 'last' of null
at Object.Waze.Action.CreateRoundabout.OpenLayers.Class.splitSegment (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:5:23428)
at Object.<anonymous> (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:5:23170)
at Array.forEach (native)
at Object.Waze.Action.CreateRoundabout.OpenLayers.Class.modifyIntersectingSegments (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:5:23101)
at Object.Waze.Action.CreateRoundabout.OpenLayers.Class.doAction (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:5:20758)
at Object.Waze.ActionManager.OpenLayers.Class.add (https://www.waze.com/assets-editor/javascripts/WME-a665068d.js:4:6166)
at WMETB_Redo_RoundAbout (chrome-extension://ihebciailciabdiknfomleeccodkdejn/scripts/WME_Toolbox.min.js:1:38628)
at HTMLImageElement.<anonymous> (chrome-extension://ihebciailciabdiknfomleeccodkdejn/scripts/WME_Toolbox.min.js:1:95371)
at HTMLImageElement.lt.event.dispatch (https://www.waze.com/assets-editor/javascripts/libs-83b4735a.js:2:4916)
at HTMLImageElement.y.handle (https://www.waze.com/assets-editor/javascripts/libs-83b4735a.js:2:1603)|https://www.waze.com/editor/?zoom=6&lat=-36.62487&lon=174.66194&layers=1413&env=row|ispyisail|6|Chrome 35
Hmmm I can’t reproduce it. After the error, has the roundabout been rebuilt ?
sorry about that.
Thanks for looking into it.