Login fails at groups.drupal.org
jayseye - November 4, 2009 - 17:22
| Project: | Drupal.org infrastructure |
| Component: | groups.drupal.org |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi, I'd like help resolving errors which prevent me from logging into groups.drupal.org :
"You are not authorized to access this page"
"The name jayseye is already in use. Please contact the site administrator."
These errors prevent me from contacting the administrator at groups.drupal.org to resolve the issue. I'm a member of several groups and would like to change my notifications.
Help in resolving this would be greatly appreciated!
Thanks,
Drupal.org username: jayseye
#1
Please submit the form at http://groups.drupal.org/node/add/account-synch
#2
Submitted the synch request and the problem persists. What can I do to facilitate a fix? Thanks!
#3
The procedure is manually done; that means it can take some time, before to be done, especially because it is a problem common to many people.
#4
This issue still "needs work" until it is actually "fixed". Being a common problem only increases its importance.
Would you please either leave this issue open, or explain why you think it should be marked "fixed" when that is clearly not the case?
Thank you.
#5
greggles has already answered you by telling you what to do; that is the reason I re-marked the support request as fixed: it has already gotten an answer.
#6
@jayseye: You have to understand there's nothing that most of us drupal.org administrators can do now. There are only a few people (can count on one hand) that can actually admin groups.drupal.org and fix the sync requests. If we left everyone's issues open for g.d.org syncs, it would pollute our trackers. Don't assume we're rebuffing you when we're setting this to fixed, but everything that can be done with regards to us has been done. You filled out a sync request, and one of the few, volunteer, unpaid g.d.org admins will get to it when they can. They have to fix them all by hand in the database and all of them have real jobs and can't do this 24/7.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.