Page 6 of 16

Re: New Waze Map Editor version - Feedback

Posted: Mon Apr 09, 2012 9:28 pm
by foxitrot
foxitrot wrote:
shirlig wrote:2. Fix order of drives in archive.
Drives incorrectly marked as "Today" or "Yesterday" - could this be fixed as well?
I've possibly caught the last minutes of the old WME's era, sorry. The new one seems to not display an incorrect "Yesterday" at the same drive.
AlanOfTheBerg wrote:Am I really the only one who cannot access WME at all in Chrome/Win7? This is really odd. :?
No, me too (if it counts). All black background, one unreadable UR, after zooming-in deep enough the black background disappears, coordinates around 0.0,0.00; one short (ID:152482945) and one 5 000 km long (unselectable) segments nearby (displayed red after long load time), no permalink entry, archive with hundreds of empty pages. That's all on recent Chrome/Win7 x64.

On Mozilla it runs fine.
rleejr79 wrote:I was just able to log in w/o any issues. Win 7 64-bit, Chrome used here.
Lucky you!

However, I'm able to use WME correctly on other Win 7 x64 machine with the same Chrome 18.0.1025.151 :shock:

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Tue Apr 10, 2012 8:43 am
by foxitrot
WME does work for me correctly on the NA server, with e.g. the AndyPoms' mentioned permalinks. But it is still completely black on the INTL server.

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Tue Apr 10, 2012 4:49 pm
by foxitrot
AlanOfTheBerg wrote:My problem could only be resolved by clearing all cookies as well. It appears that WME should have been prompting me to log in, but it didn't, so I wasn't able to access resources necessary which were requiring credential information.

This looks like, to me, a bug whereby a login is required but it is not asked for.
Sounds plausibly. I'll try to find and delete the responsible cookie.

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Tue Apr 10, 2012 5:23 pm
by foxitrot
foxitrot wrote:
AlanOfTheBerg wrote:My problem could only be resolved by clearing all cookies as well. [...]This looks like, to me, a bug whereby a login is required but it is not asked for.
Sounds plausibly. I'll try to find and delete the responsible cookie.
Login:

Code: Select all

Name:	USERAUTH
Contents:	QJoJe5NqKOcWhJtNDHTwKM0uyWhqEMOmsyo%2Bs6fqSAWXtm6AP80%2D
Domain:	world.waze.com
Path:	/
Send for:	Any connection type
Accessible for Script tag:	Yes
Created:	Tuesday, 10. april 2012 18:40:34
End of validity:	Wednesday, 10. april 2013 18:40:34
Its removal caused a log in being required in WME, then it got re-created. WME remains black
---
Finally I've found the culprit: a cookie named (loosely translated) "Local data storage"

Code: Select all

Origin:	https://world.waze.com
Size on disk:	7,0 kB
Last modification:	Monday, 9. april 2012 1:48:59
Delething this followed by a WME page refresh caused it to be recreated with

Code: Select all

Origin:	https://world.waze.com
Size on disk:	3,0 kB
Last modification:	Tuesday, 10. april 2012 19:09:37
and WME was not black anymore!!! :!:

(BTW, the www.waze.com's version of this cookie already was 3 kB in size.)

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Fri Apr 20, 2012 10:20 am
by foxitrot
foxitrot wrote:And one more - why again me? :cry: Am I blessed? :P

The roundabout at Hospital de San Pedro, Logroño, Spain is just being edited by conductor77(0).

Well, after few minutes, conductor77 feels no need to give any (at least empty) street+city name to the segments - the roundabout remains red.
BTW, the roundabout remains still red - conductor77 is not a thorough editor :roll:

So, once again, someone started to tamper with a roundabout in France, Saint-Genis-Laval, on Avenue du Général de Gaulle and I've been thrown there from Slovakia with the well-known "The highlighted roundabout does not form a circle" error message. As the target place opened, the roundabout was away, just the connecting segments were visible. During next minutes the user jefffg(0) was modifying the adjacent streets' segments and finally replaced the roundabout with a simple set of four partially curved segments.

Devs, please please, take finally a look into the throwing issue...

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Mon May 28, 2012 1:25 pm
by foxitrot
I've already modified a few segments' red connectivity arrows to green, saved - and the junctions' neighboring segments do not carry any note about the changes being bade - the "Updated by" keeps the previous editor and time-stamp. Makes me worrying again - the connectivity changes are again not traceable down to a particular editor.

Waze promised to have fixed all connectivity setting bugs a couple of weeks ago, this is apparently something new in the recent editor version (679, from 23.5.2012).

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Tue May 29, 2012 6:02 am
by foxitrot
petervdveen wrote:
gettingthere wrote:There is no insight into who has modified turn restrictions. We have asked Waze to add this visibility (at least for the last modified turn for a junction) but they have not.
Since the last update (world server) the connected segments that got changed turn orange when changing a junction.
This changes the edit date and editor of the segments.
Peter, take care, do not rely on it - it used to work like this for a couple of weeks, but since a few days ago, upon some arrows' changes, only the junction node turns orange - subsequently no adjacent segment gets visibly modified (date/by) after a save.

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Tue May 29, 2012 7:56 am
by foxitrot
gettingthere wrote:
petervdveen wrote: Since the last update (world server) the connected segments that got changed turn orange when changing a junction.
This changes the edit date and editor of the segments.
How do you know which of the two junctions connected to the segment have changed?
Sure you do not. If you encounter any sudden problems in routing through a node, you can be at least sure (according to the date), that 'something' did change and you can at least assume, which direction to look for... Otherwise you can just scratch your head - "Damn, it worked here yesterday!"
gettingthere wrote:How do you know that the junction and not the segment itself had been changed?
Sure you do not. Our way of thinking is currently limited to segments, because the nodes have no visible properties (except that no/some/all turns through are enabled). It's Waze's turn...
gettingthere wrote:This is not a proper solution...
Aren't we already (mis)used to this habit, while editing Waze maps? ;)

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Tue Jul 10, 2012 8:36 am
by foxitrot
Indeed, happens again and again. (Or green and violett paths, going e.g. in opposite directions, where the UR author remembers there was at least a couple of minutes' difference between the paths???)
And Support never ever responded to the notifications.

Re: Map Editor version (April 9, 2012) Official Feedback

Posted: Tue Jul 10, 2012 10:31 am
by foxitrot
True. We've also been talking a lot about misdated URs in the past.
ATM the URs are such anonymized and delayed, that often not even their author remembers, whether all is correct there... :D