AlanOfTheBerg wrote:What country are you trying to edit?
AlanOfTheBerg wrote:The editor was down for the last 24 hours or so due to an upgrade. If you didn't know that, keep an eye on/subscribe to status.waze.com.
I would go check in to the UK forums to see what issues might be present at this time. I am not personally aware of any lingering issues. The road images are going to be slow for many hours while the new servers build up their cache of road images in memory rather than creating them with each request. When the same upgrade was done in the US, there was also some changes required to the caching to get them to perform as expected. It will likely be a few days before the system stabilizes as they get all the settings tweaked the way they need to be.
Timbones wrote:I've not heard of any other editors having problems editing in the UK. Here are some suggestions of things to try:
Hope that helps...
- Make sure you're on the right server: https://world.waze.com/editor/ /!\
- Don't use Internet Explorer - Firefox or Chrome are recommended
- Disable any addons, plugins, ad blockers, etc
- Check that the Roads layer is turned on
- If you're having problems selecting roads, turn of the Landmarks layer
- Clear out your browser cache
davipt wrote:I've said before, for me it has nothing to do with scripts, only see it on Firefox not on Safari (yet), and happens when zooming in and the road reload happens, and I've seen it only today (which means it may be a couple of days, didn't spend much time editing yesterday)
AlanOfTheBerg wrote:davipt wrote:PhantomSoul wrote:Is anyone with Safari 6 and Mac OS 10.8 (Mountain Lion) having any trouble getting the permalinks to capture selected road segments? Last night while requesting some unlocks to resolve various UR's in my area, I noticed some inconsistent behavior with it, in that it sometimes included the selections and other times didn't.
Do you have any extensions? For example I hardly get the segments selected when using the highlights extension, have to look at the code to understand why
This is either an issue with the highlighter code or JNF code in WazeBar. The same code affects Chrome, too.
Users browsing this forum: No registered users