I have a custom theme (or module) on drupal 6 site.
a) Is there any option in info file to ignore this project when searching for available updates on d.o.?
b) May I set localhost as update server in info file?
c) Is "Update status advanced settings" module the only way to ignore projects?

I do not want to hammer d.o. with my custom projects at every update scan..

Comments

dww’s picture

dww
we/he/they
commented
Assigned: Unassigned » dww
Status: Active » Fixed

a) no.
b) yes. you can set "project status url" in your .info file if you really want.
c) yes, unfortunately. that's why that module exists, since that functionality was deemed "too complicated" for inclusion in core.

however, i really wouldn't worry about it. every update scan == 1/day usually (or 1/week if so configured), and "hammer" == a single http fetch, which d.o handles bazillions of every day.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Project: Drupal core » Update Status Advanced Settings
Version: 6.x-dev » 6.x-1.x-dev
Component: update.module » Code
Status: Fixed » Active

Enabled the update_advanced module, but my custom theme is not listed on page admin/reports/updates/settings.
Is it a bug or is it intentional functionality?

Notes:
1. The custom theme is listed on page admin/reports/updates with status "No available releases found"
2. I did not set the "project status url" in .info file

hanv3’s picture

hanv3 commented

I am using a module not known to drupal.org. I get on the available update page (drupal version 6.2) the text "No available releases found" .

Someone advised me to use this special module to exclude my module from the dayly or weekly scan. The problem is that on the drupal module list you see all modules and on the list on the available updates page you can select only the known (to drupal.org) modules.

Is it possible to get here also the unknown (to drupal.org) modules?

bxlredlabel’s picture

bxlredlabel commented

Yet no way to ignore some project during the daily scan? A modification in the .info file maybe?
This would be a good ability when you develop a custom theme since drupal don't appear up to date even if all the modules are up to date (except the base theme obviously).

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Status: Active » Fixed

I found that the answer for the question (a) is YES
just remove the "project" line from the info file and it will not show up on the "Available updates" page

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

mugginsoft.net’s picture

mugginsoft.net commented

Comment 5 above is effective.
I found it necessary to disable and then re-enable the module before it was de-listed from the update scan.

ressa’s picture

ressa
he/him
commented

Thanks @Pasqualle (in #5): I can confirm that commenting out (put a semicolon at the beginning of) the line that says ; project = "YOUR_THEME_NAME" in the info file works for themes, without having to install the 'Update status advanced settings' module.

ressa’s picture

ressa
he/him
commented
Issue summary: View changes

I added it to the documentation: https://www.drupal.org/docs/develop/theming-drupal/creating-sub-themes#s....