Hi

I've a new installation of drupal. I created a book using one account and was trying to add a page using another account. But everytime i do it, the parent of the page is set to and it's not displayed anywhere (except in content management in admin) But when i do a preview, it shows the next and up links which are to the book i'm trying to add it to.

Any Ideas
Thanks

Comments

Anonymous’s picture

I've got the same problem and would love to know what the solution is.

vmole’s picture

I have what may be a related problem. I have a collaborative book with a top-level entry "A", and two sub-entries "A1" and "A2". Entries A and A1 were created by one account, and entry A2 by second account. The parent of A1 and A2 is set correctly to A.

  • When I view A, both A1 and A2 show up in the list (correct).
  • When I view A1, The "next" link is not active, nor is there any other indications that A2 exists (wrong).
  • When I view A2, A1 is available as the "previous" link (correct).
  • When I export as HTML, A and A1 show up, but not A2 (wrong).

All with drupal 4.0 on a Debian box. Any ideas?

Just for kicks, I just added a third node ("A3") to the book, using the second account. Curiously, A3 is interlinked correctly with A1, but not A2. All three show up in the A page. When I export, A, A1, and A3 show up. Weirdly, in the
drupal pages, the sub-entries are listed in alphabetical order, but in the HTML export, they show up in creation order (Because I didn't actually name them A1, A2, and A3, that was just for convenience in this post. Confused yet? Only local images are allowed.)

Curiouser and curiouser: I set different weights on each sub-entry, hoping
to control sort order (which worked), and as soon as I had changed the first one, all the links between A1, A2, and A3 started working. My guess is that setting the weight caused drupal to go through and re-set all the next/previous links. But the HTML export still doesn't work - A, A1, and A3 are included, A2 is not.

dries’s picture

Thanks to your excellent report, I managed to reproduce the problem and fixed it in both Drupal 4.1.0 and Drupal CVS. Thanks.