I should have backed up my site but I didn't. In any case, I went to the module page and enabled the module. That ended up giving me "500 Internal Server Error" module. Now I have no idea how to fix it. Can I go directly into the database and make some changes to make the site accessible? Or what are the major changes this module makes to the underlying files? May be I can go in there and delete certain lines. Pleaseeeeeee help.

Site: http://wisemusings.com

NOTE: There is no bandwidth issue

Comments

GlobalRaj’s picture

GlobalRaj commented

Well, I deleted the "realname" folder under the module and the site seems to be working for now. But it's kind of frustrating as I wanted to check out this module.

GlobalRaj’s picture

GlobalRaj commented
Status: Active » Closed (fixed)

I think I figured it out. I had "Name" module installed and enabled. There seem to be a conflict of that module with this one. When I disabled the "Name" module completely, I was able to enable the "RealName" module and didn't get the error message. Learned something through trial and error method.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Title: Just enabling the module has rendered my site inaccessible » Compatibility with Name module
Status: Closed (fixed) » Active

That should get fixed. #1275618: Compatibilty issues with RealName

alan d.’s picture

alan d. commented
Status: Active » Fixed

Should be fixed in Name Field 7.x-1.4.

Recursive loop due with Token generation

Name: In hook_tokens, reload user object as object is not always correctly loaded
RealName: Load user tokens during hook_user_load

Cheers for reporting this!

alan d.’s picture

alan d. commented

PS: If you have a second to check that the implementation of hook_user_name in the name field module is compatible with realname. I tried to make this transparent to either module without a dependency to either

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

alan d.’s picture

alan d. commented

Hopefully this is still being tracked.

I was not checking the field names in the newly provided tokens for the name field "name-FIELD-NAME" and this caused an issue the token "name-raw". I've fixed and commited to dev, but noting this here to give you a heads up in case someone pings your queue. See #1649458: Notice: Array to string conversion in token_replace() (line 102 of /.../includes/token.inc).