Duplicate entry '71' for key 1 query: [#401456]

I get these two error messages:

# user warning: Duplicate entry '71' for key 1 query: INSERT INTO outline_book (bid, book_vid, uid, default_child_type, default_toc_depth, book_role_perm, book_user_perm) VALUES (65, 71, 3, '', '-1', 0, 0) in /home/mallsand/public_html/sites/all/modules/outline/outline.module on line 667.

# user warning: Duplicate entry '71' for key 1 query: INSERT INTO outline_node (mlid, nid, vid, bid, book_vid, is_default, child_type, toc_depth) VALUES (1180, 65, 71, 65, 71, 1, '', -1) in /home/mallsand/public_html/sites/all/modules/outline/outline.module on line 670

this occurs in a Wiki Page used as the first page of a book. I am using a Wiki Page here in form of a TOC in order to have the wiki feature of automatic redirection to creating the missing pages.

Thanks for the help - great work and much appreciated

Comments

Comment #1

tryitonce CreditAttribution: tryitonce commented 19 March 2009 at 12:36

Yes, the very same here.

Thanks for the help and the module.

Comment #2

beginner CreditAttribution: beginner commented 19 March 2009 at 12:57

@tryitonce: you are replying to yourself! (It happens to me sometimes, too... ) ;)

I'll have a loot at this as soon as I can.

Comment #3

beginner CreditAttribution: beginner commented 19 March 2009 at 13:04

Meanwhile, you can help me a lot if you can give me very precise instructions on how to reproduce on a clean install (clean code, clean database) with only core + this module.

Comment #4

tryitonce CreditAttribution: tryitonce commented 19 March 2009 at 13:44

Replying to myself - so sorry, this is so embarrasing - but may be comes with the job of sitting in front of a screen and no one to talk to around.

I am using a few wiki modules, freelinking and FCKeditor, Outline Designer as well.

I get this error when saving first page of one particular book only. I tried to replicate the error without success so far in another book and on a Clean install on my server at home locally.

The error is just a warning and disappears after reloading the page in question.

I will keep an eye on it and report back later.

For now, I guess, no action for you until I find out more details.

Thanks

Comment #5

beginner CreditAttribution: beginner commented 20 March 2009 at 07:27

Status:

Active

» Postponed (maintainer needs more info)

Don't be embarrassed. We are all suffering from the same disease ;) And I have done worse (blaming a user who didn't file an issue properly, only to find out that the user was myself, a couple of weeks earlier!!) ;)

I am using the module myself and never encountered this particular error. This bug would be critical, though: some data would have failed being inserted into the database. In the long run, the related pages may not behave as expected.

Things like this can happen when using a combination of modules. Some modules may be incompatible. We may be able to fix it, but you must first be able to reproduce it and isolate which combination of module (is this is the problem) causes this bug to occur. You must proceed by elimination.