By dantodd on

Hi all,

I've update the Drupal several times in the past with no problems. However, I am now faced with the following error:
Fatal error: Unsupported operand types in /home/dstodd/gtagencies.com/gta-3/includes/common.inc on line 1539

Any ideas or clues on how to resolve this?

Dan

Comments

dantodd’s picture

dantodd commented

Disabling the BitCache module makes it work again and reverting to the previous version also works. I'll post a support ticket for on the Bitcache page.

fernao’s picture

fernao commented

I'm having this problem too when I install a complete system (from a machine to another, i.e.) on a dev environment.

But the solution is simple: a single 'clear cache', at 'http://yourhost/admin/settings/performance'.
After that, the problem stops bothering me. :)

[]s

moomba’s picture

moomba commented

Unsupported operand types in html/drupal/includes/common.inc on line 1369.

I get this when a new user tries creating an account. I just upgraded to 6.8 too. I might go back to 6.6.

I checked the file common.inc too and line 1369 just ends code with );

Thanks

mfuggle’s picture

mfuggle commented

I have also upgraded to 6.8 and am having this problem when saving an new/edited page although the line number is 1369 rather than 1569.

I have reset the cache but that has not solved the problem and I don't have the BitCache module installed.

Regards
Martin Fuggle

mfuggle’s picture

mfuggle commented

I have reverted to Drupal 6.7 and still have the same problem. My site is not in production and I opened it up to someone else to populate some content and they created the content using cut and paste from M$Word. The html from M$Word looks pretty ghastly and it is possible that this is causing the problem. I am not certain that it is the cause and I would have thought that Drupal should protect itself from rogue html anyway so I am clutching at straws at the moment.

At this stage I am not sure whether or not this is a bug. Is anyone able the shed further light on this issue?

Cheers
Martin Fuggle

mfuggle’s picture

mfuggle commented

I have also reverted to Drupal 6.6 and the problem still exists. What happens is this

  • Open a page for edit
  • Edit the page
  • Save the page
  • It's at this point that the Fatal Error occurs
  • Use the back button on the browser and return to the page
  • It displays the text prior to the editing that took place
  • Click on the view button and the page displays the edited text

I have changed all pages where the content was pasted from M$Word but this has not resolved the problem.

I have restored back to Drupal 6.8 since it is fairly clear that the problem is not caused by the 6.8 release.Unfortunately I am not a developer so I am not able to dianose this problem by studying a code trace.  Nevertheless is there somewhere I can find more about the nature of the problem that is taking place?

Cheers

Martin Fuggle

mfuggle’s picture

mfuggle commented

I was experiencing this error on my DELL laptop. I just happened to be using my second laptop (a Macbook) to update some pages on the site and strangely the error did not occur. So the only thing that I thought could be the difference between the two machines (apart from the obvious) was the website cookie. I deleted the cookie on my DELL laptop and I no longer get the error.

I don't know why this might be the case but my issue is resolved.

Regards

Martin Fuggle

john.arroyo’s picture

john.arroyo commented

I get that error when I try to reset a password (user/password). I'm using 6.8, is there a work around? I've tried releasing the cash with no luck. I'd rather not revert to 6.6, but that's an option.

Fatal error: Unsupported operand types in /includes/common.inc on line 1369

thanks,
-John

www.johnarroyo.com | www.remixin.com

Oleksa-1’s picture

Oleksa-1 commented

same problem, when another users try to send comment they got

Fatal error: Unsupported operand types in /home/xxxxx/public_html/xxxxx/includes/common.inc on line 1369

johnmullin2003’s picture

johnmullin2003 commented

same problem here.

drupal 6.8, no cache module enabled.

the error happens when I go to --->administer-> menu -> primary links.

Fatal error: Unsupported operand types in /home/mysite/public_html/includes/common.inc on line 1539

Clear cache solution doesnt' solve my problem.

Any help appreciated.

Oleksa-1’s picture

Oleksa-1 commented

I do not have this error message anymore. in my case problem was with comment_notify_module. I upgraded to 6.x-1.x-dev and everything works fine.
Thanks Dave Raven and greggles for support.

From Dave: some modules not properly ported to D6. Just find out which one and disable it.

Greg J. Smith’s picture

Greg J. Smith commented

I'm having this same issue. It is definitely not an added module.. there doesn't appear to be much in the way of a solution to this one! If anybody else has troubleshot and solved this issue.. please speak up!

Greg J. Smith’s picture

Greg J. Smith commented

I've done a little more poking around and I've noticed that I'm not getting this error on certain nodes, but any time that I try to access an admin page, or edit a node I get the dreaded 1539 once again.

computer_jin’s picture

computer_jin commented

I have also this same problem.i was using drupal 5 and when i update on drupal 6 i m having this same issue..

--
Azhar uddin
Technical Lead
email : engr.azharuddin@gmail.com
skype : computer_jin

David_Rothstein’s picture

David_Rothstein commented

Well, looking at the code involved, it seems these errors are occurring in the url() and l() functions.

Both of these functions changed their API between Drupal 5 and Drupal 6, so it's extremely likely the errors are occurring due to a module (or theme) that is not properly updated for Drupal 6 and is still using one of these functions the old (Drupal 5) way.

The best way to find out which might be to run a PHP debugger on your site so that you can find out where the error actually came from.

signal000’s picture

signal000 commented

Don't know if this helps ,but ill throw my .02 in :)
I had the same error after I installed Memcache.
After I disabled it , the error went away.
Running 6.8 .

geomojo’s picture

geomojo commented

I had the same problem trying to enable memcache. However, I switched from memcache-v6.x-1.0 to memcache-v6.x-1.x-dev and I don't get the error now.

computer_jin’s picture

computer_jin commented

I have solved this problem.it was not the cache error message it was because of changing api, we were using l() but in drupal 6 api you will have to pass these parameters in links.. like that l($text, $path, $options = array()) try to do like this it will solve your problem INSHALLAH.
Take care ,

--
Azhar uddin
Technical Lead
email : engr.azharuddin@gmail.com
skype : computer_jin

markmck1’s picture

markmck1 commented

The way you are describing the function call "l" is the same as it is on line 1534. Could you be more specific in your instructions?

computer_jin’s picture

computer_jin commented

go on api.drupal.org than find this l() u will understand how you will use this function... reply me if u dont understand

--
Azhar uddin
Technical Lead
email : engr.azharuddin@gmail.com
skype : computer_jin

wa2nlinux’s picture

wa2nlinux commented

After upgrade from 6.7 to 6.8 this error show up

Fatal error: Unsupported operand types in /home/xxxxx/drupal-6.8/includes/common.inc on line 1369

When acces, admin/by-module

http://wa2n.nrar.net
http://artikelit.com

evilehk’s picture

evilehk commented

I was receiving this error when attempting to edit my primary links. Debugging the issue, I found that the variable $options was null in the l function in common.inc. Adding this line to the top of the function resolved the issue:

if (!$options) { $options = array(); }

I hate that I had to hack the core code to fix, so if anyone has any better solutions please let us know! Thanks,

Eric

elnucli’s picture

elnucli commented

Eric,

We have the same problem that you when trying to edit the primary links and we would like to know the exact modification code to that function in order to fix the problem:

function l($text, $path, $options = array()) {
// Merge in defaults.
$options += array(
'attributes' => array(),
'html' => FALSE,
);

Thank you very much!!!

Sergi.

evilehk’s picture

evilehk commented

Hello Sergi. I added a check in the first line of the l function. The check is if $options is not set then make it an empty array. My modification looks like this:

function l($text, $path, $options = array()) {
  if (!$options) { $options = array(); }
  // Merge in defaults.
  $options += array(
      'attributes' => array(),
      'html' => FALSE,
    );

...
elnucli’s picture

elnucli commented

Eric,

It really works!!! Thank you very much for your help.

As you can imagine, in that case for us it was more important to be able to edit the primary links that mantain the original core code.

Thanks again...

lordofwinds’s picture

lordofwinds commented

Thank you!
This modification work's well.

And i spend many minutes to resolve some problem.

kumarit84’s picture

kumarit84 commented

change the l() function with only two variable in that corresponding module eg l(t('More information.'), 'video/help') ie . pass only text & the link.

this will rectify this problem

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Take a look at the new Troubleshooting FAQ page on this error for information on how to debug and fix this problem.

computer_jin’s picture

computer_jin commented

Hi every one ,
I am also having this same issue before many days and today i debub how can i solve this issue actually i was having error ....
warning: Invalid argument supplied for foreach() in \includes\form.inc on line 1193.
I am having this issue and when i debug and comment the code of checkboxes in my module than this error is resolved but i have to use this checkboxes ,check my code if i m missing some minor code and tell me how can i solve this ..

$form['payment_options']['business_payment_method']= array(
'#type' => 'checkboxes',
'#title'=> t('Payment Options'),
'#default_value' => variable_get('business_payment_method',$selected_payment),
'#options' => $payment_options,
);
I am using this tell me if you understand how can i solve this issue ...

Thanks in Advance

Azhar
4 Ace Technologies(www.4acetech.com)
karachi,Pakistan

--
Azhar uddin
Technical Lead
email : engr.azharuddin@gmail.com
skype : computer_jin