user warning: Duplicate entry 'sites/all/modules/seo_checklist/seochecklist.module' for key 1 query: INSERT INTO system (name, info, type, filename, status, throttle, bootstrap) VALUES ('seochecklist', 'a:10:{s:4:\"name\";s:15:\"\"SEO\" Checklist\";s:11:\"description\";s:52:\"A Search Engine Optimization checklist for Drupal 6.\";s:4:\"core\";s:3:\"6.x\";s:7:\"package\";s:15:\"\"SEO\" Checklist\";s:7:\"version\";s:7:\"6.x-2.0\";s:7:\"project\";s:13:\"seo_checklist\";s:9:\"datestamp\";s:10:\"1249685460\";s:12:\"dependencies\";a:0:{}s:10:\"dependents\";a:0:{}s:3:\"php\";s:5:\"4.3.5\";}', 'module', 'sites/all/modules/seo_checklist/seochecklist.module', 0, 0, 0) in /usr/home/hoslo/public_html/includes/module.inc on line 147.
Comments
Comment #1
sam mooreYep, I'm getting this too.
Ran update.php - no fix
Attempted to enable module - can't do it.
There doesn't seem to be an uninstaller.
Next action will be to delete module's tables from the database, and code from /modules, and start over - losing all settings for all sites :-(
Any ideas appreciated.
Comment #2
eclipsegc commentedSo... if I understand correctly, the issue here is that the tables in question already exist, and already have these entries in them. You need to uninstall the 1.x version before installing the 2.x version. If you can't do that definitely drop the old module tables, and files and go with the 2.x code. I would imagine that "previous" settings are rather trivial since you're just going to click the button that detects installed modules and you're basically done. Is there something I'm not understanding here?
Eclipse
Comment #3
Starminder commentedFair enough, just thought you should know this happens. Not all users will know which tables to drop, perhaps a script can be provided?
Comment #4
sam mooreOK, this worked for me:
- enabled the new module
- disable the new module
- uninstall
- re-enable the module.
Lost all the checklist data for my various sites, which will freak my clients out, but at least the SQL is behaving.
Comment #5
venusrising commentedSame issue on two sites here
Comment #6
robbdavis commentedSame issue here. New install of 2.0 threw a bunch of duplicate entry errors. Tried uninstalling old version and it still didn't work (although now that I think about it, I could have probably tried clearing my cache after uninstalling).
Regardless, there is some kind of problem here.
Comment #7
rornelas commentedI am getting the same error after I have remove the old checklist folder and deleted the seo_checklist, seo_groups tables. I have tried to enable the new module, but it fails to enable. Also tried clearing the cache. Any other thoughts?
Here is the error message...
user warning: Duplicate entry 'sites/all/modules/seo_checklist/seochecklist.module' for key 1 query: INSERT INTO system (name, info, type, filename, status, throttle, bootstrap) VALUES ('seochecklist', 'a:10:{s:4:\"name\";s:15:\"\"SEO\" Checklist\";s:11:\"description\";s:52:\"A Search Engine Optimization checklist for Drupal 6.\";s:4:\"core\";s:3:\"6.x\";s:7:\"package\";s:15:\"\"SEO\" Checklist\";s:7:\"version\";s:7:\"6.x-2.0\";s:7:\"project\";s:13:\"seo_checklist\";s:9:\"datestamp\";s:10:\"1249685460\";s:12:\"dependencies\";a:0:{}s:10:\"dependents\";a:0:{}s:3:\"php\";s:5:\"4.3.5\";}', 'module', 'sites/all/modules/seo_checklist/seochecklist.module', 0, 0, 0) in /home/ornelaso/public_html/includes/module.inc on line 147.
user warning: Duplicate entry 'sites/all/modules/seo_checklist/seochecklist.module' for key 1 query: INSERT INTO system (name, info, type, filename, status, throttle, bootstrap) VALUES ('seochecklist', 'a:10:{s:4:\"name\";s:15:\"\"SEO\" Checklist\";s:11:\"description\";s:52:\"A Search Engine Optimization checklist for Drupal 6.\";s:4:\"core\";s:3:\"6.x\";s:7:\"package\";s:15:\"\"SEO\" Checklist\";s:7:\"version\";s:7:\"6.x-2.0\";s:7:\"project\";s:13:\"seo_checklist\";s:9:\"datestamp\";s:10:\"1249685460\";s:12:\"dependencies\";a:0:{}s:10:\"dependents\";a:0:{}s:3:\"php\";s:5:\"4.3.5\";}', 'module', 'sites/all/modules/seo_checklist/seochecklist.module', 0, 0, 0) in /home/ornelaso/public_html/includes/module.inc on line 147.
Comment #8
sam mooreYou could try deleting the entries relating to the module.
Might be a good idea to uninstall first - not sure about that part.
Stop here if you're not comfortable in mysql.
And of course back up your database first.
You'll want to go into your site's database and find the table called "system".
Now look for a row whose "name" field has the value "seochecklist". Delete that row.
So, from the console it would be something like
mysql> use ::your database name::;
mysql>SELECT * FROM 'system' WHERE 'name'='seochecklist';
mysql> DELETE FROM 'system' WHERE 'name'='seochecklist';
The "SELECT" line isn't really necessary; I just like to look at stuff before I delete it.
You could of course do this from a graphical manager like Webmin or phpMyAdmin.
After doing this, you should be able to do a fresh install. You've lost all your data for the checklist, but no biggie I guess.
You'll have to do this for each of your sites.
UPDATE - in the older version of the module I believe the 'name' value is SEOChecklist, not seochecklist.
Comment #9
ben finklea commentedThanks, Sam. Sorry that it's difficult. You might want to backup your database and/or print out the SEO Checklist screen from the admin section of your site before installing the new module.
Comment #10
sam mooreNo sweat.
Thanks again for the module.
Comment #11
kbell commentedHey, could you guys maybe fix this? I've got 5 sites I manage that I'm having to do all of this (and losing all my date, and my clients are NOT happy about it at all). There was a recent update but this was still broken (this bug was true for the last version as well). This is a nontrivial problem, really. :-(
Thank you for an otherwise excellent module, and for the great work that you've done.
Cheers,
Kelly
Comment #12
tamhas commentedTagging this won't fix really doesn't cut it. At the very, very least, you need to put detailed instructions of the required steps in the release notes, but recognize that, if this involves having to do SQL clean-ups of existing data and losing all settings, this will be a great way to keep people from upgrading. You really need a technique to handle the upgrade.
Comment #13
Turkish Delight commentedA view from shell of the table pre-deletion:
sites/all/modules/seo_checklist/SEOChecklist.module | SEOChecklist | module | | 0 | 0 | 0 | -1 | 0 | a:10:{s:4:"name";s:15:""SEO" Checklist";s:11:"description";s:52:"A Search Engine Optimization checklist for Drupal 6.";s:7:"package";s:15:""SEO" Checklist";s:7:"version";s:13:"6.x-1.0-beta3";s:7:"project";s:13:"seo_checklist";s:9:"datestamp";s:10:"1235159158";s:4:"core";s:3:"6.x";s:12:"dependencies";a:0:{}s:10:"dependents";a:0:{}s:3:"php";s:5:"4.3.5";} |
After uninstalling my older version and manually deleting this from system, I can confirm that the error goes away. Thank you Sam for the suggestion.
Comment #14
drupalhouston commentedI found that I got this issue because I pasted the updated module files into the previous versions' folder. The module names had different capitalization and created a conflict. The script would run the first module and reach errors on the second module in the folder.
After deleting the module and deleting the entry 'modules/seo_checklist/SEOChecklist.module' in the system table, everything worked again.
If I replaced the folder rather than pasting into the same folder, everything would have been ok.
Comment #15
dianaxondie commentedThis is awful. This has already wasted an hour of my time and I still can't get the error to go away. Are the maintainers of this module working on a real fix for this?
Comment #16
ben finklea commentedThe fix is easy but would delete the data generated by the 1.0 version of the module. We basically had to make a choice between getting the module secure by following Drupal development guidelines and preserving the data on the old module. Neither choice was going to be popular but I think for the future of the module, we did the right thing. Security and good code should come first. (You could argue that I should have done it properly in the first release and you'd be right - it's my first module.)
There are detailed instructions on getting the new version of the module up and running on the module's project page. I will see that these instructions make it into the Readme on the next release.
Incidentally, there is hardly any difference in the functionality and only a handful of SEO suggestions introduced in 2.0 of this module. It is primarily a rewrite of the underlying code. If you're happy with the old version of the module, there is no need to upgrade. Of course new releases of the module will include more SEO information and suggestions so in the long run you'd be better off upgrading. But, for now, there is no good reason to make the change.
I'm sorry if I've wasted your time. Hopefully, you've saved more time by using the module than you've lost trying to upgrade.
Regards,
--Ben Finklea
Comment #17
Goonjo commentedtry deleting in out of the sites/all/modules folder and just putting it in the regular ol' modules folder on root. I tried all of the above to no avail - but this trick fixed it up.
Comment #18
Goonjo commentedtry deleting in out of the sites/all/modules folder and just putting it in the regular ol' modules folder on root. I tried all of the above to no avail - but this trick fixed it up.
Comment #19
webel commentedAm having exactly the same problem. It's a shame when this was recommended as a security update (otherwise I would not have bothered upgrading).
I have read all of these postings thoroughly, and am confused about how to proceed, not least because people have recommended "uninstalling" when this module does not appear under /admin/build/modules/uninstall. Could the maintainers please provide now exact steps for successful upgrade of this module.
Comment #20
webel commentedOk, now I see the instructions on the project page:
C'mon guys, that has to be in the README.txt ! When prompted to upgrade due to a security advice nobody would think to then also read the project page. Too late for me. I'll see what I can do to recover (and remain grateful to Volacci and others for this excellent module).
Comment #21
webel commented@Ben who wrote:
Then why are we given a security directive that says we should upgrade ?
Comment #22
kosmik commentedI had just upgraded my site to Drupal6 from 5 which had SEO Checklist 1.X.
Surely I had that dreaded "duplicate entry" warning too. Spent 2 hrs uninstall/install and whatever without good result.
So I thought of restoring the DB, the one just before I install new SEO Checklist module and uploaded 'old' version of seo_checklist 6.x-1.0-beta3. No error seen, good!
Then deleted whole folder of "seo_checklist" (1.0-beta3) and uploaded ver 2. Goto phpMyAdmin, select DB, select table "seo_checklist" and run SQL as suggested:
UPDATE system SET name = 'seochecklist', filename = REPLACE(filename, 'SEOChecklist', 'seochecklist'), status = 1 WHERE type = 'module' AND name = 'SEOChecklist'Good, no error again. Done.
Comment #23
catchlight commentedExactly the same issue with an error on line 147, etc, etc. I'm not a developer so I'll be un-installing and re-installing. (Thanks for the tip, guys)
A complete re-write for this module in Drupal 7 perhaps ???