Fatal error: Unsupported operand types in common.inc on line 1592 [#739158]

Comment	File	Size	Author
#36	unsupported_operand-739158-36.patch	511 bytes	carsonblack
#14	common.patch	467 bytes	pydubreucq
#7	output.txt	310.52 KB	RedTop

Comment #1

German

Switzerland

commented 11 March 2010 at 07:05

This means that something calls l() wrong, the second argument is not an array. And I assume it is a contrib module, because I can't reproduce it.

You need to figure out who is the caller. Open that file, go to that line (or look for "function l($text, $path, $options = array()) {")) and then insert "array " before $options so that it looks like "function l($text, $path, array $options = array()) {".

Then access the above link again, that should give you a different error message. Post that here.

Log in or register to post comments

Comment #2

Mascher commented 11 March 2010 at 08:08

I insert "array" how u write, but i have some error message...
Fatal error: Unsupported operand types in /var/www/fantasy-portal.ru/htdocs/includes/common.inc on line 1592

But... I have error in logs:
Argument 3 passed to l() must be an array, null given, called in /var/www/fantasy-portal.ru/htdocs/includes/menu.inc on line 1612 and defined in file /var/www/fantasy-portal.ru/htdocs/includes/common.inc on line 1585.

Log in or register to post comments

Comment #3

berdir

German

Switzerland

commented 12 March 2010 at 06:36

Ok, strange.

We just have to dig until we find where this is coming from.

So open common.inc again and add the following code (without < ?php / ? >) directly above the "// Merge in defaults.":

if (!is_array($options)) {
  debug_print_backtrace();
  exit();
}

and then print the output here...

Log in or register to post comments

Comment #4

heine commented 12 March 2010 at 11:42

Category:	bug	» support
Priority:	Critical	» Normal

Log in or register to post comments

Comment #5

fax8 commented 14 March 2010 at 10:38

There are actually 2 lines containing "// Merge in defaults.". I guess that's the one in the l() function. I have it at line 1588.

Log in or register to post comments

Comment #6

fax8 commented 14 March 2010 at 10:47

I faced this error after upgrading one of my websites from d5 to d6 .. I had a custom block containing some PHP code which used the old d5 definition of l() while, after upgrading to d6, it's required to use the new d6 l() syntax.

In particular I had something like:

print l(theme_image('images/camera1-small.jpg'), 'images/camera1.jpg', null, null, null, null, true);

and I had to convert it to:

print l(theme_image('images/camera1-small.jpg'), 'images/camera1.jpg', array('html' => TRUE));

Hope this helps,

Fabio Varesano

Log in or register to post comments

Comment #7

RedTop commented 28 March 2010 at 23:05

Status	File	Size
new	output.txt	310.52 KB

I' m getting the same error when trying to access the settings page of one of the menus. It is quite a large menu with lots of child items (max dept probably around 5 levels or so). I' m able to access the other menus' settings just fine.

I tried the backtrace and the output was incredibly large. I have attached it to this comment.

Smart suggestions, anyone? :)

[edit]
Some debugging I tried today:

- Tried debugging as described here: http://drupal.org/node/362799. Unfortunately the output didn't change so that didn't help.

- I also tried the hack here: http://justinhileman.info/articles/unsupported-operand-types-in-drupal-6x , didn't help either (output stays the same except obviously for line number). :(

- I also tried disabling contributed modules by renaming the folders. None of the contributed modules seem to be the cause of this problem.

- Compared common.inc with a clean copy I always keep as a backup (sometimes it's hard keeping track of things when debugging). No differences. Copied the clean copy to includes folder anyway but didn't make a difference.

- The site has no custom blocks using PHP snippets (In fact, no custom snippets used anywhere on the site).

- The backtrace output mentiones line 73 in menu.admin.inc:73 of the menu module:

 $form[$mlid]['title']['#value'] = l($item['title'], $item['href'], $item['localized_options']) . ($item['hidden'] ? ' ('. t('disabled') .')' : '');

[edit]
This fix did the trick for me:
http://drupal.org/node/228435#comment-782632

Log in or register to post comments

Comment #8

Mascher commented 30 March 2010 at 07:27

Berdir I do as u say and i have this code in common.inc:

function l($text, $path, array $options = array()) {
  global $language;

if (!is_array($options)) {
  debug_print_backtrace();
  exit();
}
  // Merge in defaults.
  $options += array(
      'attributes' => array(),
      'html' => FALSE,
    );

  // Append active class.
  if (($path == $_GET['q'] || ($path == '<front>' && drupal_is_front_page())) &&
      (empty($options['language']) || $options['language']->language == $language->language)) {
    if (isset($options['attributes']['class'])) {
      $options['attributes']['class'] .= ' active';
    }
    else {
      $options['attributes']['class'] = 'active';
    }
  }

  // Remove all HTML and PHP tags from a tooltip. For best performance, we act only
  // if a quick strpos() pre-check gave a suspicion (because strip_tags() is expensive).
  if (isset($options['attributes']['title']) && strpos($options['attributes']['title'], '<') !== FALSE) {
    $options['attributes']['title'] = strip_tags($options['attributes']['title']);
  }

  return '<a href="'. check_url(url($path, $options)) .'"'. drupal_attributes($options['attributes']) .'>'. ($options['html'] ? $text : check_plain($text)) .'</a>';
}

And i have this output:

In log i have:

Argument 3 passed to l() must be an array, null given, called in /var/www/fantasy-portal.ru/htdocs/includes/menu.inc on line 1612 and defined в файле /var/www/fantasy-portal.ru/htdocs/includes/common.inc  в строке 1585.

You can see this at - http://fantasy-portal.ru/blog/amon/lalalalala , as sample.

And! This patch help me:
http://drupal.org/node/228435#comment-782632

but i restore Berdir writen code for test and patch if need.

Log in or register to post comments

Comment #9

deep-z commented 7 April 2010 at 18:55

Maybe incorrect URL formation, caused by some module conflicting with core clean url's system.

Make sure you don't have Clean pagination module (6.x-1.0-alpha2 version in my case) enabled. Disabled it and error vanished.

Hope this helps.

Log in or register to post comments

Comment #10

Mascher commented 15 April 2010 at 07:30

Berdir read this issue? I have patch now:

http://drupal.org/node/228435#comment-782632

If u need see debug tell me here...

Log in or register to post comments

Comment #11

Mascher commented 15 April 2010 at 07:31

Assigned:

Mascher

» Unassigned

Unassign now...

Log in or register to post comments

Comment #12

golubovicm commented 2 November 2010 at 12:11

Exactly same error happened to me, but fortunately it was in module I was working on, so I managed to localize it. Problem was that I by mistake named my functions like hooks, even they was not hooks.

My module name is "flash_uploader", and I named functions i.e. "flash_uploader_generate()".
So, I guess Drupal realized that this function is some mysterious hook_generate() hook and tried to do something with it and crushed there.

Just a wild guess - I'm still Drupal beginner.

Log in or register to post comments

Comment #13

pydubreucq commented 9 November 2010 at 00:02

Hi all,
Excuse-me I'm French and I don't speak english very well...
I have the same problem.
This occur when I configure error page (403 & 404) in :
/admin/settings/error-reporting
If I don't put one I don't have this error...
Like on this page :
http://drupal.org/node/362799
I've modify common.inc to see what's the problem :

1585 function l($text, $path, $options = array()) {
1586   global $language;
1587   if (!is_array($options)) {
1588     echo "<pre>";
1589     $backtrace = debug_backtrace();
1590     var_export($backtrace[0]);
1591     die();
1592   }
1593   // Merge in defaults.
1594   $options += array(
1595       'attributes' => array(),
1596       'html' => FALSE,
1597     );

When I want to see my custom error page I can see now that :

array (
  'file' => '/var/www/dev-website-com/includes/menu.inc',
  'line' => 1612,
  'function' => 'l',
  'args' => 
  array (
    0 => NULL,
    1 => NULL,
    2 => NULL,
  ),
)

If I go on the line 1612 in menu.inc file I can see that :

1611     foreach ($active_trail as $parent) {
1612       $breadcrumb[] = l($parent['title'], $parent['href'], $parent['localized_options']);
1613     }

If I comment that, my 404 error page works fine :)

This is not the right solution, but it works
breadcrumb is a priority for me

Thanks by advance for your help ;)

Bye

Log in or register to post comments

Comment #14

pydubreucq commented 9 November 2010 at 00:26

Status	File	Size
new	common-404-error-path.patch	467 bytes

This patch works fine :
http://drupal.org/node/228435#comment-782632

I've modify it because the line was not good...

You can find it on this comment.

Bye ;)

Log in or register to post comments

Comment #15

Ela commented 22 November 2010 at 21:33

#14 works for me, Thank you :)

Log in or register to post comments

Comment #16

harvlad commented 8 December 2010 at 22:49

Hey, this happened to me using the Me module

Log in or register to post comments

Comment #17

RedTop commented 15 December 2010 at 22:54

Status:

Active

» Closed (fixed)

Multiple comments mention that this patch works and fixes the issue:
http://drupal.org/node/228435#comment-782632

pydubreucq modified the patch and included it in #14.

This thread is a duplicate and a fix is available. Now we just have to wait on the devvers in http://drupal.org/node/228435#comment-782632 to perfect it and commit to core.

Setting this as 'fixed' even though the fix available hasn't been perfected/committed yet. The patch works and a 'fixed' status will be more meaningful for people looking for a patch.

Log in or register to post comments

Comment #18

damien tournoud commented 15 December 2010 at 23:26

Status:

Closed (fixed)

» Closed (works as designed)

There is nothing to fix here. Drupal Core works as designed, but something is calling the API in an incorrect way. Try to fix the really issue, not the symptom, please.

Log in or register to post comments

Comment #19

Ela commented 16 December 2010 at 02:57

As in #7, I had this error when trying to access one of the menus. I deleted the menu, created it again, but gave it a different system name, and without the patch all seems fine.

Log in or register to post comments

Comment #20

gianfrasoft commented 31 January 2011 at 17:26

Status:

Closed (works as designed)

» Needs review

Using the debug method explained in http://drupal.org/node/362799 I changed in menu.inc the rows:

    foreach ($active_trail as $parent) {
      $breadcrumb[] = l($parent['title'], $parent['href'], $parent['localized_options']);
    }

in

    foreach ($active_trail as $parent) {
      $breadcrumb[] = l($parent['title'], $parent['href'], array($parent['localized_options']));
    }

and problem seems to be solved. I think that is an invalid call of l() function, passing from the D5 sintax to the D6 one.

Log in or register to post comments

Comment #21

31 January 2011 at 17:41

Status:

Needs review

» Needs work

The last submitted patch, common.patch, failed testing.

Log in or register to post comments

Comment #22

damien tournoud commented 13 March 2011 at 15:19

Status:

Needs work

» Closed (works as designed)

Log in or register to post comments

Comment #23

SHS commented 28 July 2011 at 16:37

#20 worked for me! thanks a lot :)

Log in or register to post comments

Comment #24

hchall commented 31 July 2011 at 02:36

Thanks pydubreucq! #20 worked for me!

Log in or register to post comments

Comment #25

darrellduane commented 7 August 2011 at 17:05

#20 was a big help -- This issue only happened when the user was anonymous, when logged in the error didn't happen.

Log in or register to post comments

Comment #26

-enzo- commented 16 September 2011 at 16:22

Thanks pydubreucq! #20 worked for me! too

Log in or register to post comments

Comment #27

salientknight commented 13 October 2011 at 15:10

Not sure what this adds to the conversation, but I just made a copy of a working site, and then started to get this error when logging in to the copy. All database and path settings are correct and they are on the same server... two other copies I made work fine.

*stumped*

Log in or register to post comments

Comment #28

salientknight commented 13 October 2011 at 16:25

I needed to update my $cookie_domain variable in settings.php.

Log in or register to post comments

Comment #29

Michsk commented 16 October 2011 at 09:16

I can also confim as stated in @#16 (http://drupal.org/node/739158#comment-3804798). This is happening with the ME module (offcourse multiple modules can have this, but ME is confirmed that it has this issue). Will look at it.

Those who also have this with the me module: http://drupal.org/node/899508#comment-5122266

Log in or register to post comments

Comment #30

David_Rothstein commented 1 December 2011 at 17:19

Note that for the case where this kind of error occurs on custom 403 and 404 pages (as described in #13 above), this is likely due to #918356: WSOD when drupal_get_title called during hook_init and custom 403 or 404 pages are being used.

Log in or register to post comments

Comment #31

mattcasey commented 7 December 2011 at 10:17

#20 works for me, I am using Acquia's latest Drupal 6.x version and got the error for 404 pages.

Log in or register to post comments

Comment #33

amstel commented 13 March 2012 at 19:21

#20 also worked for me. I had this error message when trying to access admin pages after session expired.

Log in or register to post comments

Comment #34

chinita7 commented 24 May 2013 at 17:12

#20 worked for me also. Thanks.

Log in or register to post comments

Comment #35

carsonblack commented 6 June 2013 at 06:41

Version:

6.16

» 6.28

This is still broken in 6.28
#20 works

Log in or register to post comments

Comment #36

carsonblack commented 6 June 2013 at 06:58

Status	File	Size
new	unsupported_operand-739158-36.patch	511 bytes

Here is a patch implementing #20.

Log in or register to post comments

Comment #37

carsonblack commented 6 June 2013 at 06:59

Category:	support	» bug
Status:	Closed (works as designed)	» Needs review

Log in or register to post comments

Comment #38

codenamerhubarb commented 9 December 2014 at 00:19

Issue summary:

View changes

Thanks gianfrasoft
#20 also worked for me!

Log in or register to post comments

Comment #39

2 March 2016 at 22:18

Status:

Needs review

» Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.

Log in or register to post comments

Fatal error: Unsupported operand types in common.inc on line 1592

Comments