in database

on "not null"

function

release file information

This was dead code that was never actually being called anymore.

When Drupal.org renamed 'Installation profiles' to 'Distributions'
(#1314124) it broke the hack in this script that was adding 'variant'
info to the release history feeds for distribution releases. Still a
hack, but at least it's working again. ;)

Fix #703720 by bdragon: (finally) add the drupal.org varnish usage stats processing functionality to project_usage. This version is written as drush commands.

Previously, there was no visual feedback when you submitted the
per-project maintainer form. Now there's a message saying what happened.

Note: this is a hack, but it's better than nothing. ;) The problem is
particularly acute on packaged distributions where there are 6 files.

Previously, the package-release-nodes.php and the general packaging
framework itself had knowledge of a $contents array for the benefit of
project_package. However, this was both wonky and insufficient. Now,
any communication with project_package is the responsibility of the
packaging plugins themselves, instead of complicating the framework.

Download tables were broken on views 6.x-2.13 and higher due to commit
076e78e4270 to views. There was no longer any way to define a custom
JOIN that references other fields in the query, since views is
assuming the 'extra' to a JOIN must reference actual values and is
therefore doing various quoting/escaping tricks. There's now a 'raw'
option when defining 'extra' for a JOIN for this, if you have views
6.x-2.16+5-dev or higher (so long as you have revision 402eed8905).

Previously, project_release had conditional code inside hook_view()
to embed the view of packaged local items if project_package was
installed. Now, project_package just embeds the view into the release
node via hook_nodeapi().

- project_package_release_nodeapi() is only invoked for nodes of type
  'project_release' so we don't need to check for that again.
- Instead of the more expensive COUNT(*) we can just select a single
  row from the respective tables to see if we need to embed the view.

This includes both a new view embedded on the package release node with
details about patches to local items, and a new magic 'patch count' views
field for the {project_package_local_release_item} table with a custom
handler that uses pre_render() to count all the patches from
{project_package_local_patches} for every package/item pair in the view.
Also renamed 'project_package_items' to 'project_package_local_items'
for consistency and to be more self-documenting about what it is.