Sorry guys, I think I found a bug with the otherwise fantastic paging module:
When a multi-page article is put into a book outline, no book links appear: no child pages, no previous, next, up , etc links. I've marked this as critical because (AFAIK) book.module is now part of core?
Similarly, when I tried using multi-pages on an og_group_homepage, all the indices of group nodes disappeared completely ... and no, unfortunately they didn't just append to the last page :(
Is it something to do with simultaneous calls to theme_pager function by different modules? Sorry I can't help more.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | French_0.zip | 1.15 KB | Jérôme |
Comments
Comment #1
merlinofchaos commentedOh man. The problem here is the order that nodeapi is being called. The paging module actually overwrites the body (because it's reducing what is displayed) and the book module (and I assume og module as well) are appending to the end of the body. Drupal, in 4.6, only calls these modules in alphabetic order, too, so there isn't a good way to fix this in 4.6.
It's a little easier to fix in 4.7 by changing the module's weight.
I'll have to see if I can come up with something.
Comment #2
merlinofchaos commentedWell there's only one fix.
Rename paging module to aapaging and search and replace paging_ to aapaging_
Silly but it'll work. Be sure to disable the module before doing that. Oh and get the newest one, it's got an important fix.
Comment #3
Jérôme commentedAn official release of this NAV-BUG fix ?
Attached is a POT proposal and a French Translation,
Enjoy.
Comment #4
Gurpartap Singh commentedCommited a fix code. Fixes problems with book module(specifically) absolutely.
Comment #5
(not verified) commented