Skip to main content
replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
Source Link

An update URL is formatted as:

http://updates.drupal.org/release-history/[project-name]/[api-version]

So for Views v7, for example, that would be:

http://updates.drupal.org/release-history/views/7.x

I think that's as much information as Drupal.org makes available about modules via its API. You won't find a structured way to query information about hooks, for the same reasons we talked about in your similar recent questionyour similar recent question

An update URL is formatted as:

http://updates.drupal.org/release-history/[project-name]/[api-version]

So for Views v7, for example, that would be:

http://updates.drupal.org/release-history/views/7.x

I think that's as much information as Drupal.org makes available about modules via its API. You won't find a structured way to query information about hooks, for the same reasons we talked about in your similar recent question

An update URL is formatted as:

http://updates.drupal.org/release-history/[project-name]/[api-version]

So for Views v7, for example, that would be:

http://updates.drupal.org/release-history/views/7.x

I think that's as much information as Drupal.org makes available about modules via its API. You won't find a structured way to query information about hooks, for the same reasons we talked about in your similar recent question

Source Link
Clive
  • 167.9k
  • 19
  • 303
  • 337

An update URL is formatted as:

http://updates.drupal.org/release-history/[project-name]/[api-version]

So for Views v7, for example, that would be:

http://updates.drupal.org/release-history/views/7.x

I think that's as much information as Drupal.org makes available about modules via its API. You won't find a structured way to query information about hooks, for the same reasons we talked about in your similar recent question