I'm running Drupal 6.2 and have just installed nodeformsettings-6.x-2.0 and enabled the following:

CCK Form Settings
Comment Form Settings
Node Form Settings

and I get the following error:

Fatal error: Cannot use string offset as an array in /home/photo/public_html/sites/all/modules/nodeformsettings/commentformsettings/commentformsettings.module on line 269

whenever I try to visit a page containing comments. Disabling the Comment Form Settings module, but leaving the other two enabled seems not to break anything, but clearly I can't configure Comment Form Settings.

Comments

lelizondo’s picture

lelizondo commented
Version: 6.x-2.0 » 6.x-2.x-dev
Priority: Critical » Major

I'm sorry for the late response. I'm not getting this error, at all. But I just noticed that you're using Drupal 6.2? Is it 6.2 or you just missed a 0 in 6.20? If is 6.2 please upgrade Drupal first.

One more thing you could try is to test the 6.x-2.x-dev version

Another thing to test is if you have overridden the theme_box in your theme.

ajaysolutions’s picture

ajaysolutions commented

Sorry, yes it's Drupal 6.20.

I've upgraded to the 6.x-2.x-dev version, and I still get the error. I've also switched the theme back to Garland, and confirmed it's nothing in my theme that's causing the error.

I've got quite a lot of modules enabled on this installation, and I've tried disabling anything comment related to no avail. Do you have any suggestions?

h2odigital’s picture

h2odigital commented

I have the same error but just if theme developer is enabled

lelizondo’s picture

lelizondo commented

Theme Developer sometimes can trigger some errors that otherwise would never happen. Please confirm if you have this module installed or if something else is causing the problem. If is not, a list of the modules installed could help replicate the problem.

ajaysolutions’s picture

ajaysolutions commented

Thanks. I had them installed until recently, and I disabled them. I have now removed them completely from the server (Devel and Theme Developer) and tested again, and I'm still getting this error.

These are the modules I have installed:

Admin menu (6.x-1.6)
Ajax comments (6.x-1.8)
Archive (6.x-1.4)
Backup and migrate (6.x-2.4)
Captcha (6.x-2.4)
CCK (6.x-2.9)
Checkbox validate (6.x-2.1)
CKeditor (6.x-1.3)
Clientside validation (6.x-1.12)
Colorbox (6.x-1.0-beta11)
Comment hideusername (6.x-1.0)
Comment moderation (6.x-1.0)
Comment notify (6.x-1.5)
Conditional styles (6.x-1.2)
Custom breadcrumbs (6.x-2.0-rc1)
Date (6.x-2.7)
EXIF (6.x-1.4)
Facebook Like Button (6.x-1.1)
File field (6.x-3.10)
Fivestar (6.x-1.19)
Global Redirect (6.x-1.x-dev)
Google Analytics (6.x-3.3)
HTML Purifier (6.x-2.4)
IE6 No More (6.x-1.0-beta2)
ImageAPI (6.x-1.10)
ImageCache (6.x-2.0-beta12)
ImageCache Actions (6.x-1.8)
ImageField (6.x-3.10)
ImageField Crop (6.x-1.x-dev)
IMCE (6.x-2.1)
Input Format Permissions (6.x-1.0)
jQuery update (6.x-2.0-alpha1)
Libraries (6.x-1.0)
Logintoboggan (6.x-1.9)
Nodeformsettings (6.x-2.x-dev)
Node reference URL (6.x-1.11)
Pathauto (6.x-1.5)
PNG Behave (6.x-1.7)
Poormanscron (6.x-2.2)
Quote (6.x-1.2)
Recaptcha (6.x-1.7)
Semantic Views (6.x-1.1)
SU Comments (6.x-1.2)
Subpath Alias (6.x-1.1)
Token (6.x-1.16)
Touch Icons (6.x-1.0-rc1)
Transliteration (6.x-3.0)
Tweet Button (6.x-1.4)
Ubercart (6.x-2.4)
UC Product Power Tools
URL Alter (6.x-1.2)
Vertical tabs (6.x-1.x-dev)
Views (6.x-2.12)
Views Attach (6.x-2.2)
Views Customfield (6.x-1.0)
Views Cycle (6.x-1.0)
Voting API (6.x-2.3)
Webform (6.x-3.11)
XML Sitemap (6.x-2.0-beta2)

...Phew!

Before you go to the hassle of installing all that lot and playing about, I'll use Backup and Migrate to create a copy of this site on another server, and start disabling modules to see if I can find what's doing it.

Let me know if anything jumps out at you, but I've already tried disabling any modules that are comment related, and as I mentioned, changing the theme back to Garland - no joy yet.

I'll keep you posted. Thanks for the feedback.

lelizondo’s picture

lelizondo commented

Thanks, I'll start creating a site with all those modules to see where is the problem. If you start to disable some modules I would start with:

Comment hideusername (6.x-1.0)
Comment moderation (6.x-1.0)
Comment notify (6.x-1.5)

fnikola’s picture

fnikola commented

receiving the same error message on 6.x-2.0 - any updates to this issue?

fnikola’s picture

fnikola commented

i was able to eliminate the error by changing the "Preview button" to Disabled under the "Comment form settings". note that the "Preview comment" option is set to Optional under the "Comment settings".

fnikola’s picture

fnikola commented

just wanted to confirm that this issue happened on another content type on the same site and the steps taken in #7 resolved it too.

dineshpal’s picture

dineshpal commented

I have also the same error on drupal 6.20.

vml-bsummers’s picture

vml-bsummers commented

I was recieving the same error in my situation it was caused by something different.

viewing a page 'primary_page'

bringing in a view with context (content type is discussions ). this view displays items as nodes (full display with comments)

the commentformsettings it is trying to retrieve is looking for the settings for primary_page instead of discussions which did not have a variable string

charlie-s’s picture

charlie-s commented

Step taken in #8 solved for me as well. Definitely a bug.