By rotnme on

OK. I posted previously about my problems but now after searching Drupal and Google I am no further along. I'm so at a loss. I add keywords to page title on my start page and get this error :

"Fatal error: Unsupported operand types in /home/content/m/a/r/markcissi/html/includes/common.inc on line 1416"

I have searched this everywhere and can't find a solution. Opened my site in Firefox using Firebug and went to line 1416 and this is what is there:

< / li >
there are no spaces but that is the only way it would post.
Anyone? I'm on my last nerve with this. Thanks in advance.

⋅ Categories: Drupal 6.x

Comments

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

Hi,

This is a PHP issue, not a JavaScript, HTML or CSS issue, so firebug will not help.

With the information you've provided it's hard to say exactly what the issue is, but I'm guessing that it's somewhat related to the version of PHP your web server is running.

The best place for the support you will need is actually the Drupal issue queue, so I would suggest searching that to see if anyone had a similar issue (don't include your path '/home/content/m/a/r/markcissi/html', as that is unique to your server and will turn up no results) and if you can't find anything there that looks the same you could create your own issue and hopefully someone will be able to help.

Cheers,
Deciphered.

rotnme’s picture

rotnme commented

Thanks so much!

rotnme’s picture

rotnme commented

Well, upon further investigation.... If I log in as myself (admin) and try to enter keywords to the title or to meta tags, I get the above error. I have a friend of mine set up to have access as well to peek and tweek. Just for the hell of it I logged in as him and entered title and meta tag keywords and it worked just fine. My thought now is that it is not a php issue but rather a permission issue. Where to go from here, I have no idea. Any thoughts appreciated.

femrich’s picture

femrich commented

I am experiencing the same error message. It happens when users post a content type either as a draft or as a published post. Clicking save launches the error message, though the content is successfully saved. So far I have found no other instances of this error in drupal.org other than two threads you initiated, rotnme. Have you had any luck with this yet?

rotnme’s picture

rotnme commented

Not at all. I've been fooling with this for what seems like forever. What gets really weird, I have a friend who I set an admin/editor acct for to peek and tweek. If I log in as him I don't get the error and all is well. So, does that make it a permission thing? I'm so lost. Ditto to you as far as finding similar errors, there are some thru drupal, google, etc but none that I have found mimic my situation. FYI, I have not stumbled across any issues either. Throwing my hands up in the air and looking for help.

femrich’s picture

femrich commented

http://drupal.org/node/677824

femrich’s picture

femrich commented

And here's a handbook page with a possible solution: http://drupal.org/node/362799

rotnme’s picture

rotnme commented

I actually looked at these. The first, I don't have that module so I kind of dismissed it. The second, I am by no means a pro at this and am hesitant to start changing code. Also, if you reference my post above, another user does not experience this so I am very reluctant to start changing stuff. All I can say is that I'm frustrated and clueless in Raleigh.

femrich’s picture

femrich commented

rotnme, the solution offered in the handbook page worked for me. (The offending module was Akismet.) I suspect you are feeling nervous about messing with coding? I'm a non-coder, but I've worked with drupal for a while and figured out pretty much that tested solutions are pretty safe. Just get into your back end, download a copy of common.inc to your desktop, open the file with wordpad and do a search to find the proper code, then copy/paste to replace.

Next delete common.inc from your site and upload the edited version to the includes folder. Run update.php, then visit the frontpage of your site and do whatever caused the original error message. If you are like me, the offending module is identified.

Next, rename your edited common.inc file, restore the original file, delete the edited file, and run update.php again. Uninstall the offending module, update php again, and you should be done.

Sounds complicated, but it isn't really. And for a non-coder, it will give you a sense of having figured something out. If you were here in person, I'd show you myself.

Of course, another option is just to uninstall Akismet (if you have it installed) and see if that fixes things.

Good luck!

rotnme’s picture

rotnme commented

Thank you so much. I just read your post and am going to start trying what you suggested. I appreciate you're understanding of my hesitance. Will let you know what happens.

rotnme’s picture

rotnme commented

Success, I guess. I disabled Akismet and things are good. Not now, but maybe tomorrow when I"m in a better frame of mind I may tackle the code end and re-activate Akismet. For now, I am grateful. Thanks again!

femrich’s picture

femrich commented

Congratulations. Sounds like progress. As per the instructions on the Handbook page, I filed a bug report on the Akismet page. Don't know if it will result in anything, but you might follow that to see whether there are any useful fixes posted: http://drupal.org/node/698824

If you come up with a solution elsewhere that helps with a reinstall of Akismet, I would appreciate you posting a comment here.

Cheers!

rotnme’s picture

rotnme commented

Just looked for any relevant issues regarding akismet, found nothing. For now, I am content to leave it disabled. It still bugs me that I as administrator encountered this problem, but yet when I logged in as my friend who also has the same permissions, everything worked fine. What would be different? I don't know, just happy to get past it. Now back to optimizing, not fun.

femrich’s picture

femrich commented

I did not experience the same difference between super-admin and registered user experience, but it may be that the problem has something to do with one user's posts being subjected to the akismet filter and the other's not. Just a thought.

I've also found nothing at the Akismet support page and noticed the page seems relatively inactive, so I will look to another option for spam protection. CAPTCHA is a much more popular module in Drupal, though it works differently. But I may check it out.

Good luck!

rotnme’s picture

rotnme commented

I'm running Captcha as well as mollom. No problems, everything seems to be fine. As far as I'm concerned Akismet can stay inactive.