Maybe it is all down to me then.. I was in Bristol myself last week!

Thanks for the replies, I'll put it to bed now and have a go tomorrow evening.

Cheers, Moose.

I haven't managed to do any updating yet, but it died seem like it's fixed. As the op can I just thank everyone who has put in the effort to get this fixed.

Cheers, Moose

oops...dreadful spelling mistake there with me writing 'died' instead of does. Blame my fat thumbs and the ShapeWriter keyboard!

Cheers again fellas.

waynemcdougall wrote:

krankyd wrote:We're still investigating and having some trouble reproducing the problem.
If any user is familiar with firebug and can send us (to alpha@waze.com) the log of when such an error happens, it will be very helpful.

I hope @KrankyD isn't implying it's a problem just in this location because it is a global problem (on the world server at least), that started about 24 hours ago.
http://www.waze.com/wiki/index.php/Waze ... _The_World

No, krankyd is just asking for the error logs that result when this problem occurs. Firebug is an add-on for firefox that allows you to view and debug errors in the coding.

I wish he would pop back in here and answer martynhodder's question about what information they need. I've installed firebug and I'm pretty computer savvy but I've never used it before, if they would just tell me what information they want I could certainly post and send it.

FWIW, it's not just a world server problem. I'm experiencing the same errors on the www server.

Yeah, that code up there was just the HTML for the error report. Doesn't really help.

Maybe that's why I'm having difficulties and was hoping for direction... I was looking for a javascript error but was having a hard time finding one.

Of course, that could be because I've never used firebug before. Still wishing for krankyd to return and provide some direction.

RightTurnOnRed wrote:I just emailed you what I'm getting in my Firebug log when the internal server error happens.

Would you mind posting it here for us to see? Email is definitely the best way to get support to respond... but I'm curious about where the error lies as well.

The Fej wrote:OK - USA server updated as well.

Thanks! Working well for me so far.

krankyd wrote:We're still investigating and having some trouble reproducing the problem.
If any user is familiar with firebug and can send us (to alpha@waze.com) the log of when such an error happens, it will be very helpful.

I hope @KrankyD isn't implying it's a problem just in this location because it is a global problem (on the world server at least), that started about 24 hours ago.
http://www.waze.com/wiki/index.php/Waze ... _The_World

unwallflower wrote:

waynemcdougall wrote:

krankyd wrote:We're still investigating and having some trouble reproducing the problem.
If any user is familiar with firebug and can send us (to alpha@waze.com) the log of when such an error happens, it will be very helpful.

I hope @KrankyD isn't implying it's a problem just in this location because it is a global problem (on the world server at least), that started about 24 hours ago.
http://www.waze.com/wiki/index.php/Waze ... _The_World

No, krankyd is just asking for the error logs that result when this problem occurs. Firebug is an add-on for firefox that allows you to view and debug errors in the coding.

Yes, but that doesn't clarify whether he appreciates the scope of the problem.

It started about 24 hours ago (36 at most), is worldwide, and is trivial to reproduce. The forums are full of people reporting the problem. Asking for debug logs seems disengenious to me. Waze broke something just over a day ago. They should be looking at what changed over a day ago.

unwallflower wrote: I wish he would pop back in here and answer martynhodder's question about what information they need. I've installed firebug and I'm pretty computer savvy but I've never used it before, if they would just tell me what information they want I could certainly post and send it.

Agreed. You will notice a pattern that Waze HQ drops into a forum, makes a post, and never returns again for followup.

But I don't actually think Firebug logs will help. It's pretty clear that its borked at the server end - it's not a Javascript error or anything. All we're going to get is the post like the one above - there was an error. No diagnostic codes. Nothing useful.

Still if we're told how we can help with Firebug, we certainly will.

They can reproduce the problem here by turning this into an 8m roundabout

http://world.waze.com/cartouche/#?zoom= ... =110226197

unwallflower wrote: FWIW, it's not just a world server problem. I'm experiencing the same errors on the www server.

Thanks for that.

Copy of email sent to alpha@waze.com

Dear Waze

About 2000 UTC 31 Oct problems started occurring on the Cartouche editor on the World server. The same problems are occurring on the WWW server but I can't confirm they started at the same time.

The problems all seem to be with junctions. Adding junctions, deleting junctions, creating roundabout, setting connectivity.

@KrankyD asked in one forum thread for a Firebug trace. One very smart user, and also me, can't figure out just what we need to do to give you what you want. I also suspect that you won't get anything useful. It's not a Javascript error - we just get back messages about the Waze server had an error. It should be easy to reproduce:

1. Try creating a roundabout (8m) here:
http://world.waze.com/cartouche/#?zoom= ... =110226197
2. Try creating a roundabout here
http://world.waze.com/cartouche/#?zoom= ... FTFFFFTTTT
3. Try deleting a junction here
http://world.waze.com/cartouche/?zoom=8 ... 1=96400728


Discussed in these forum threads:
http://www.waze.com/forum/viewtopic.php ... 080#p48080
http://www.waze.com/forum/viewtopic.php?p=47994#p47994
http://www.waze.com/forum/viewtopic.php?p=48010#p48010

http://www.waze.com/wiki/index.php/Waze_Service_Status