Release Monitor questions - follow up

Hi Doug,

Thanks for a great module!

Although it is still in dev, after you mentioned that Release Monitor only worked with PHP5, I finally decide to make the move to PHP5. (May I suggest to make it more obvious in your documentation that it does not work at all with PHP4 for the newer users).

So out of curiosity and in order to fully experiment the Release Monitor module, I moved my entire Drupal to another vhost inside my server that had PHP5 although I wasn't sure if it would break other functionalities in the system. Not clear if everything is PHP5 compatible yet but so far, so good, except for a few javascript errors that did not show up within PHP4 (Strange since for me these are normally not related to PHP issues but I'll come back on that in a another post in the forums).

And now some questions regarding the updating of the modules via the Release monitor

1. Status messages - Releases - Drupal Version Status
link: /admin/settings/releasemonitor

I get these messages:

Status not completely retrieved for devel; views; nodewords. See Releases.
or
Status not completely retrieved for ; devel; jstools; video; views; tinymce; nodegoto; nodewords. See Releases.

And finally as an example, after a third attempt:

The latest status has been retrieved for all active modules. See Releases.

Why does it always take more than 1 attempt to get the full list retrieved?
Is it normal or is it a problem? I am not sure yet.

2. The list of modules that need updating - Release monitor
link: /admin/build/releases

Status not completely retrieved for (address, cart, auction, ecviews, ec_anon, ec_mail, payment, paypal, product, shipping, store, subproducts, tax, countdowntimer_fr, securepages, securesite, ec_devel) - refresh this page or run cron.php

The long list...

name description release major minor cvstag cvsid
...

In the list I receive, I get the whole list of modules installed. Great since they seem to all show up.
Despite updating physically the modules by uploading them, setting them up in Modules and then refreshing cron and/or thepage itself, why do I receive again the same list of modules that need updating?

Examples of modules always in there despite updating:

adsense Display Google AdSense ads on your site to earn revenue. 5.x-1.x-dev
DRUPAL-5--1-2 1.50.2.15
adsense Display Google AdSense ads on your site to earn revenue. 5.x-1.x-dev
DRUPAL-5--1-2 1.50.2.15
cck Allows administrators to define new content types. 5.x-1.2
DRUPAL-5--1-3 content 1.90.2.25, content_copy 1.1.2.5, fieldgroup 1.1.4.12, nodereference 1.39.2.3, number 1.34.2.6, optionwidgets 1.10.2.3, text 1.41.2.7, userreference 1.30.2.6
nodelist Construct alphabetical listing of nodes 5.x-1.x-dev
DRUPAL-5 1.11.2.3
pdfview Enables users to view nodes as PDF. 5.x-1.0
DRUPAL-5--1-1 1.37.2.3
slideshow_creator Create true slideshows using any image over internet with many other features. 5.x-1.13 DRUPAL-5--1-15 1.1.2.5
tagadelic Tagadelic makes weighted tag clouds from your taxonomy terms. 5.x-1.x-dev
DRUPAL-5 1.36.2.1
imce An image/file uploader and browser supporting personal directories and user quota. 5.x-1.x-dev
DRUPAL-5 1.8.2.25
tinymce The most popular WYSIWYG editor for advance content. 5.x-1.x-dev
DRUPAL-5 1.90.4.11

3. In the watchdog, I get many logs (sometimes useful) from Release Monitor like:

warning releasemonitor 7 Feb 2007 - 20:33 A newer content module is available admin

Could you make these messages show up more clearly straight into the Releases page itself? Or by adding a special link? Inserting those messages within the Releases pages, it would most certainly save us from always going back and forth between the watchdog and Release Monitor pages to check things out.

Again many thanks for a great module,
Jean