The forums module doesn't display posts. Posting a topic to a forum will add a node, but won't show up in forums. When I browse to the top level of the forums, I get this message:

warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/machine/public_html/blog/modules/forum.module on line 705.

Each level I browse to in the forums throws an error/warning, references all instances of this line in forum.module:

if ($tid && !in_array($tid, variable_get('forum_containers', array()))) {

Comments

Uwe Hermann’s picture

Uwe Hermann commented

I think this worked for me with yesterday's HEAD version. Which versions exactly did you use?

mrmachine’s picture

mrmachine commented

I just updated to HEAD and still have the same problem.

decafdennis’s picture

decafdennis commented

From what you say in http://drupal.org/node/50889 your problem is related to taxonomy. It might be that somehow both the image and forum modules are using the same vocabulary.

mrmachine’s picture

mrmachine commented

After updating to latest HEAD, i get this error when trying to add a new forum container:

Fatal error: [] operator not supported for strings in /home/machine/public_html/blog/modules/forum.module on line 531

The container gets added, but i still get the problems as mentioned above.

decafdennis’s picture

decafdennis commented

I'm certain one or more of forum's variables are corrupted. First try a clean Drupal installation with the same modules enabled and try to reproduce.

mrmachine’s picture

mrmachine commented

I found out the problem - a while ago I changed the name of the Topic vocabulary to Blog ... I just changed it back, and everything is working fine.

So, changing - or deleting - the Topic vocabulary is not going to work when using the Forums or Image modules (and maybe others) ... should this be the case?

decafdennis’s picture

decafdennis commented

I wouldn't understand why just renaming the vocabulary solved your problem. As far as I know none of the modules search for the vocabulary by its name.

It might have something to do with the 'module' field in the database getting reset when you manually edit a vocabulary (like renaming it). This was fixed two days ago. (http://drupal.org/node/60265)

chx’s picture

chx commented
Status: Active » Fixed
Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)