I think that this started after i installed fckeditor, but i have tried uninstalling it and still have issues. I have the block activated, but when I send the question it goes to a blank page with this error:

Fatal error: Unsupported operand types in /webroot/d/e/denti005/www/includes/common.inc on line 1275

the site is www.dentistryart.com

you can ignore the fckeditor interface. I am trying to disable that now.

thanks if you can help.

Comments

Morten_P_Andersen’s picture

I got the same massage : "www/includes/common.inc on line 1275" without the Fckeditor when I replay too a post

nancydru’s picture

I don't use an WYSIWYG editor (there are way too many issues filed because of them) and I don't see this. Is this happening when you create the question or when you answer it? Is it for registered users or anonymous? Are you using the "notify" option?

zilla’s picture

@nancydru - i'm seeing the same thing as a registered user - but only the non-admin users see this when submitting comments

i do have notifications installed - and it appears to work, but i'm on a tiny dev install, just me!!

what about the other module, "comment notify" - could this be a culprit? any way to tell from the error or just need to tinker and turn things off and on...?

nancydru’s picture

It might be helpful to tinker to try to narrow this down. I do know that by the time you can submit comments, it is no longer Faq_Ask, but FAQ. Please bear in mind that once a question is selected to be answered, Faq_Ask turns it over to FAQ and is out of the picture from then on.

zilla’s picture

@nancydru- i tinkered last night and narrowed down my particular problem to the "comment notify" module - disabled and error went away...

nancydru’s picture

Status: Active » Postponed (maintainer needs more info)

Good - at least for me. I hope you have reported this to that module.

dave reid’s picture

Status: Postponed (maintainer needs more info) » Fixed

This error in comment_notify has been fixed.

Status: Fixed » Closed (fixed)

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