Active
Project:
Project
Version:
7.x-2.x-dev
Component:
Releases
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Oct 2012 at 22:07 UTC
Updated:
7 Nov 2012 at 20:42 UTC
Project Release has a Drupal 6 dependency: The code requires the name of the term reference field for the API vocabulary to be named
'taxonomy_' . $api_vocabulary->machine_name
The only way to create a field that follows this pattern is to upgrade from Drupal 6, see taxonomy_update_7004(). A Drupal 7 term reference field will have the field_ prefix, and can have an arbitrary name.
To reproduce:
drush vset project_release_api_vocabulary N #, where N is the vid of your vocabulary created above
project_release_find_latest_releases($nid, $tid, NULL). You'll see the error PHP Fatal: EntityFieldQueryException: Unknown field: taxonomy_version.
??
??
N/A
???
Comments
Comment #1
dww'taxonomy_' is fine for taxonomy.module provided fields. 'field_*' is supposed to be the namespace for field.module fields. But taxonomy creates its own fields and instances for its vocabs.
My guess is that you're hitting this on a local dev site where all the terrible project_release taxonomy stuff hasn't been properly configured yet. It's all a mess.
But, for example, what does 'drush vget project_release_api_vocabulary' get you? I'm guessing it's empty. There might not even *be* an api compatibility vocab on your site.
Comment #2
grendzy commentedI do have a release taxonomy configured. dww found the culprit: update.php creates "taxonomy_[NAME]" fields in taxonomy_update_7004(). So I think the only way to have one of these fields is to update from Drupal 6.
Maybe we need a variable to store the field name in addition to the vocab id?
Comment #3
dwwI hate to do this, but based on a conference call where we're trying to estimate all the remaining tasks for the d.o D7 launch, we're untagging this one since technically the code as written is going to work for the d.o case. :/ So, instead tagging this as something we should fix before we ship an official 7.x-2.0 release, but it's not blocking d.o D7 anymore.
Comment #4
grendzy commentedThat makes sense. I'll clarify the issue summary.
Comment #4.0
grendzy commentedclarify fieldCondition
Comment #4.1
grendzy commentedapply summary template