With the latest WME beta version I'm seeing repeatable cases of being logged out and forced to log back in while editing in an WME beta tab.  The only script I have running is Wazebar.  There are two screen shots provided below. The first shows the console where Wazebar has paused execution on debugger.  Typically, what I have done on the map to initiate this part of the Wazebar script is to pan across the WME map and sometimes followed by selecting a segment or venue.  After allowing the script to complete (I do this by closing the console) I am then logged out of WME.  This has happened a couple dozen times since I started using the newest version of WME beta.  I cannot duplicate in production.

I'm using Chrome.

Console screenshot:

https://prnt.sc/cGL-0imSWahO

https://prnt.sc/cGL-0imSWahO



Next thing that happens after allowing debugging to complete:
https://prnt.sc/IIOFv70COZkX


This is not an emergent request.  I just want to let you know.

Thanks.
 

n4dog wrote:Thanks for the updates. Still wish there was some way to run this on top of other webpages. That would be Sweet. Thanks Again for your Script work.

Or to float at the top of the browser window when the page is scrolled.

JustinS83 wrote:

mudge42 wrote:I cannot add HNs when WazeBar is enabled. Anyone else having the same problem? (Chrome, Mac)

Wazebar interacts with WME absolutely 0, so in theory this shouldn't be possible. Unless it is an issue caused by elements shifting due to Wazebar taking up 20 pixels at the top of the screen.

I have the same issue with HNs. Cannot add them when Wazebar is active. Turn off Wazebar and I can add them. Turn Wazebar back on, can no longer add them.

karlcr9911 wrote:Hi...Could you add a 1/2 second to 1-second delay...

+1 to that request!

There is no Mark Read when the filter option is used to limit to a certain state. Clear the filter then the Mark Read appears.

ramblinwreck_81 wrote: ↑Mon Nov 28, 2022 2:35 pm With the latest WME beta version I'm seeing repeatable cases of being logged out and forced to log back in while editing in an WME beta tab.  The only script I have running is Wazebar.  There are two screen shots provided below. The first shows the console where Wazebar has paused execution on debugger.  Typically, what I have done on the map to initiate this part of the Wazebar script is to pan across the WME map and sometimes followed by selecting a segment or venue.  After allowing the script to complete (I do this by closing the console) I am then logged out of WME.  This has happened a couple dozen times since I started using the newest version of WME beta.  I cannot duplicate in production.

I'm using Chrome.

Console screenshot:

https://prnt.sc/cGL-0imSWahO

https://prnt.sc/cGL-0imSWahO



Next thing that happens after allowing debugging to complete:
https://prnt.sc/IIOFv70COZkX


This is not an emergent request.  I just want to let you know.

Thanks.
 

 

I'm also experiencing being persistently logged out with Wazebar running in Beta.

Mike nailed it - happens with every hard refresh and even happens if I change something in settings (like compact mode) in the Waze Sidebar.

The usual thanks for awesomeness...

I may be a loner in thinking this useful, but could there be a click/hover on the Server Update status, to show a dropdown of the last five or ten (?) updates? I would find this useful in troubleshooting/responding to URs from the recent past, when changes have been made in the meantime.

Could you add the INTL map update and maybe user config for waze forums/threads (I would like to add the unlock thread for Spain, for example)?

jm6087 wrote: ↑Wed Mar 08, 2023 11:09 pm I believe this is a long time issue due to WME Beta logging out regularly.
 

 

Ryan described it as having to log in even if he just refreshes beta WME.  I'm running Wazebar and not having the same experience.  @ramblinwreck_81  said it was with only wazebar running.  Didn't happen without it.

I think this is something that may be harder to track down since it does not affect everyone equally.