After installing this module it reports two sites (originally clones of each other) the version to be 6.0 instead of 6.28: Drupal core 6.0 -> 6.28 (SECURITY UPDATE). Version 6.28 is the current version of both sites.

Also I get this message: Simplenews 6.x-2.0-alpha5 -> undefined (SECURITY UPDATE).
6.x-2.0 alpha 5 is the latest version and no info about a security update is available for this version.

Comments

sam hermans’s picture

sam hermans commented

Hi,

First of all i would like to thank you for testing this out..

Could you provide me with the ID of one of your sites ? When using the webinterface you should be able to inspect the div containing your site, and it should be "group_*****".

As for the simplenews module .. the page at http://updates.drupal.org/release-history/simplenews/6.x indeed suggests that the current version for drupal6 should be simplenews 6.x-2.0-alpha5 so this is a bug on my end for sure. I think it's related to the <supported_majors>1,2</supported_majors>.

Sam

promes’s picture

promes
Primary language Dutch
commented

I presume you like the info from this page: https://www.drupalstatus.org/account.
As far as I can see it is group 9933 and 9934.
The listing of all groups:

<div id="header-content"> … </div><div id="wrapper"><div id="sites"><div id="group_9938" class="sortable" sortprio="100000" updates="0"> … </div><div id="group_9947" class="sortable" sortprio="100000" updates="0"><div id="site_9947" class="site no_report_available"><div class="site_box no_report_available "> … </div><div class="open_button"> … </div></div></div><div id="group_9933" class="sortable" sortprio="2" updates="2"> … </div><div id="group_9934" class="sortable" sortprio="2" updates="1"> … </div><div id="group_9939" class="sortable" sortprio="1" updates="2"> … </div><div id="group_9940" class="sortable" sortprio="1" updates="2"> … </div><div id="group_9931" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9930" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9935" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9932" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9936" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9937" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9942" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9943" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9941" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9944" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9945" class="sortable" sortprio="0" updates="0"> … </div><div id="group_9948" class="sortable" sortprio="0" updates="0"> … </div></div>

promes’s picture

promes
Primary language Dutch
commented

Hello Sam,,

In the weekly status report the Simplenews still is flagged as to be updated. See your comment #1.
Info: the Drupal core 6.0 -> 6.28 hasn't been solved, so it is in the weekly status as well.

sam hermans’s picture

sam hermans commented

Could you just let me know if you are still having this issue ?

promes’s picture

promes
Primary language Dutch
commented

Hi Sam,

See https://drupal.org/comment/8369823#comment-8369823.

Good luck

sam hermans’s picture

sam hermans commented

This is so weird. So i just set up a new clean drupal6 and the fetch reports:

{"system_status":{"core":{"drupal":{"version":"6.29"}},"contrib":{"system_status":{"version":"6.x-2.1"}

When i run the check on your site i get:
{"system_status":{"core":{"drupal":{"version":"6.0"}},"contrib":"{system_status":{"version":"6.x-2.1"}

I know i'm asking a lot but it would mean a great deal to me if you could execute the following script in your documentroot .. just create a debug.php or so next to index.php

<?php
require_once './includes/bootstrap.inc';
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);

$drupal_modules = module_list();
$system_modules = array();

foreach($drupal_modules as $name) {
  $path = drupal_get_path('module', $name) . '/' . $name . '.info';
  $info = drupal_parse_info_file($path);
  $system_modules[$info['project']] = $info;
}

foreach ($system_modules as $module) {
   if(isset($module['project'])) {
     if($module['project'] == "drupal") {
       $res['core']['drupal'] = array("version" => $module['version']);
   } else {
      $res['contrib'][$module['project']] = array("version" => $module['version']);
    }
  }
}

echo "-- system modules--";
print_r($system_modules);
echo "--- res --";
print_r($res);
sam hermans’s picture

sam hermans commented

PS: I just created another release of the Drupal6 version of system_status. This sould fix the issue you where having with the core version nr.

promes’s picture

promes
Primary language Dutch
commented
Issue summary: View changes
Status: Active » Fixed

Hi Sam,

Today I was looking in file system_status_status.page.inc and found function system_status_status_page.
Since I have still two strange results in my todays overview I created a small program with some of your code and was able to see the version results my sites were returning to you. Your reported versions matched mine in the list.
Conclusion: something should be wrong in my sites. I found out some of my custom modules had wrong project information in the info files. After changing this, all results were correct.
I presume your previous efforts resolved some problems and the last miles were found as described in this comment.
I close this issue because I think your module is behaving correctly.

Thanks for your patience and help and of course for this great module.

PROMES

sam hermans’s picture

sam hermans commented
Status: Fixed » Closed (works as designed)

Great news! :)