By kae on
I'm trying a make a handbook that reviews the 300-400 Drupal modules on www.drupalecommerce.com using 4.7. When I go to submit a book page, every existing book page is on the pulldown menu. If you try it on drupal.org (not 4.7 yet) you'll see that the pulldown list seems to have hundreds of lines. I read nodes 11283 and 12927 which has been discussing fixing this from 2004 to present. Am I correct in thinking that this problem still is not fixed in 4.7? (That would make it seem like a very difficult problem to fix, rather than an oversight)
Comments
can't use book.module
I'm thinking that I'll have to convert all the book pages to just pages to get rid of the ridiculously long checkbox.
You don't have to use the
You don't have to use the pull down box to select a parent page if you FIRST navigate to the parent page and use the "add child page" from the links below. Then the parent is pre-selected from the pull down list and you don't have to worry about it.
Advanced Web Design
user
thank you. I agree. but the problem is this is too confusing for the user. I'm sure many of them will inadvertently submit something on the wrong page and it'll be terrible to fix.
on my browser (Konqueror on Linux), when I hit the down arrow to scroll down the screen, it scrolls me down the pulldown menu instead.
there is...
There is an unofficial "bookplus.module" out there with some useful features (user-selectable weights, cascading dropdowns, etc.) that'll probably make its way into the 4.7 codebase as soon as it's out of beta.
Um, you mean as a contrib
Um, you mean as a contrib module and update dto work with 4.7? Once 4.7 is feature frozen (and it sort of is now) then features won't be added except through contrib modules.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
thx
I'll look for it. is the a to z module on your site a drupal module? i'd like one like that.
There is a patch...
A patch has been submitted that addresses this issue for 4.7. Hopefully it gets incorporated in whole or in part. Here are the posts about patches (http://drupal.org/node/27736) and (http://drupal.org/node/62264).