"Illegal offset type in" warnings on node preview.

maybe it's a conflict with the ubercart module.
do you get the same error messages with a different own content type and content taxonomy fields?

I was getting the same message (no Ubercart). It started after upgrading from d6.9 to d6.10. I "solved" to problem by going into the CT field for my content-type then unchecking the "Save values additionally to the core taxonomy system (into the 'term_node' table)." option, saving, re-checking, saving.

thanks for this information. I'm still running drupal 6.8 on my local installation.
I'm going to update my installation and check this issue again

updated my drupal installation and still not getting any error
maybe it has been fixed with this issue (fixed today)

@mh86 Re #5 : I don't think that http://drupal.org/node/395328 solves this issue.
I upgraded from 6.x-1.0-beta6 to 6.x-1.x-dev 2009-03-17 but I still see the error. I have a simple content type with

- a Content Taxonomy CCK field, Select List widget type, nested in Standard Group, configured for vid 4
- vocabulary 4 is NOT directly assigned to my content type in admin/content/taxonomy/edit/vocabulary/4

Going into node editing, when clicking on preview I get the error warning: Illegal offset type in isset or empty in /var/www/drupal/modules/taxonomy/taxonomy.module on line 1015.
If I now create a vid 5 and assign it to content type via admin/content/taxonomy/edit/vocabulary/5 then preview is ok, no error.
I could assign vid 4 as both Content Taxonomy field AND direct vocabulary assignment, but I assumed that this would
be a bad practice... is that assumption wrong? Thank you.

The same issue has been encountered here with Drupal 6.10, CCK 6.x-2.2 and Content Taxonomy 6.x-1.x-dev (2009-Mar-17).

To reproduce it:

1. Create a new content type
2. Add a content taxonomy field to the new content type
3. Configure that field to use one of the options widgets, e.g. Select List, and enable the option "Save values additionally to the core taxonomy system".
4. Create, preview and save a new node of this content type (should preview and save fine)
5. Edit the node and hit Preview. This should get you the "illegal offset type" error message(s)

Same issue for me -- did the same as richardwdoe described in #9.

    * warning: Illegal offset type in isset or empty in /www/htdocs/XXX/XXX/drupal/modules/taxonomy/taxonomy.module on line 1015.
    * warning: Illegal offset type in /www/htdocs/XXX/XXX/drupal/modules/taxonomy/taxonomy.module on line 1016.
    * warning: Illegal offset type in /www/htdocs/XXX/XXX/drupal/modules/taxonomy/taxonomy.module on line 1019.
    * warning: Illegal offset type in /www/htdocs/XXX/XXX/drupal/modules/taxonomy/taxonomy.module on line 592.

Following up on my previous comment #9, further investigation suggests that these warnings will not be displayed if you:

• associate another taxonomy vocabulary with your content type; and
• do not add that vocabulary to the content type's list of fields (by means of content_taxonomy's CCK fields).

In other words, if you have at least one vocabulary associated with the content type that is not handled by content_taxonomy, you will not get the warnings.

subscribing

Hi!
Finally I was able to reproduce the problem (thanks to the detailed descriptions). The Taxonomy module was throwing the warnings on preview because of a wrong format in $node->taxonomy. This happened when every core taxonomy field got hidden. I think this problem already existed for a longer time, at least since some Content Taxonomy versions.
The problem was quite hard to debug, but I think I found a working fix (a bit strange, but ok). I committed the changes to the dev version. So, when trying the fix, be sure to have the right version. Fix will be included in the next release anyway ;)

not sure if this was committed to the latest (May 17) release but I'm still getting these errors as well.

thanks for all your work.

I was getting this but the mode I have in taxonomy fixes this. This has been reported as a taxonomy issue but isn't fixed. See http://drupal.org/node/275352#comment-1422794 for my solution. If you add

  drupal_set_message("<pre>" . print_r($tid, true) . "</pre>");

to taxonomy just be line 1011 if (!isset($terms[$tid])) you can see the majority have $tid as numeric but some are complete objects.

I've just checked out the latest branch, DRUPAL-6--1, and I'm still getting the same errors. See http://drupal.org/node/275352 for related issues.

Having same problem with 6.x-1.x-rc1.

Content Taxonomy writes taxonomy terms to core database, option widgets activated (but does not matter). Preview mode throws the described errors.

I use Content Taxonomy to have a per node type restriction / representation for taxonomy terms. In one node type it is allowed to add terms, in another node type it is not. In one node type you have single selection, in another node type you have multiple selection. I can not do without this module.

Subscribing...downloaded latest CT, and problem is still there..

@mh86: I found error with your patch: in form_alter hook you seem to unset $form['taxonomy'] while you should actually work with $form['#node']->taxonomy (as taxonomy code which is causing preview problems). Also, at the beginning of the funcion you make following check:

if (!is_array($form['taxonomy'])) {
      return;
    }

and I checked that during preview $form['taxonomy'] is empty so function simply terminates at the beginning because of this check.
If I understand it correctly, during preview whole node object is prepared in $form['#node']. If I simply enter at the beginning following code:

if (isset($form_state['node_preview'])) {
  unset($form['#node']->taxonomy);
}

then preview works without errors ( but it's ofcourse not solution, cause it disables normal non-CT vocabs too, I think).

So my conclusion: seems like entire content_taxonomy_form_alter() function needs major rework. Those $form_state's seem to be tricky and require good understanding of what is happening deep and what needs to be done. If taxonomy code behaves differently in different $form_states then we should too, but currently same code runs in CT function.

This happens not only with Options widget.

I added another few lines to prevent an empty taxonomy form array on preview. it seems like this fixes the warnings for me. I hope this is working now.

accidentally changed issue settings with previous comment..

Going through the same steps I detailed in comment #9 with the dev versions dated 2009-Jul-16 and 2009-Aug-12, this issue looks to be fixed in both.

Thanks mh86.

In my dev-version from Sep 13th I still get this error.

and active

me too... sorry

It seems this was 'unfixed' in #552874: php undefined variable notices. The patch in #4 of that issue, fixes things for me.

@crea / #22: I have spent some hours debugging this and was thinking exactly the same as you. However, apparently mh86's changes do fix everything (and make sure that taxonomy_preview_terms() isn't called unnecessarily? I'm too tired of this to re-check that ;) )

Me too experiencing the problem with drupal6.15 / content taxonomy 6.x-1.0-rc2
I'm not an expert of php, I just flag the error I'm having and paste bottom the warnings I get.
Thank you, zoo

    * warning: Illegal offset type in isset or empty in ***\modules\taxonomy\taxonomy.module on line 1011.
    * warning: Illegal offset type in ***\modules\taxonomy\taxonomy.module on line 1012.
    * warning: Illegal offset type in ***\modules\taxonomy\taxonomy.module on line 1015.
    * warning: Illegal offset type in ***\modules\taxonomy\taxonomy.module on line 591.
    * warning: Illegal offset type in isset or empty in ***\modules\taxonomy\taxonomy.module on line 1011.
    * warning: Illegal offset type in ***\modules\taxonomy\taxonomy.module on line 1012.
    * warning: Illegal offset type in ***\modules\taxonomy\taxonomy.module on line 1015.
    * warning: Illegal offset type in ***\modules\taxonomy\taxonomy.module on line 591.

Subscribe

Same thing here...can we get a final commit to the fix for this? If it was fixed in the past, why is that not being committed?

patch from #552874: php undefined variable notices committed, this should fix this issue again.
please check out the latest dev version and give me some feedback if everything works

subscribe

Confirmed as fixed for my installation with -dev.

Drupal 6.15
PHP 5.2.6

I have same error on preview with latest dev version.

problem appears in d6.16 and latest -dev in my site too

Confirming #40 issue persists in Drupal 6.16 and content_taxonomy-dev as of 28 May 2010.

hold on, i need to take my foot out of my mouth. The -dev version does resolve this issue for me.

subscribing. Seen this issue in dev version w/ drupal 6.16, in conjuction with hierarchical_select-6.x-3.1.tar.gz

Posted the issue I am seeing here: http://drupal.org/node/815796

Please confirm if the patch is in the latest dev version. Thanks

I can confirm that the -dev version (as of 3 June 2010) resolves the following error in Drupal 6.16. I received the error when submitting a node for preview. The dev version resolved this issue for me on two sites.

<pre>
warning: Illegal offset type in isset or empty in .../modules/taxonomy/taxonomy.module on line 1023.
warning: Illegal offset type in .../modules/taxonomy/taxonomy.module on line 1024.
</pre>

I experienced the same problem and can confirm that 6.x-1.x-dev (release form 2010-Apr-08) fixed it, thanks.