We’ll be rolling out a patch to address a number of bugs shortly:
- exception when leaving a game before it is started by the creator
- incorrect session count in page footer
- broken encoding for special characters
- removal of www from http://www.weewar.com
The site will be down for 5-10 minutes.
12 Comments
Hooray for bug fixes! Keep up the good work, guys!
Thanks a lot! We’ll get there :)
seems nice and snappy this morning! yay!
This is not a bugfix but a suggestion. Can we have the ‘send e-mail when ready’ turned into a label with a ‘for’ attribute? It’s a small thing but would make a huge difference :) Keep up the good work fellas!
Here’s another suggestion: Instead of deciding to kick someone off after the time has elapsed, it’d be cool if you could just skip them. That way, they’re penalized, but they don’t totally lose out.
That’s a great suggestion SaintArved. And would be especially useful, what with some of those more triggerhappy. How about it weewar, can we make this happen? Something like a forced skip a turn instead of the boot?
I still can’t get in to the site, and its been a day already. Is it just me?
Please use either Tangler or the contact form to make and discuss suggestions. There are quite a few threads on this specific one already.
@selalerer This sounds like a caching issue. Try reloading the page you see at weewar.com in your browser (not using the refresh link but the browser’s reload function.)
ps @sans “send e-mail when readyÕ” will be a proper label after the next update
The E-mail notifications are definitely not working correctly since the last update. I used to get them every time through Gmail, but I haven’t gotten a single one since the last patch. I have already added the proper address to my contacts to insure the notifications aren’t spam filtered.
Thanks Alex, will share feedback there instead And superthanks for the label!
@Matt Looks like you were right. It seems that some of our servers were not sending emails which did not show as our tests happened to run on those that did. It should be fixed now. Sorry for that!