Closed (fixed)
Project:
Printer, email and PDF versions
Version:
4.7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Feb 2007 at 19:01 UTC
Updated:
3 Oct 2007 at 12:08 UTC
when printing print friendly pages and pagination of an article, it will only print the current page, not the whole article.
Comments
Comment #1
jcnventuraCan you tell me if the latest dev release for Drupal 5.x fixes this?
Thanks,
Joao Ventura
Comment #2
dicreat commentedI'm using Drupal 5.2 with Paging module and I have the same problem.
Comment #3
dicreat commentedAny suggestion?
Comment #4
jcnventuraI still don't have any answer to my question.. Is this happening with the latest 5.x-2.1 release of this module?
If it is, please try adding the following line and tell me if this fixes it (I don't use the paging module):
$node->body = str_replace("<!--pagebreak-->", "", $node->body);Comment #5
tinthing commentedHi, I just installed 5.x-2.1 on a v5.1 test system hoping that it would correct problems I've had previously with applying input filters to blog pages (it did!) - but I also noticed the problem reported here for paginated pages. I made the mod you suggest but it doesn't appear to make any difference - in fact I tried hacking the str_replace to change some plain text which I know appears in the body of the affected page but it didn't seem to change that either. Other aspect of the page content did change when edited, so I don't think I'm getting fooled by the cache.
HTH
Comment #6
dicreat commentedPrint module version "5.x-2.1".
New line don't fix the problem.
Comment #7
jcnventuraI have solved the problem in the latest dev release (should be 2.2 in a couple of days).
The solution is to add the following:
just below the node_load call (same point as my previous suggestion)
Comment #8
tinthing commentedYes, that does it, thanks.
Initially after adding those lines I got no content in the pages at all, just 'n/a'. Then I checked and found that I was using a 5.x-1.x-dev release of the paging module (not sure why). On changing to 5.x-1.0 the fix worked as described, so perhaps this issue will show up again as new paging module releases appear.