user warning message + no child pages
| Project: | Book Expand |
| Version: | 5.x-1.0.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | dwees |
| Status: | closed |
Jump to:
Hi,
I have installed this module on Drupal 5.3.
I have OG.
Book expand filter set to Groups.
I created a group, it created a book automatically, but when I tried to add child page, I could create only a top level book, there was no parent to choose from.
Then I tried to edit the child, it gave the following warning, in the edit page as well as 'Create a book page' page, with no option to select parent.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '% ORDER BY b.weight, n.title' at line 1 query: SELECT n.nid, n.title, b.parent, b.weight FROM node n INNER JOIN book b ON n.vid = b.vid WHERE n.status = 1 AND n.nid <> % ORDER BY b.weight, n.title in /usr/www/users/avnet/drupal/includes/database.mysql.inc on line 172.
When I reset the filter to defaults this message disappears but then all other books gets listed which I don't want.
I want a group member creating book page to see only that group's handbook as parent.
I removed all the books, removed all the groups, started all over again, but with no success.
Now when I create a group it is not even creating a book, gives me the same warning message.
Any suggestion as to how to solve this problem?
Thanks,
Manoj
ps. i am new to Drupal, but is in the process of setting up drupal for our community Intranet where I need to restrict various groups to edit only their book.

#1
I'm sure I've followed this up already once. Maybe that bug that hit my computer also hit Drupal.org....
Anyway, try using the retroactive link available in the newest version to automatically create the top-level book pages for all of your previous groups. Don't click it more than once.
Dave
#2
I found the bug. It looks like on like 356 there is a % by itself and no %d. Simply adding the d should be enough to get this module working for you. I'm going to verify that this problem exists in the most recent version.
Note that this bug will only exist for user 1, all other users should be unaffected, which is why I didn't spot it before. On my test site, I was always creating content as a test user.
Dave
#3
This should be fixed in the newest version uploaded on 11-18-07.
Dave
#4
Automatically closed -- issue fixed for two weeks with no activity.