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.Hi...
I have just run into a critical issue. I updated my site from Drupal 7 to Drupal 7.2 and views 7.x-3.0-alpha1 to beta 3, (and reverted back to dev3 but that's irrelevant)
I am using the audiofield module and I have a block view with the audio field.
After upgrading Drupal I got this error:
Debug:
'Missing handler: field_data_field_track_preview entity_id field'
in views_get_handler() (line 841 of C:\wamp\www\test\sites\default\modules\views\views.module).
Error message
Notice: Undefined property: stdClass::$unknown in views_handler_field->render() (line 713 of sites\default\modules\views\handlers\views_handler_field.inc)
My audio field in my view is now missing, in place it says "Broken/missing handler". I tried to re-add the field but it is not in the field list.
After updating to Views beta3 the error is gone, but the field is still missing.
I'm stuck and don't know what to do next...
Thank You.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | missing.jpg | 112.81 KB | Rick Bergmann |
Comments
Comment #1
dawehnerDid you cleared the views cache on admin/structure/views/settings under the advanced tab?
Comment #2
Rick Bergmann CreditAttribution: Rick Bergmann commentedI have now cleared the views cache, and the handler is still broken or missing.
Comment #3
Rick Bergmann CreditAttribution: Rick Bergmann commentedI have just noticed another message in the actual content type which has the missing handler , has got to do with field module. It comes up twice because I have that particular audio field twice.
Update:
There is a problem with those fields. If I add a new one, then the new one is fine.
I'm a bit worried to delete the broken ones and re-add them with the same field name because there is a lot of data associated with those fields and I don't want to lose it and re-add it, but I think that's the only/best solution?
Can you confirm that's my best option?
Thanks.
Comment #4
Rick Bergmann CreditAttribution: Rick Bergmann commentedAttaching a screen shot to show what exactly is missing.
Comment #5
dawehnerLet's move to audio module because this missing widget type is definitive not something caused by views.
Comment #6
Rick Bergmann CreditAttribution: Rick Bergmann commentedComment #7
Pete B CreditAttribution: Pete B commentedI ran into the same issue and found that at some stage in the past, audiofield defined its own field type 'audio' using a hook_field_info()
This was later changed to use the 'file' field type.
So for me, on upgrading from an old dev version to beta4, I got the error as above (now on line 375 in drupal 7.12)
The fix was to go into the database and run:
Then clear the site cache and views cache.
Thanks,
Pete
Comment #8
tamerzg CreditAttribution: tamerzg commentedYes the initial dev version of audiofield had its own audio field type which was then converted back to using file type as people had problems with upgrading.
Solution posted in #7 should fix this issue for users upgrading from older dev to beta1.
Comment #9
micheas CreditAttribution: micheas commentedIt seems to me that the proper solution is to put in an upgrade of 7001 that runs the upgrade script.
I have a couple sites that need to go through dev->test->live and have the database upgrade happen,
It seems like it would be fine for people that have type=file to have the update script and ease the upgrades.
(I have only read about how to do this so I'll have fun learning how to create the upgrade statement, and it seems pretty simple)
Comment #10
Daniel.Moberly CreditAttribution: Daniel.Moberly commentedCan't imagine this issue still applies to anyone.