Details
-
Type: Bug
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.7.30
-
Fix Version/s: None
-
Component/s: Drupal Integration Modules
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
-
Verified?:No
Description
- Drupal modules which define the "project" property in their *.info file will be included in "available updates" checks performed by the Update status module, which checks drupal.org for the release history of that module/project.
- CiviCRM and its included Drupal modules no longer have a release history on drupal.org (since when? not sure.)
- Because CiviCRM's Drupal modules still define the "project" property in their *.info file, the Update status module tries in vain to check drupal.org for their release history, and then reports the failure with the error message "Failed to get available update data for one project." or "Failed to get available update data for @count projects."
We could eliminate this error by removing the "project" property from the *.info files of CiviCRM's various drupal modules.
Reference: https://www.drupal.org/docs/7/creating-custom-modules/writing-module-info-files-drupal-7x#project