To reproduce:
On 2011-03-02 ran
Home > Administer > Reports > Available Updates
Expected behavior
module securepages 6.x-1.8 installed, 6.x-1.9 available
(per security advisory DRUPAL-SA-CONTRIB-2011-011)
Actual behavior
all modules green (current) including securepages 6.x-1.8
Note: page http://drupal.org/project/securepages indicates module version 6.x-1.9 was updated 2011-Feb-23
Environment (reported from cpanel v11.28.83)
Hardware i686
OS: linux
Webserver: Apache 2.2.17
PHP: 5.2.15
MySQL: 5.1.52
Additional info:
1. recent log entries shows a number of attempts to access page /admin/login.php failing with access denied
2. at time of discovery last checked showed 21+ hours previously, clicked on check manually and results were same.
3. recent log entries shows 9 occurrances at same time of error
user: known good admin login from known good ip address
location /admin/reports/updates/list
message:
Duplicate entry 'sites/all/themes/mysiteinitials405/mysiteinitials405.info' for key 'PRIMARY' query: INSERT INTO system (name, owner, info, type, filename, status, throttle, bootstrap) VALUES ('mysiteinitials405', 'themes/engines/phptemplate/phptemplate.engine', 'a:11:{s:4:\"name\";s:6:\"mysiteinitials405\";s:11:\"description\";s:62:\"mysiteinitials405 theme - css changed, module theme overrides implemented\";s:7:\"version\";s:6:\"mysiteinitials405\";s:4:\"core\";s:3:\"6.x\";s:6:\"engine\";s:11:\"phptemplate\";s:7:\"regions\";a:11:{s:6:\"header\";s:6:\"Header\";s:7:\"navmenu\";s:15:\"Navigation Menu\";s:15:\"upper_rt_corner\";s:15:\"upper_rt_corner\";s:12:\"sidebar_left\";s:12:\"Left sidebar\";s:13:\"sidebar_right\";s:13:\"Right sidebar\";s:11:\"content_top\";s:11:\"content top\";s:14:\"content_bottom\";s:14:\"content bottom\";s:5:\"user2\";s:5:\"user6\";s:5:\"user3\";s:5:\"user3\";s:5:\"user4\";s:5:\"user4\";s:6:\"footer\";s:6:\"footer\";}s:8:\"features\";a:7:{i:0;s:4:\"logo\";i:1;s:4:\"name\";i:2;s:6:\"slogan\";i:3;s:7:\"mission\";i:4;s:7:\"favicon\";i:5;s:13:\"primary_links\";i:6;s:15:\"secondary_links\";}s:11:\"stylesheets\";a:1:{s:3:\"all\";a:6:{s:12:\"mysiteinitials_base.css\";s:36:\"sites/all/themes/mysiteinitials405/mysiteinitials_base.css\";s:16:\"mysiteinitials_form_box.css\";s:40:\"sites/all/themes/mysiteinitials405/mysiteinitials_form_box.css\";s:15:\"mysiteinitials_product.css\";s:39:\"sites/all/themes/mysiteinitials405/mysiteinitials_product.css\";s:12:\"mysiteinitials_rpts.css\";s:36:\"sites/all/themes/mysiteinitials405/mysiteinitials_rpts.css\";s:13:\"mysiteinitials_shops.css\";s:37:\"sites/all/themes/mysiteinitials405/mysiteinitials_shops.css\";s:12:\"mysiteinitials_user.css\";s:36:\"sites/all/themes/mysiteinitials405/mysiteinitials_user.css\";}}s:7:\"scripts\";a:1:{s:17:\"js/mysiteabbrev_misc.js\";s:41:\"sites/all/themes/mysiteinitials405/js/mysiteabbrev_misc.js\";}s:10:\"screenshot\";s:38:\"sites/all/themes/mysiteinitials405/screenshot.png\";s:3:\"php\";s:5:\"4.3.5\";}', 'theme', 'sites/all/themes/mysiteinitials405/mysiteinitials405.info', 0, 0, 0) in /home/boo/public_html/modules/system/system.module on line 822.
updates may have been applied at this time but no update errors were reported.
Comments
Comment #1
mdlueck commentedSubscribe:
Please see my reply in the Secure Pages mod queue: http://drupal.org/node/1079908#comment-4174118
This seems to be a 100% regular problem with the new "Available Updates" facility in D6 handling security updates. 100% of the time a contrib mod has had a security update since D6 this sort of nonsense happens.
I have never gotten this sort of error applying a non security update "Available Updates" told me was available.
Thank you sfbob for making the effort to open a bug report against Drupal core.
Comment #2
mdlueck commentedThe situation was explained here: http://drupal.org/node/1079908#comment-4177166
I will quote from that post:
I agree! Even the six hours is bad enough... very unsettling to be responding to a security notice and have the system tell you to immediately go back to the "insecure" version!
Comment #3
sfbob commentedProblem has been fixed, explanation in
http://drupal.org/node/1079908
Closing
Comment #4
mdlueck commented@sfbob #3: Yes that is the explanation, however it should have never happened. Drupal core developers did not come up with a good enough design if even for 6 hours the "Available Updates" mod will warn "go back!"