Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Recently migrated from Drupal 6 to 7.
- Uncompressed Views Bulk Operations and Administrative Views in modules pathway - have not enabled yet.
- Went to update.php
Following errors were reported:
Notice: Undefined offset: 0 in taxonomy_field_views_data() (line 401 of /var/www/html/sites/all/modules/views/modules/taxonomy.views.inc).
Notice: Undefined offset: 0 in taxonomy_field_views_data() (line 401 of /var/www/html/sites/all/modules/views/modules/taxonomy.views.inc).
Any advice on how to troubleshoot, what it means and how to make it go away will be greatly appreciated.
Thanks,
Ace
Comments
Comment #1
dawehnerYou seems to have a field without a vocabulary setup, this might have been a problem with your migration process.
In general there were multiple issues about this problem already and it is always a question whether hiding an error is better then showing one, which gives you the hint that something might be wrong.
Comment #2
Avalanche CreditAttribution: Avalanche commentedThat makes a lot of sense - and I have an idea of which content types might be the problem.
I'll post an update and close the ticket out once I chase down the culprit.
Thanks dawehner
Comment #3
nsjski CreditAttribution: nsjski commentedI saw this too, found a field called taxonomyextra, had been created by taxonomy upgrade, belonged to one of my content types but the field was not used, I deleted the field and the error message went away.
Comment #4
Melissamcewen CreditAttribution: Melissamcewen commentedVisiting the edit fields page of the offending content type cleared this error for me.
Comment #5
Melissamcewen CreditAttribution: Melissamcewen commentedJust kidding, still having this issue.
Comment #6
jessZ CreditAttribution: jessZ commentedNotice: Undefined offset: 0 in taxonomy_field_views_data() (line 433 of /home/reimagi8/public_html/new/sites/all/modules/views/modules/taxonomy.views.inc).
I also have the "field called taxonomyextra, had been created by taxonomy upgrade," but unfortunately it includes all the old gallery taxonomy terms and they didn't migrate to the new "image gallery" term and only the legacy terms show up on the nodes (over 1500 of them).
Is their a way i can change this field so it has a parent and i can then delete the unnecessary ones via the UI for taxonomy.
Comment #7
nimazuk CreditAttribution: nimazuk commentedsubscribing!
Comment #8
Hetta CreditAttribution: Hetta commentedTo migrate taxonomyextra terms into their correct vocabularies, you have to run below sql for each vocabulary.
Back up your database before you start, because this can mess things up quite royally:
;
Also do this for the _revision_ tables:
;
Once your taxonomyextra table is completely empty, you can go to each of your content types and delete the taxonomyextra field.
(your server) /admin/structure/types
For image, for instance:
(your server) /admin/structure/types/manage/image/fields
-> taxonomyextra (click delete).
Now the "undefined offset" warning is gone.