printer-friendly book pages only showing teaser

rickauer - January 18, 2008 - 10:30
Project:Drupal
Version:5.6
Component:book.module
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed
Description

Hello everybody,

on an upgraded 5.6 installation that uses the book module excessively, the print version only shows the teaser of each book page.

I tried to workaround this problem using the printer-friendly module but ran into another one (which is probably not of interest here). Am I overlooking something obvious? In 4.7 the printer-friendly pages worked perfectly for all book pages.

Here's an example of a book page of a customer of mine:

Online view: http://www.figu.org/ch/verein/periodika/bulletin/2007/nr-62/leserfragen
Print view: http://www.figu.org/ch/book/export/html/1820

Can somebody pls. help me here?
Thanks, Stephan

#1

rickauer - January 21, 2008 - 13:52

nobody? Do I need to provide more data? Is nobody using the book module? Is there a life after death?

Thanks,
Stephan

#2

ScoutBaker - February 9, 2008 - 09:22
Status:active» active (needs more info)

Does this only happen on old book pages that were created before you upgraded? I don't have a 4.x site to upgrade, but creating a new book page in D5.7, the printer-friendly page is showing both the teaser and the body of the book page. I tried different sizes to make sure it wasn't related to the length of the page (or teaser).

#3

rickauer - February 11, 2008 - 19:45

it happens for both, old and newly created content. As a test, when I set the teaser to be the full node (by putting the 'break' to the end of the node), the full node is displayed also with the printer-friendly view. I already double-checked the book module (if I really had a clean install). Must be some left-over from the upgrade, I presume.

#4

ScoutBaker - February 11, 2008 - 20:43

What does it show if you create a page with no break in the body?

#5

rickauer - February 12, 2008 - 10:10

then the automatic teaser kicks in after 400 characters or so, leaving the printer-friendly page in the same 'broken' state.

#6

ScoutBaker - February 13, 2008 - 04:36

Since this is happening to all of the book pages, old or new, it sounds like something corrupted in the D5 install. If it was the upgrade process itself, I'd only expect some sort of issue in the old entries.

With that in mind, you might try reuploading the 5.6 files to see if that resolves the problem. You could also try upgrading to 5.7 (make sure to backup everything first of course).

#7

rickauer - February 14, 2008 - 17:33

I know it feels like that, but I am pretty confident that's not the cause. I've started with Drupal 5.5 and upgraded to 5.6 in the meantime, both by using the terminal, no ftp. I would not know where a corruption of files should be caused. However, I'll have to do the 5.7 upgrade still, so that's another chance, but I am not too optimistic, frankly.

#8

ScoutBaker - February 14, 2008 - 19:23

If this is something inherent in the code, then I should be able to reproduce it without performing an upgrade from D4.x.

You could also be looking at something specific to the system you're running on. If that's the case, then if you install a completely fresh instance of D5.6/5.7 you should get the same results. This is more work than checking for possibly corrupt files by reuploading. I was trying to keep it simple, and one step-at-a-time.

The other standard troubleshooting that we hadn't touched is the contrib modules you are using. Have you disabled all of them and checked the behavior? When you upgraded, did you follow the directions in UPGRADE.txt, or do some variation? All of those can have an effect as well, it's just a lot to deal with at one time.

#9

rickauer - July 15, 2008 - 15:14
Status:active (needs more info)» fixed

For some reason, the printer-friendly pages for books do now show up properly, after upgrading to 5.8. This can only mean there has been a problem indeed, but it either hasn't been communicated or I wasn't able to find the issue in the bug tracker. I am glad this could be resolved, but it leaves a disturbing feeling when thinking about the next upgrade ...

#10

Anonymous (not verified) - July 31, 2008 - 04:46
Status:fixed» closed

Automatically closed -- issue fixed for two weeks with no activity.

 
 

Drupal is a registered trademark of Dries Buytaert.