It is public forum part 
I’ve noticed that the WME generates save errors, whenever trying to connect anything to Walking Trails or Railroads. Is anyone else experiencing that?
When I’m create new segment, near Ural rocks for example, WME put Poland instead Russia in country field. And makes it permanent. It’s very annoying.
YES! Not connected to the new version, though - it’s been happening for a couple of weeks. As far as I can see, it is not possible to perform any action that splits a railroad segment.
The workaround is to change the railroad to street, join another segment to split it, then change it back to railroad. This works without having to save in the middle. 
Love the feed. Can’t wait for the next iteration of the WME.
There are some things I do not like each other in the foreground the URS. You should have a window to gain access to this information.
The save bug I see is probably related to this: (all 38 errors are server response codes)
When changing the state (US Server), I am presented with extra states that aren’t even remotely near where I’m editing. In this example, I’m editing west of Batesville, MS, but am being offered Tennessee and Arkansas (~40 miles away) and Georgia (~200+ miles away) as state options.
Hi Guys!
The 46 years issues was fixed in beta and will be deployed to Prod. next version.
Looking into the rest of your great feedback.
Last night alt had the same behavior as ctl to select multiple segments, only selecting the segment specifically clicked on, rather than all segments between the 2 clicked segments. This was for segments with identical names/elevation/lock/SL.
Thanks,
Its better, but there are still some issues.
[i]Hello 
I’ve been using the new version, tell them you have a lot of mistakes that make quite tedious editing, apart from keeping URs foreground (which deemed unnecessary), there are problems with the writings do not work well, I had no trouble shitting the roads and satellite images, when saving the work is crazy giving error, there is a window open all the time ship sends you to review the validator and if you do it appears another sending do more things. I think it should be better debug versions before removing the general public.[/i]
:shock: I’m glad it was no trouble but I hope you can still sit down :lol:
Google Translate? 
Yes hahahahaha I’m sorry
Enviado desde mi I9700 mediante Tapatalk
There are problems loading the satellite images
Loading of satellite image and road tiles almost always happen for a while after a major update. Especially when Devs push small bug fix updates throughout the week.
It will take a while for that issue to “resolve”.
Waze recently launched a new update of WME, which generated lots of expectations and inconvenience to different publishers in the community, as they had to make the launch in conjunction with the updated editing tools, as the Toolbox and WME WME Validator and different script to lessen the impact.
I just hope that the team responsible for waze updates take this experience for future updates to the editing platform.
On the other hand very well include filing URS in the editor but must pose a pull-tab for that display and not directly in the edit screen. For Editors’ choice whether they displayed and instantly made.
Regards.
Waze is in no way responsible for ensuring scripts created by us are not broken. The updates/changes that the developers do will never coincide with the scripts/extensions. The authors/creators of the things like Toolbox and Validator are given the opportunity to “try” and make sure the next update won’t break it with beta access.
There is no way the developers will ever make sure the scripts work with every release as it’s not important to them or has any relation to how the editor operates.
When a major update rolls out, especially with big changes to the UI, the creators of the scripts tend to go one of two ways.
- They are on it and try their best to keep up with the major changes to the code, testing non-stop until it’s fixed.
- Wait till a majority of the updates are rolled out so they can then work on it.
The issue with #1 is that the devs have bugs that need to be fixed. If a script creator applies a fix and the devs roll out another update, it could kill the script again. Some don’t want to go through the hassle of constantly chasing fixes until the flow of updates slows down. This could take at least a week or two. They do their best and they know it.
What makes this extremely bad here, is that not only are editors being offered “Tennessee” as a choice (halfway across Arkansas to the west). But it is being placed in the state block as the DEFAULT choice. You only SEE Arkansas if you click on the block.
Older editors are used to this in areas close to other states (MO over into NE Okla, etc). But this is a new problem for Tennessee to show far into Arkansas.
The same thing happens in México, I think it is caching cities/states where you edited, I was adding cities to our country in those states, the correct state was Sonora (StateID# 1700008):
