However, since these errors seem to be cropping up all over the place, I will attempt to gather the most common ones here. Keep an eye for updates, and I warn you: these answers will be frank.
Error Type: 181 (Client request data did not match the session. This may indicate an attempt to hijack this login session.)
This bug should be solved! See this thread for more information.
If you do encounter this error, please follow the instructions for reporting a bug found at the bottom of this post.
You can attempt to resolve this several ways.
- Go to http://www.acen.org/...tion/logout.php. You may get an error message there, but disregard it.
- Clear your browser's cookies.
- For Firefox: Tools | Options | Privacy | Show Cookies. Either click "Remove All Cookies" or type "acen" and remove those cookies.
- For IE7: Tools | Internet Options | Browsing History | Delete... | Delete Cookies... and click "Yes".
- For Opera: Tools | Advanced | Cookies. Either type "acen" and remove those cookies or select all of them and hit "Delete".
- For Safari: ...sorry, I'm not going to reboot into my Mac side to figure this out. I'm sure it's similar, and that someone will post it below.
- For Firefox: Tools | Options | Privacy | Show Cookies. Either click "Remove All Cookies" or type "acen" and remove those cookies.
- Sometimes you need to close your browser and re-open it.
- Sometimes you need to just come back to it.
In order to prevent this bug from hitting you in the future:
Make sure you log out when you have finished. Not only is this more secure and good practice, but it will prevent this bug from striking in the future in most cases.
Believe me, we're working on this bug. We know it's there. We know the error message is scary. Personally, I've lost over 50 hours of my life to this bug, over 24 of that in one go. We're testing a patch right now to see if we can get rid of this, but since this bug comes and goes, it's hard to set up the correct testing environment. Please be patient with us as we work on this.
Error Type: 101 (An illegal parameter was passed to the "Attempted to get illegal key 'payend' from class 'L_BadgeType'." function.)
This bug should be solved!
If you do encounter this error, please follow the instructions for reporting a bug found at the bottom of this post.
If you were subject to this bug:
Please PM me with your badgetype, badge number (or login name), and real name and I will restore your badge.
Error Type: 105 ("We're sorry, but this browser is not supported by Limon due to problems with its implementation of cookies, javascript, or rendering engine. Supported browsers include Firefox, Safari, Opera, and Internet Explorer 7. We're working hard to support as many browsers as possible, but for right now you'll just have to use one of those to access your registration account (if you already registered) or create a new one (if you haven't). We apologize for the inconvenience.)
As this bug says, you're accessing this page with a browser that is not supported. Everyone should have either IE7 (Windows 2000 and above), Safari (Mac OS X), or Firefox (you Linux types) installed or installable. Note that IE6 is not supported. Yes, we know that some employers only have IE6, and we're sorry that we can't support it at this time. Its implementation of javascript, cookies, and rendering engine are not compatible with Limon and getting the program up to full functionality is higher on our priority list than dodging around the quirks (such a charitable word) of IE6.
IE7 has been tested on three operating systems (2000, XP, Vista). Firefox has been tested on six operating systems (XP, Server 2003 (don't ask), 98SE (yeah, that's right), Tiger, Leopard, Ubuntu). Safari has been tested on Tiger and Leopard. Opera has been tested on XP only. We have heard rumors that the Wii browser is supported. I can confirm that the Safari included with the iPhone/iPod Touch is supported. I recall that the AOL browser is supported. I do not know if Opera mobile is supported. No, you cannot use lynx. (If you're using curl, well, you shouldn't have any problems understanding this error message; go download and compile Firefox.)
Error type: 0 (Zend Session is read-only.)
This is a known bug and is on our list of things to fix. For right now, it's perfectly harmless, though we're not sure exactly what's causing it.
In order to work around this bug:
- Hit 'back' and log in again. The error should clear up.
"I get an error that says there's a 'security certificate error' or a 'domain name mismatch'... something about 'trying to connect with acen.org but the certificate presented belongs to *.acen.org'. Is there a security risk here?"
No, there is not a security risk here. ACen's SSL certificate recently changed to allow subdomains, but the original link for the registration site specified acen.org instead of www.acen.org. In short, if you use https://www.acen.org/registration/, you will not run into any problems.
"I tried to pay/join a group/register/pay for my group but I got a blank white screen! What happened? Will I be charged?"
To get quite technical, this error occurs when there is a parsing error in the programming. This can be as a result of a mistyped line of code, or a new debugging statement we've put in to chase down a bug. We try to avoid these as much as possible but it's not always feasible to catch them all (especially since working with an IDE isn't always possible for some debugging situations). We do test our scripts before we put them up, but sometimes these errors still sneak in there.
If you encounter this error, you should PM me or Riker, following the instructions at the end of this post. The sooner we know about it, the sooner we can get it fixed. As for whether the charge will go through or not, it's impossible to say in every case, but I can definitively say this: If the charge did go through, the system will know this and you won't be charged again. If the charge did not go through, well, you haven't been charged for anything, so there's no harm in paying again.
"How do I know when I've paid?"
If you can "Get Confirmation" when you log in, you have paid successfully. If you check your badge info, you will see your badge's status. "Paid and pending" means that your badge is paid but your order has not yet been processed by the Registration department.
"When will badges be mailed?"
According to this thread, the answer from the Registration DH is "sometime in April." He also asks that you bear with us while we try to avoid last year's mailing fiasco. Mailing thousands of badges ain't easy, guys. Also, he'd appreciate it if you don't bring up last year; he's trying to get out from under that even though he didn't have anything to do with it.
Update: The first batch of badges has gone out. You may or may not be among this first batch, but beware that PMing us to ask where your badge is will not result in it being mailed faster. The badges are coming via first class mail, and all badges belonging to a group will be sent en masse to a group leader, probably the group leader who paid.
Please hunt around the forums before you PM someone with your question. There are many threads on the badge mailing here and one may be able to answer your question. Don't forget that you can search the forums for your topic as well.
If you live in Canada: If you did not PM someone about your postal code, please PM Tevva or send an e-mail to acenreg08 AT gmail DOT com.
If you live in Estonia: You rock, dude. Your badge should be on its way soon. Awesome props for getting a badge mailed to Estonia.
"I haven't gotten a confirmation e-mail!"
Check your spam folders, and you may find it there. I've confirmed that these e-mails are indeed going out.
In any case, if you need a confirmation at any time, you can log in and choose "Get Confirmation" from the menus on the left.
"I forgot to check that I wanted my badge mailed!"
We should be rolling out a fix that lets you change this yourself soon. If you've already paid, well... I think you're out of luck. You can always e-mail acenreg08 AT gmail.com and ask if they'll take the extra $1.50 to add it even though you're paid, but no guarantees. If you haven't already paid, PM me with your badge number. I'll do what I can. And please, next year, look out for it.
"When are concert tickets going on sale?"
Registration does not answer questions that aren't directly related to registration, because we don't want to give out misinformation. This question, for example, is best asked of the Main Programming department. There is a forum for each [external] department at ACen; please direct your query there. If you're not sure where to direct it, the general forum is where you want to go.
See also this topic for more information.
"OMG your program sucks it never works and I can't believe you wouldn't make it work for me this sucks."
This isn't a great way to get support for your problem, and believe me, there's nothing worse than reading posts where people trash something you've been working on for eight months, sometimes at a very high priority, sacrificing sleep and other obligations for. I'm happy to help and I know the program isn't perfect (yet), but I can't help someone who is rude to me and my work (and my partner's work) and won't even tell me what the problem is. Therefore I ask you to be polite; we're just as stressed that something we made isn't working correctly. We know what's at stake, and we try to work quickly; insulting us will only make us less eager to put your bug high on our list of things that need to be solved.
If you have a bug to report, please PM me with:
- your badge number
- your login name
- your browser (IE7, Firefox, Safari, Opera, etc...)
- your OS (XP, Vista, Leopard, Ubuntu, OpenBSD, etc...)
- what you were doing when you found the bug (how could I reproduce it?)
- approximate time of the bug
- did you receive an error message, and, if you did, what was it?
I hope this covers a lot. I will attempt to keep it updated.
(Edited! Added a question about non-registration questions. Added a topic jump too.)
(Edited! Added a snide remark about people who use curl.)
(Edited! Added a question about getting an SSL error.)
(Edited! Added a way to prevent the dreaded error 181 from occurring in the future in most cases.)
(Edited! Added a question about confirmations.)
(Edited! The dreaded 181 bug is solved. Keinahora.)
(Edited! Added a question about Error 0.)
(Edited! Added a section about the dreaded white-screen problems.)
(Edited! Cleaned up and clarified some other sections.)
(Edited! Was able to personally confirm that the iPhone/iPod Touch browser is compatible with the registration system.)
(Edited! Added a bit about the 101 bug and proper responses to it.)
(Edited! Badge mailing has gone out!)

Sign In »
Register Now!
Help
This topic is locked


MultiQuote





