Skip to main content
On the product detail view, you can offer buyers the option of downloading the product data as a PDF file. The file is generated from a separate template that is designed independently of the product page. This lets you create, for example, a data sheet with its own layout and optional personal notes. The buyer receives the result as a download, not as a page view in the browser.

​
Extending the shop configuration

Three sections of the shop.config are involved. Create any missing sections and parameters.

​
Assigning the template

The ProductPDF parameter in the <Templates> section names the template from which the PDF file is generated.

​
Defining the file name

The <PDFGenerator> section determines the name under which the file reaches the buyer.
The same section also contains the file names of the shop’s other PDF functions, for example for the basket and the order confirmation. ProductPDFFilename is the entry for the product detail view. Reference: PDFGenerator section

​
Storing the error message

If the generation fails, the shop shows the notify page with this text. Store it in the <NotifyMessages-Txt> section.
Reference: NotifyMessages-Txt section

​
Adding the button to the product detail view

The button belongs in the product form, because the generation is triggered by submitting it.

​
Determining the cause of an error

If an error occurs, the buyer lands on the notify page with the text stored above. The technical cause is in MSG-InternalErrorMessage. Add this block to the notify template if it is still missing.
Only include this tag within an HTML comment. Internal error messages must not appear to the buyer in plain text. You can still read the message via the browser’s source code view if an error occurs.
Reference: MSG-InternalErrorMessage Possible causes also include a timeout during generation. For the buyer, this looks exactly like a content error, but it can be distinguished in the source code.

​
Related topics