You are here

Home » API reference » Update Status Advanced Settings 6

README.txt in Update Status Advanced Settings 6

Same filename and directory in other branches
  1. 7 README.txt
The "Update status advanced settings" module extends the administrative
interface for Drupal core's "Update status" module. It provides
additional configuration options on the "Settings" tab of the
"Available updates" report, located at: admin/reports/updates/settings

  Administer >> Reports >> Available updates >> Settings 

These advanced settings allow site administrators fine-grained control
to ignore certain projects on the available updates report, even when
a newer version is available. Administrators can also choose to ignore
a specific recommended release of a given project.

A more appropriate name for this module might be "Update status
advanced noise filter", since that's really what it does -- it lets
administrators filter out noise in their available updates report so
that they can focus on the signal of important updates they should
know about.

There are many reasons why an administrator might need to ignore a
certain "noisy" project and/or a specific version. For example:

- The administrator has made local modifications to a module, and does
  not wish to be notified about newer releases all the time.

- The maintainer of the module is not very careful, and frequently
  puts out releases that the site administrator does not wish to
  upgrade to.

- The maintainer might have released a newer official version which is
  incompatible with other modules that the site is depending on. For
  example, perhaps the site cannot upgrade to CCK version 5.x-1.5,
  since that breaks compatibility with specific CCK field modules in
  use on the site which the administrator cannot upgrade yet.

- The maintainer of the module might have released a new official
  version with known bugs and the administrator does not wish to upgrade.

If the site administrator chooses to ignore a project or specific
release of a project, there is a text area to optionally enter a note
indicating why. If this note is defined for a project


Send feature requests and bug reports to the issue queue for the
Update status advanced settings module:
http://drupal.org/node/add/project_issue/update_advanced


Written by: Derek Wright ("dww") http://drupal.org/user/46549

Inspired by similar functionality in the "Update status" module for
Drupal version 5.x in the contributions repository, by Earl Miles and
Derek Wright (http://drupal.org/project/update_status).

File

README.txt
View source 
  1. The "Update status advanced settings" module extends the administrative

  2. interface for Drupal core's "Update status" module. It provides

  3. additional configuration options on the "Settings" tab of the

  4. "Available updates" report, located at: admin/reports/updates/settings

  5. 

  6.   Administer >> Reports >> Available updates >> Settings 

  7. 

  8. These advanced settings allow site administrators fine-grained control

  9. to ignore certain projects on the available updates report, even when

  10. a newer version is available. Administrators can also choose to ignore

  11. a specific recommended release of a given project.

  12. 

  13. A more appropriate name for this module might be "Update status

  14. advanced noise filter", since that's really what it does -- it lets

  15. administrators filter out noise in their available updates report so

  16. that they can focus on the signal of important updates they should

  17. know about.

  18. 

  19. There are many reasons why an administrator might need to ignore a

  20. certain "noisy" project and/or a specific version. For example:

  21. 

  22. - The administrator has made local modifications to a module, and does

  23.   not wish to be notified about newer releases all the time.

  24. 

  25. - The maintainer of the module is not very careful, and frequently

  26.   puts out releases that the site administrator does not wish to

  27.   upgrade to.

  28. 

  29. - The maintainer might have released a newer official version which is

  30.   incompatible with other modules that the site is depending on. For

  31.   example, perhaps the site cannot upgrade to CCK version 5.x-1.5,

  32.   since that breaks compatibility with specific CCK field modules in

  33.   use on the site which the administrator cannot upgrade yet.

  34. 

  35. - The maintainer of the module might have released a new official

  36.   version with known bugs and the administrator does not wish to upgrade.

  37. 

  38. If the site administrator chooses to ignore a project or specific

  39. release of a project, there is a text area to optionally enter a note

  40. indicating why. If this note is defined for a project

  41. 

  42. 

  43. Send feature requests and bug reports to the issue queue for the

  44. Update status advanced settings module:

  45. http://drupal.org/node/add/project_issue/update_advanced

  46. 

  47. 

  48. Written by: Derek Wright ("dww") http://drupal.org/user/46549

  49. 

  50. Inspired by similar functionality in the "Update status" module for

  51. Drupal version 5.x in the contributions repository, by Earl Miles and

  52. Derek Wright (http://drupal.org/project/update_status).

  53.