Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Invoice Payment - Long name issue | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Invoice Payment – Long name issue

Invoice Payment – Long name issue

Posted: October 1, 2012 at 4:06 pm

Viewing 1 reply thread


Andrew Clarke

October 1, 2012 at 4:06 pm

G’day,

The name of our organisation is so long that reaches over to the right hand side of the generated PDF invoice and overwrites the “Primary Attendee ID:” part of the line on the right hand side.

Is there a way to change the generated invoice so that either:
1. The name is output on a separate line below that of the Date and Primary Attendee ID: lines.
2. The name can be made to go over two lines.

Your help with this would be most appreciated.

Best regards, Lloyd Borrett (for Andrew Clarke)


Dean

  • Support Staff

October 2, 2012 at 4:29 am

Hi Andrew,

This took me a while to find.

At line 121 in event-espresso/gateways/invoice/template.php is this

//Set the top left of invoice below header
$pdf->SetFont('Times', 'BI', 14);
if (isset($invoice_payment_settings['payable_to'])) {
    $pdf->MultiCell(0, 10, pdftext($invoice_payment_settings['payable_to']), 0, 'L'); //Set payable to
} else {
    $pdf->MultiCell(0, 10, pdftext(''), 0, 'L'); //Set payable to
}

Where it says Multicell(0,10, if you change the 0 to another number (on both lines) it will limit the width of that title and force it onto a secondary line.

Maybe start with 100 or so and see how it looks.

Viewing 1 reply thread

The support post ‘Invoice Payment – Long name issue’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server