No login new users: "The name is being used as the {sitename} guest name."
The name is being used as the {sitename} guest name.
=> after filling in the form on ".../user/3/edit", on email-link to open a new account. The user never gets its password into the system, but in the logfiles/system one can see the user is authenticated. As admin/user1, I'm the only one able to get into the site. I couldn't see this error message anywhere on the internet.
The next error -if I go in that first-time-login-form to the "Name and Address" page ".../user/3/edit/Name and Address"- can be seen on Google only 2 times and related to CiviCRM, no idea if this message has anything to do with my new users login problems:
Sorry. A non-recoverable error has occurred.
The requested Profile (gid=1) is disabled OR it is not configured to be used for 'Profile' listings in its Settings OR there is no Profile with that ID OR you do not have permission to access this profile. Please contact the site administrator if you need assistance.
Also I looked on user management and password policy etc, and couldn't find anything strange that reasonably could be involved in this error. So what to do? If I have to fill in an official bug report, where, as I have no idea if a module-and which one- or the core causes this, or whatever?
Go to the user permission
Go to the user permission section admin/user/permissions
under the civicrm section you will need to give rights to authenticated (and maybe anonymous) with the permission "access all custom data". This should fix your second issue atleast.
finally: YES (tried a lot, but both messages remain)
That didn't work. So I checked some more fields of anything that -to my only very basic knowledge- reasonably could have effect.
+ cron.php + update.php => No effect.
I can see the account and its internally generated password, that couldn't been changed by the user, due to the error when confirming the new user login / password request form.
Unblocked my 2nd account on another email address on the "False Account Detector" (yes, it saw I had the same cooky, by-by!).
But a friend couldn't log-in with exactly the same error, while that is his first account.
Also tried: .../admin/content/node-settings/rebuild
The content access permissions have been rebuilt.
If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Possible causes for permission problems are disabling modules or configuration changes to permissions. Rebuilding will remove all privileges to posts, and replace them with permissions based on the current modules and settings.
Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed posts will automatically use the new permissions.
=> NO; both error messages remain (ofcourse; everytime I ask for a new password again and get a new login link => that logs the user in, but cannot update the internal password, so on logging out, th new user cant get back. Ofcourse if I look-up the internal password and send that to the user, but..)
Then unchecked de CiviCRM module(s) + cron + update => no effect, both errors remain
The databases: civicrm OK, but drupal:
sitename_d1.d1_users
warning : Found row where the auto_increment column has the value 0
status : OK
Auto-repaired database + cron + update => No effect.
Well; the strange thing was that later the CiviCRM was checked-on back again; probably I had a page load error, so it showed like the module was checked-off. Checked-off another time AND YES => thought I saw the same error showing up, BUT NOW I CAN LOGIN WITH THE NEW PASSWORD.
NO: after logging out, again I can't login with the new account. Strange that it first seemed to work.
Now disabling/unchecking all:
* organic group components,
* Bad Behavior,
* False Account,
* MolloM,
* Password Expire,
* Password Policy,
* Persistent Login,
* Secure Pages,
* Secure Site,
* Username AJAX check
=>
The content access permissions need to be rebuilt. Please visit this page. =>
The content access permissions have been rebuilt.
Another time new password => YES: "The changes have been saved." !
=> log-in screen + new (first userknown) password => logged in !
logout, login again => logged in !
logout, clear cookies etc, reload page. login in => YES LOGGED IN !
ANYTONE ANY IDEA WHICH MODULE CAUSES THIS?
(would take me a hell of a job to try all of them + all combinations between them)
Accidently looking on the new modules page http://drupal.org/project/Modules/date :
"January 18, 2009 - Ajax - Due to a fatal error in Internet Explorer 7 in 6.x-1.10 and 6.x-1.11, it is highly recommended that you upgrade to 6.x-1.12." -yes, but I'm using Mozilla mostly...
Same page says to upgrade contrib-toggle 1.11 because of errors in 1.10
same error after core upgrade, but its SECURE_SITE error
"The name is being used as the -sitename- guest name."
Finally most upgrade errors seem to have resolved. But ofcourse, on checking some modules on, this error re-appeared.
Only which module is responsable?
The error includes two issues: it is checking the user name AND it thinks its equal to the "guest name", whatever "guest name" maybe? As I haven't changed "anonymous user" to "guest".
Out of the list I'd removed earlier; I would say that the username AJAX check is the first candidate that applies for those specifics (followed by False Account, that had some minor errors).
SO: un-check "Username AJAX check" (doesn't show up as de-install)=>
Same error: "The name is being used as the ... guest name."
OK, then: .../admin/content/node-settings/rebuild
=> 0 -> 1 rebuild: "The content access permissions have been rebuilt."
=> same error
Ok then: unchecking & uninstalling the false account module (+update, rebuild)
=> same error
Let's delete the whole user-account (of what I cant administer a password, except for the internal given) and start a new account:
(In between I tried to change the pw of my admin/user1 account; gave no problems at all.)
Make new account, wait for email and use loginlink, login with that and try to change password:
=> no, same error
OK; what's next most probable? Organic_groups and password_policy...
First "organic group access control" & "og notifications" unchecked no effect.
Now unchecked the last part of o.g. +civicrm-og-sync that depended on it
+ rebuild permissions to be sure:
=> same error
Then uncheck password_policy & password_expire +rebuild again:
=> same error
Then delete that account and make a new account and try again:
=> same error
See some og modules remaining, lets uncheck og_user_roles first:, together with og_block_visibility &
og_forum, then the last remaining organic group and civicrm modules
=> no effect
unchecking bad_behavior => same error
unchecking Mollom => same error
rebuild permissions again => same error
uncheck persistent_login + permissions => same error
uncheck secure_pages + reb.perm. => same error
uncheck secure_site + reb.perm. => YES YES YES !!!
But not very happy... means I can finally sleep after 2 days.
all other modules back: "secure site" only caused this error
For the record: Bringing all above mentioned modules back except for secure_site, to be sure that this was the only one causing that error. Rebuild permissions. New user & trying to respond to welcome email:
=> YES, everything works now (for another type of new error, I only had to completely uninstall CiviCRM, probably due to a database error or/and integration with organic groups and/or a new o.g. module; will wait till the new civicrm version end Februar).
And I deleted all my cookies, before applying for another user account, as in "false account" module ain't a setting to permit double accounts, only after wards if someone gets through in first instance.
I didn't had the problem with login but the cause is secure site
I had the same strang error and disabling the secure site (wich was not really useful in my case) solve the problem too.
I had the same error but found a workaround for secure site
Here is what worked for me:
1. Grant 'access secured pages' permission to 'anonymous user' (admin/user/permissions)
2. Set 'Guest user' to 'anonymous' or anything non-blank in secure site configuration (admin/settings/securesite)
3. Remove 'access secured pages' permission from 'anonymous user'
Problem solved:
Ciao,
the message "The name is being used as the {sitename} guest name." is inside drupal/sites/all/modules/securesite/securesite.module
(found with 'rgrep "is being used as the" *')
so if you look inside
https://$YOURSITE/admin/settings/securesite
and fill in "Guest access" fields... the problem goes away :-)
ciao
PaoloPì