Project releases module did not create a vocabulary called "Project release API compatibility

It was (temporarily) removed as part of #642106: Add native support in project_release for a "Release type" vocabulary and #642110: Add native support in project_release for a "Security update" term. Those are both listed as 6.x-1.0 blocker issues.

Can't decide if this issue should be marked duplicate with #642106 or postponed. I guess I'll leave it open here so it's more likely people will see it with this title -- I certainly don't expect anyone to be able to figure out that this is caused by #642106 just from searching the queue...

To fix it, yes, you can manually create a new vocabulary, and then you just need to set the variable project_release_api_vocabulary to the vocabulary ID. So, if you create the new vocab and it's ID 5, you'd put something like this in your settings.php file:

$conf['project_release_api_vocabulary'] = 5;

Cheers,
-Derek

I resolved this by creating the "Project release API compatibility" vocabulary under Administer › Content management > Taxonomy. Then you need to update the view as well. So go into Administer › Site building › Views and choose edit on the "project_release_by_project" view. Under filters, click on "Project release: API compatability term exposed ". Then click the gear next to it. Set the vocabulary to "Project release API compatibility". Save your view.

Hope that helps.

I have just followed the instructions and this appears to solve the problems as observed by others. However, on closer inspection, I see that the %api variable is not being populated for the release version string template.

I see from http://drupal.org/node/116544 that it the variable is expected to be blank if there are no Taxonomy values defined as mentioned on the project instructions.

"Note: If you have not configured the "Project release API compatibility" vocabulary as described in the previous section, the api variable will always be blank. However, if you have configured this vocabulary, then the api variable will contain the value of the term associated with a release."

Is this a known issue, and is there a fix?

Thanks in advance.

subscribing

sub

subscribe

sub...

This is a very important module for Drupal and Drupal Developers who would like to use Drupal for their project management IMHO. I wonder why I see the issue submitted here left ignored for almost a year now. Makes me uneasy about whether I should invest in using the project and issue tracker...

I have been trying to build a completely Drupal based project management system for a startup, and I just run into this issue too. Clicking on view all releases returns the same error here.

Creating the taxonomy manually takes care of the error, but it doesn't solve the underlying issues.

subscribing

Confirming this issue still exists, but manually setting project_release_api_vocabulary doesn't solve everything. ( I used `drush vset project_release_api_vocabulary 3`) I still can't select supported releases for a project. I also noticed that things get pretty broken if projects are created with project module before project release module is enabled. I'm hacking on the code and will post a patch if I make progress. Meanwhile, any advice would be appreciated. It's kinda sad that a module so essential to drupal.org is in such a sorry state....

same problem

Is this project dead?

2 years later the issue is still alive...

I am closing this issue, as Drupal 6 is no longer supported.