CiviCRM Community Forums (archive)

hey folks,

when i use the batch update via profile and try to print the screen that results, the printout (or preview) only shows one page of records.

i replicated this on the drupal.demo.civicrm.org site. i view the participants of the Fall Fundraiser event. i then select all and choose the Batch Update via profile option and choose the participant status profile.

if i try to print this page, or click the printer icon and try to print that page, i get one page's worth of records and then the bottom of the screen and it ends.

not sure where to troubleshoot this. any thoughts?

--josue

thanks for the reply lobo!

i did some more testing and discovered that google chrome printed the whole page. that inspired me to play with firebug (which i do not know a whole lot about!) and i think i found something:

there is a table that gets created right after the <legend>Batch Update for Events - Event Tracking Profile</legend>

this table has, according to firebug, an element.style that says "position: relative;"

if i change, with firebug, "relative" to "absolute" then i can successfully print the whole list of results!

now if someone can tell me where that style gets created, then maybe this is a bug that can be fixed.

--josue

Josue - The relative class on the enclosing table is being inserted by packages/jquery/plugins/jquery.tableHeader.js for the sticky headers feature (table column headers stick to top of browser window). You can turn it off by removing the class="sticky" from this line in Batch.tpl

<thead class="sticky">

However, that will "break" the sticky headers feature :-( which you probably want in the normal (non-print friendly) view. The print friendly view has a "snippet=2" param which causes the surrounding blocks to not be included. Also, print.css is included in print friendly mode. So ... you might want to look at passing a param to the Batch.tpl template to tell it we're in print friendly mode so you can conditionally not apply the sticky class. Seems like this would be pretty easy to do in templates/common/snippet.tpl. I turned on smartyDebug and there is a $printerFriendly smarty var now but it just has the path and doesn't change whether you're in printer friendly mode or not - so you'd need to add something like $isPrinterFriendly. You could also see if it makes sense to add jquery to action.tpl (which is called by snippet.tpl) to suppress the sticky header behavior if we're in print friendly view. That would be a nice general fix.

OR perhaps suppress you can figure out a way to suppthe sticky class js behavior in print.css (not sure if that idea is viable).

In either case, we would be open to a patch to fix this problem. :-)