I have some blocks in my footer that I want to supress when going to the printer friendly page. I use "print/*" in the "Show on every page except the listed pages" section. Any suggestions?

Comments

jcnventura’s picture

Status: Active » Postponed (maintainer needs more info)

Hello,

Since the module is designed to replicate the original page's contents, I don't think that you will manage it trough configuration. My recommendation is that you edit the print.tpl.php line with class="print-footer" and replace it with your fixed footer code.

João

eMPee584’s picture

hi,
just hit the same issue trying to hide the drupal footer block.. the proposal to just hardcode the footer in the template is not an ideal solution..
imho the print module should not try to circumvent the block mechanism by removing /print from the path that is set when theme_blocks is called but this is really debatable.. i see the problem here, someone might have set a block only to appear on /node/42 and another block not to appear on /print/* which brings about quite a paradox situation.
at my site (http://hfopi.org) f.e. I got 2 blocks in the footer and want to have the copyright block displayed but not the drupal one. Fo0Oobaaar?!
everything else works real nicely though :)

jcnventura’s picture

Hello,

It's not trying to circumvent anything. It's just calling some Drupal services to recreate as best as possible a clean version of the original page. I think I have an idea why the theme blocks may be getting info that the current path is the original node, but I would like to ask you to try it, as this is something that is simple to change yet requires a lot to test.

Can you please move the following line:

$print["footer_message"] = filter_xss_admin(variable_get('site_footer', FALSE)) ."\n". theme('blocks', 'footer') ;

a couple of lines up to the line before

menu_set_active_item($path);

Thanks,

João

eMPee584’s picture

yeah that solves the problem nicely :)

jcnventura’s picture

Status: Postponed (maintainer needs more info) » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

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

mr.j’s picture

Category: support » bug
Status: Closed (fixed) » Active

Re-opened this because I just downloaded 5.x-3.3 and the bug persists. I assume it may still exist in 6.x too.
The fix in comment #3 works - could it please be ported to the 5.x branch?

Thanks

jcnventura’s picture

Status: Active » Fixed

I have committed that change to the 5.x dev branch. It will be generated in a few hours.

João

Anonymous’s picture

Status: Fixed » Closed (fixed)

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