#2316077 Running without project_release_api_vocabulary - $api_tid can also be false or the empty string

Frodo Looijaard authored Aug 16, 2014 and Neil Drumm committed Aug 16, 2014

#2316077 Running without project_release_api_vocabulary - do not add vocabulary handling to the views SQL query if project_release_api_vocabulary is not defined

Frodo Looijaard authored Aug 16, 2014 and Neil Drumm committed Aug 16, 2014

#2316077 Running without project_release_api_vocabulary - handles the fact that some parts of the code expect, if project_release_api_vocabulary is not defined, an empty string, while others expect a NULL

Fix notices: projects which previously had releases still have release nodes when they are disabled.

Checks the update status of all releases and rebuilds the download
table on projects. Optional argument restricts to a single project.

The display for insecure releases should not filter on recommended
branches, since the regular display for 'Other releases' is also
filtering by update status and we still want to display those here.

This adds a new 'Releases missing security updates' display to the
project_release_download_table view which generates a new header and
table for the Downloads section on project pages.