Fatal error: Unsupported operand types modules/user/user.admin.inc on line 697

By estevan_carlos on 22 Jan 2011 at 16:04 UTC

I'm unable to access the permissions area within the People section of the admin in Drupal. In case I'm doing something or in case there's an easy fix, I thought I'd ask. Anyone else have this issue? I haven't been able to find this issue listed elsewhere. Although I may not fully understand how to navigate the issues areas of these modules, etc.

Comments

Anybody have any advise on this one?

kjv1611 commented 7 March 2011 at 03:49

I got the same issue - NO issues on a Beta release test site, but I've got the same issue on a new site, and this is using the supposed to be "stable" release.

Any thoughts - anybody?

dodgy module?

John_B commented 7 March 2011 at 08:37

I had the same this morning, it cleared up after I deleted module soundmananger2 (which anyway in the dev version was generating a warning and could not be disabled via the UI).

For completeness I mention I also deleted module contemplate, but I have no reason to suspect it.

So maybe not the fault of the stable release of Drupal, in my case it was my risk as I was running a dev module.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

Same here. Drupal

gezzbanger commented 18 April 2011 at 14:01

Same here. Drupal 7.0
'admin/people/permissions' is white screening and php logs show the error message as above;
Fatal error: ....modules/user/user.admin.inc on line 697.

Anyone have any ideas on debugging the source??
Thanks, I'm kinda stuck without permissions.
I guess its a case of switching off modules one by one.

Thanx.

Buggy module beacon9_social

gezzbanger commented 18 April 2011 at 14:11

Buggy module 'beacon9_social'.

In my case I got "Fatal

cajmcmahon commented 30 August 2011 at 15:03

In my case I got "Fatal error: Unsupported operand types in /modules/user/user.admin.inc on line 696" after I installed and activated Open Web Statistics (7.x-1.x-dev).
Seems it might be a bug in the case of OWS: http://drupal.org/node/1228286#comment-4926166

OWA

mcmayer commented 21 September 2011 at 04:43

Had the same problem and in my case it was the OWA module 7.x-1.0-alpha2 that needed de-activating.

Agree

caseyhewlett commented 17 January 2012 at 15:37

I can verify this solution. It could be that OWA can't handle the way the user is configured for this page. So it kind of shrugs its shoulders and screws up everything.

Agree

epe commented 11 March 2012 at 16:51

deactivated the owa module and the error is gone.
also, the owa module if activated and the site details are filles in, it doesnt have any function e.g. accesses are not being counted.

Bug was reported

wranvaud commented 3 June 2012 at 04:08

There's a bug report for this problem http://drupal.org/node/1228286 (it just happened to me)

Please can any one help me I'm unable to access my permission

Checdedon commented 13 December 2011 at 00:29

Please can any one help me I'm unable to access the permissions area within the People section of the admin in Drupal

Try Disabling Modules, One at a Time.. Or..

kjv1611 commented 13 December 2011 at 15:04

Try Disabling Modules, One at a Time..

Or you might be able to go to it via yoursitename.com/admin/people/permissions If I am remembering the path correctly. Whatever it is, you can try that without the #overlay portion of the path, and see if it works.

Another thing to check is in your web browser: make sure you don't have your site blocked with any script-blocking or possibly ad blocking addins/plugins/addons/whatever.

Also, try a different web browser to make sure it's not a browser related issue.

Otherwise, give a more detailed issue - don't just say "it's not working" - if you get an error message, post that. Give as much description as possible - what you did to get there, what browser you're using, perhaps even what add-on modules you've installed prior to this event, if any..

Thank you i have another error, i can not access any page after

Checdedon commented 23 December 2011 at 05:44

Thank you i have another error, i can not access any page on my localhost after enabling statuses and domain acces module when ever i load any page, i always get General error. 2006 MySQL server has gone away SELECT acl_id FROM {acl_user} WHERE uid=uid Array ( [uid]=&gt, 1 ) in acl _node_grant. I use drupal 7. 10 and my browser is firefox, please can anyone help me out

Statuses module caused this for me

SocialNicheGuru commented 10 April 2012 at 01:06

Statuses module caused this for me

http://SocialNicheGuru.com
Delivering inSITE(TM), we empower you to deliver the right product and the right message to the right NICHE at the right time across all product, marketing, and sales channels.

hi did you solve this? thanks

bossmac commented 17 May 2012 at 08:40

hi did you solve this? thanks

Peanut Media module is

SocialNicheGuru commented 15 July 2012 at 15:01

Peanut Media module is another culprit. putting in their queue

Problem identified!

drupalshrek commented 5 May 2012 at 17:20

I had exactly the same problem on Drupal 7.14. Investigating it, it happens when a module incorrectly defines an element outside of the correct array nesting. This means that instead of an array, the core code receives a single element. For example, below is a simplified version of the wrong code which the VChess module had, together with the correct version.

/**
 * VChess permissions
 */
function vchess_permission() {
  return array(
      'basic access' => array(
          'title' => t('Basic access'),
          'description' => t('Access basic VChess functions such as ability to create a game')),
      'reset games' => array(
          'title' => t('Reset games'),
          'description' => t('This enables someone to completely reset the games database. ')), 
          'restrict access' => TRUE,  //Note how this is incorrectly outside the 'reset games' array
  );
}

The right coding of the permissions is

/**
 * VChess permissions
 */
function vchess_permission() {
  return array(
      'basic access' => array(
          'title' => t('Basic access'),
          'description' => t('Access basic VChess functions such as ability to create a game')),
      'reset games' => array(
          'title' => t('Reset games'),
          'description' => t('This enables someone to completely reset the games database.'),
          'restrict access' => TRUE  // This is now correctly inside the 'reset games' permission
          )
  );
}

The ideal would be that Drupal core would trap this incorrect code and simply issue a friendly error message.

drupalshrek