Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There seems to be some error that caused drush to fail for me starting yesterday.
I tracked it down to the update_status_xml_parser class.
Basically anything after the "terms" section of the xml and before the "releases" section is deleted,
including recommended_major, supported_majors, and default_major (which drush uses).
The xml looks like this for example:
<?xml version="1.0" encoding="utf-8"?>
<project xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>Lightbox2</title>
<short_name>lightbox2</short_name>
<dc:creator>bugz_nz</dc:creator>
<terms>
<term><name>Projects</name><value>Modules</value></term>
<term><name>Projects</name><value>Content display</value></term>
<term><name>Projects</name><value>Media</value></term>
<term><name>Projects</name><value>Javascript Utilities</value></term>
</terms>
<api_version>5.x</api_version>
<recommended_major>2</recommended_major>
<supported_majors>2</supported_majors>
<default_major>2</default_major>
<project_status>published</project_status>
<link>http://drupal.org/project/lightbox2</link>
<releases>
......snipped
My temporary work around is to add a break to the beginning of case 'TERM' and 'TERMS' in the parser start and end tag handlers, to essentially ignore the TERMS section of the xml.
Comments
Comment #1
dugh CreditAttribution: dugh commentedHere's the actual URL drush is fetching with the xml content in the case of installing module lightbox2:
http://updates.drupal.org/release-history/lightbox2/5.x
Comment #2
sunThis might also be the cause for Upgrade Status module not being able to output project titles of not yet ported modules: #269510: Project Title missing from listing of modules not yet ported
Comment #3
dwwUgh. Yes, I recently committed #157514: Add possibility to retrieve a list of projects from the server which did in fact change the XML generated on the server, which in turn seems to have broken update_status. :( I just confirmed this via local testing. Therefore, I backed out that change on d.o and re-ran the script to generate the XML files. So, things should be back to normal for update_status users now. We'll just have to fix the patch for #157514 so that we don't re-break this. Thanks for the report.
Comment #4
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.