Drush currently identifies the type of project (module, theme, distribution, etc.) using a vocabulary term that we used to use on Drupal.org when on Drupal 6. Something like this:
This was never meant to be used this way. It is very brittle (because it relies on the name of a taxonomy term, that is not a primary key). We broke it a few times in the past.
On Drupal 7, we now have different project types (node types) for the different project types. We added a <type> key in the XML:
They are guaranteed to be stable, even if we reserve the right to add new values in the future.
We are not using vocabulary anymore for this. So the old keys were missing from the XML when the Drupal 7 version went live. Yesterday, we deployed a compatibility fix that adds back the old keys.
Drush needs to be updated (all supported branches, ideally) to use this new format, as we would like to deprecate the old format as soon as possible.
The text was updated successfully, but these errors were encountered:
damz commentedNov 6, 2013
Drush currently identifies the type of project (module, theme, distribution, etc.) using a vocabulary term that we used to use on Drupal.org when on Drupal 6. Something like this:
This was never meant to be used this way. It is very brittle (because it relies on the name of a taxonomy term, that is not a primary key). We broke it a few times in the past.
On Drupal 7, we now have different project types (node types) for the different project types. We added a
<type>key in the XML:The possible values for this key are:
They are guaranteed to be stable, even if we reserve the right to add new values in the future.
We are not using vocabulary anymore for this. So the old keys were missing from the XML when the Drupal 7 version went live. Yesterday, we deployed a compatibility fix that adds back the old keys.
Drush needs to be updated (all supported branches, ideally) to use this new format, as we would like to deprecate the old format as soon as possible.
The text was updated successfully, but these errors were encountered: