Contributions

PDF Customer Invoice v1.0

This contribution will add a link to a customer's order history detail page (account_history_info.php). When clicked, this link
will generate a PDF copy invoice for the order.
This contribution is based on PDF Invoice (http://www.oscommerce.com/community/contributions,3027)
Apart from recoding PDF Invoice to work client side, I have added the following features, configurable from within admin:

1. Font can be chosen - arial, times, courier, helvetica.
2. Colours for the invoice elements can be chosen. Hex values supplied are automatically converted to RGB as needed by FPDF so you can easily
match up your stylesheet.css colours to the invoice colours for a consistent look.
3. An optional watermark (text of your choice e.g. "Copy Invoice") can be added to the invoice.
4. An optional VAT tax reference can be added to the invoice.
5. Choice of displaying generated PDF inline or by forcing a download - set within admin configuration.
6. PDF Metadata (Store owner, Invoice number etc) is automatically added to the PDF.
7. Choice of store logos - png, gif, jpg.
8. Custom footer splash (marketing text) can be added.
9. Store logo size can be easily 'tweaked'.

The invoice will also display product attributes, if applicable (something which is missing from PDF Invoice)

Expand All / Collapse All

Bugfix PDF Customer Invoice and SuperTracker 3.4

1 Mar 2010

Cross posted to Supertracker contrib.

Short bug fix for Supertracker 3.4.1 if you are also using PDF Customer Invoice 1.1 (12 March 2008).

Using both of these contributions breaks PDF Customer Invoice. You will see an error message like below when a customer attempts to view their PDF invoice:

FPDF error: Some data has already been output, can't send PDF file

Simple fix. Took me some time to narrow it down, so hoping to save others the aggravation. :)

The problem is that Supertracker inserts data into the HTML stream before the PDF completes, which basically interrupts the PDF, causing it to abort. If you use any sort of FPDF application, I suspect you may run into this problem. The solution is to skip use of Supertracker when user is viewing a PHP account related form.

-----------

open /includes/application_top.php

from:

// Supertracker
require(DIR_WS_CLASSES . 'supertracker.php');
$tracker = new supertracker;
$tracker->update();
}

TO:

// Supertracker
if (strpos(basename($PHP_SELF),'account') !== false) {
require(DIR_WS_CLASSES . 'supertracker.php');
$tracker = new supertracker;
$tracker->update();
}