karlcr9911 wrote:

karlcr9911 wrote:Live users (even with the layer on) cannot be seen in WME at the moment.

Confirmed in Chrome and Firefox - no scripts and confirmed with other editors.

Still no live users showing as of this morning.

dmcrandall wrote:We did. The stock response is now "ask Frebola. "

Spelling errors are courtesy of large thumbs and a small smartphome keyboard.

crazycaveman wrote:I've come across a PUR from avsus (staff editor responsible for ads, I believe) that looks like it's meant to merge two user created Taco Bell's (PURs to update one and delete the other). I do find it interesting that they want the address removed, though. Does this mean merge functionality might actually work sometime "soon"? Has anyone else come across similar PURs?

citeman wrote:

ohad-ron wrote:Hey everyone, a new editor version is here.

Changes:

• Fixed issues with duplicate house numbers on disconnected segments

I'm not sure that this is fixed. I was trying to move some house numbers on this segment:
https://www.waze.com/editor/?env=usa&lo ... ts=4608027
When I went to save I got an error window saying: "Some house numbers are invalid. You can fix them and try to save again. If you are certain they're correct - force them." When scrolling over the the red highlighted house numbers it indicates, "Number already exists". The numbers I'm trying to move are 1508 and 1512 (1506 is supposed to be 1508, but I changed it trying to diagnose the problem and now cannot change it back). I cannot find a duplicate house number anywhere in the selected area; nor could I find one several miles up or down stream.

I will admit that Pacific Coast Hwy goes through lots of cities and somewhere along the way it could duplicate, but shouldn't the City name be taken into account and not trigger a duplicate error?
On a somewhat related note, when you try to force them, you get the same error; therefore, it puts you into a error loop and the only way to exit is to not save changes.

[EDIT]- Just thought of something, could the duplicate error be coming from an alternative street name? Meaning if the alternative name matches it would block the duplicate number. In this case the alternative name (SR-1) virtually runs the entire length of the state.

taco909 wrote:

PesachZ wrote:It is also checking against residential places (which act like house numbers but are not tired to the closest segment). Search nearby for a residential place with the same street address.

???????
We can't have a HN that duplicates a Place or a Place that duplicates a HN?

Durango48 wrote:Hi,

during a reload or permalink all layer settings are saved.

But not the new "road experimental". This must be re- activated.

Should that be so? And if yes, why?

Regards, Thomas

top_gun_de wrote:

AlanOfTheBerg wrote:

top_gun_de wrote:After pressing F5, the changes are saved, but the current position in WME is gone.

On this point only, this is the wrong way to reload the current map position.

Actually, the reload-button in the upper right corner is not working at that time, neither does the Permalink-button in the lower right corner function. So, what would you suggest? Besides, what do you think of the problem itself?

Regards,

Detlev

taco909 wrote:

tonestertm wrote:It would actually be nice if unconfirmed app closure submissions were a different color, altogether, like yellow. That way, they'd stand out, and call attention for editors to confirm.

Excellent idea.
Suggest it on Centercode and I'll vote for it.