I have enable the HS for forum taxonomy. Also I am using advanced forum.( not quite sure whether is the problem conflict with advanced forum or just the core forum)

when user try to post node . get the message below. the node can not be saved.

* warning: Illegal offset type in isset or empty in /home/xxx/public_html/xxx.com/includes/form.inc on line 697.
* An illegal choice has been detected. Please contact the site administrator.

after I trun off HS, the problem gone.

Please help.

Comments

wim leers’s picture

Status: Active » Postponed (maintainer needs more info)

Are you using CTools?

totodetokyo’s picture

Hello,

I just discovered exactly the same issue ( using also Hierarchical Select 6.x-3.x-dev)
(I am using Advanced Forum too)

Would you need some very specific information so that we could try to fix this issue?

Your support would be greatly appreciated!

Thank you

Anonymous’s picture

Title: got warning message when using for advanced forum » got warning message when using forum

I'm not using Advanced Forum, just the plain vanilla Forum module and get the same error message.

Anonymous’s picture

Status: Postponed (maintainer needs more info) » Active

It's also throwing errors on the /admin/reports/dblog page:

warning: preg_match() expects parameter 2 to be string, array given in /home/.../includes/bootstrap.inc on line 771.

I think it's the Form API trying to leave the error message in the log but getting an array instead of a string for %choice:

Illegal choice %choice in !name element.

a:2:{
  s:7:"%choice";a:1:{s:6:"hidden";a:1:{s:19:"lineages_selections";a:1:{i:0;s:21:"a:1:{i:0;s:4:"5969";}";}}}
  s:5:"!name";s:7:"My Forum Vocabulary";
}
yenidem’s picture

is there any solutions this problem?

wim leers’s picture

Assigned: Unassigned » wim leers

Problem reproduced.

wim leers’s picture

Title: got warning message when using forum » #options set by forum module, this causes a validation error
Status: Active » Fixed

The forum module inappropriately sets the #options attribute, it should first check if that exists or not. Worked around this core bug by increasing the module weight.

Committed a fix: http://drupal.org/cvs?commit=243334. You must run update.php to automatically increase the module weight.

Status: Fixed » Closed (fixed)

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