Hi,

I'm receiving the "This webpage is not available." (Error 320 (net::ERR_INVALID_RESPONSE): Unknown error.) on /user/uid page (the viewing mode) The Edit mode works fine. Tested on FF and Chrome as logged in user.

Realname configured to work for Core profile with two fields: First name and Last name (Name pattern is "%1 %2"). Options checked: Show realname in nodes and Show "Not verified" for anonymous users.

The same error I'm getting with the realname-6.x-1.1.

Sincerely,
Alex.

Comments

dlx’s picture

Title: View user profile - "Not available" » Viewing user profile - "Not available"
NancyDru’s picture

Status: Active » Postponed (maintainer needs more info)

Do you have any other modules that might be at play here? I have never even heard of this before.

dlx’s picture

Hi Nancy,

I do have a few modules that could deal with profiles: apply_for_role, autoassignrole, profile_category_weight, profile_permission, profile_role. However, I disabled them all and have the same result - basically, it's a blank page in Firefox on /user/uid page. Chrome gives an error I described in the initial post. Again /user/uid/edit works just fine.

I did notice though a few bugs reported similar to this one in a queue.

Sincerely,
Alex.

dlx’s picture

Update: Actually, apache logs indicate [Fri Jan 30 10:46:19 2009] [notice] child pid 19505 exit signal Segmentation fault (11) on that page.

After disabling realname module everything goes back to normal...

dlx’s picture

Ok, it seems that user_load() on line 146 is causing the problem.

      // Node is being loaded.
      // Save the username that is already there.
      $node->realname_save = $node->name;
      if (!isset($accounts[$node->uid])) {
        $accounts[$node->uid] = user_load(array('uid' => $node->uid));      <<<<<<<<<<<<<<<<<<<<<< Line 146 <<<<<<<<<<<<<<<<<<<<
      }

When it's commented out, profile viewing is fine.

dlx’s picture

Ok, here's what fixed it.

On line 134 I changed the $op parameter from 'load' to 'view'. I'm not sure whether it's going to affect anything else though. I suspect that the Related content listing on the profile page causes segmentation fault if the option is 'load'.

Sincerely,
Alex.

dlx’s picture

Status: Postponed (maintainer needs more info) » Active
NancyDru’s picture

Status: Active » Fixed

Well, let's try it. I didn't see any problems in my testing, and I'm not sure why there should be any.

Committed to 6.x only.

Status: Fixed » Closed (fixed)
Issue tags: -Error 320, -/user/uid

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