Issue

Custom modules, Strongarm configurations and Features are reported on "Failed to get available update data" list

http://example.com/admin/reports/updates

These items are local to the site and will not be available for update.

I suggest to distinguish between modules that are "updatable" and not and to avoid trying to find updates for custom modules and features.

Have you discuss this already ?

CommentFileSizeAuthor
Drupal Update module 1.JPG24.43 KBRefineo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

aklys’s picture

aklys CreditAttribution: aklys commented

For custom modules you can implement hook hook_update_projects_alter and hide project from update list.
Example for module called "mytest":

function mytest_update_projects_alter(&$projects) {
  // Hide a site-specific module from the list.
    unset($projects['mytest']);
}

After creating this function Drupal update manager is not checking for updates of module "mytest".

sheena_d’s picture

sheena_d CreditAttribution: sheena_d commented

The solution in #1 does not, predictably, work for themes. Is there any suggestion for hiding a custom theme from the Update Manager?

the_g_bomb’s picture

the_g_bomb CreditAttribution: the_g_bomb commented

IMHO I don't think that the solution in #1 is the right way to go about things anyway. Update should automatically ignore custom modues, features etc, as I see it.

Having to include a function in every custom module and feature just so that update ignores it seems to me to be the wrong approach.

From the quick look I had, I think the function _update_process_info_list()
in the file: modules\update\update.compare.inc

needs to have some logic to determine whether the module/theme needs to be checked then skipped if appropriate.

For example changing:

    if (!isset($file->info['datestamp'])) {
      $file->info['datestamp'] = 0;
    }

to:

    if (!isset($file->info['datestamp'])) {
      $file->info['datestamp'] = 0;
      continue;
    }

Would check to see if the drupal.org packaging script has set a datestamp and then excludes features and custom modules from the available update report as it won't have, not that I am suggesting using the datestamp as a signifier, but just to highlight that if something more reliable is available then it could work.

the_g_bomb’s picture

the_g_bomb CreditAttribution: the_g_bomb commented

Just for clarification the solution in #3 does fix the issues I'm experiencing with update.module and also the issue I'm experiencing here #1307198: Features not to be reported on "Failed to get available update data" list
edit: wrong issue linked

Refineo’s picture

Refineo CreditAttribution: Refineo commented
Version: 7.8 » 8.x-dev

I reassign this to 8.x-dev so it maybe gets more notice and discussion as new features are implemented in D8 first and then down-ported.

shark’s picture

shark CreditAttribution: shark commented

The change in #3 worked for me (in that by hiding the modules, the system does not appear broken).

But +1 for showing local modules in their own section, with a comment like "These items are local to the site and will not be available for update" as was mentioned in the description.

wylbur’s picture

wylbur CreditAttribution: wylbur commented

We tested the fix in #3, and while it excludes modules like features that do not have a datestamp value, it seems to suppress the notice that Drupal Core needs to be updated.

I toggle the change, and with the new code I don't get the Drupal core notice. But with the original code I do get the core update notice.

Besides that, this does work to avoid reported errors with feature modules failing to retrieve updates.

the_g_bomb’s picture

the_g_bomb CreditAttribution: the_g_bomb commented

I have the suspicion that this method may not work with git deployed modules as well, but I haven't looked into it any further, to be honest.

As mentioned in #1307198: Features not to be reported on "Failed to get available update data" list perhaps the update url is a better indicator as to whether the update module should look for update information.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

@ Thank you for reporting this problem. We rely on issue reports like this one to resolve bugs and improve Drupal core.

Is this issue still a problem?

There has been no activity here for 10 years.

Since we need more information to move forward with this issue, I am keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

More information has not been provided here after 8 months.

Therefor, I am closing this issue.