mPDF Manual – Installation & Setup

Installation v6.x

First-time users

Installation:

  • Download the .zip file and unzip it
  • Create a folder e.g. /mpdf on your server
  • Upload all of the files to the server, maintaining the folders as they are
  • Ensure that you have write permissions set for the following folders:
    • /ttfontdata/
    • /tmp/
    • /graph_cache/

To test the installation, point your browser to the example files folder e.g. [path_to_mpdf_folder]/mpdf/examples/

If you wish to install additional fonts please see the notes in Fonts & Languages for further instructions.

If you wish to define a different folder for temporary files rather than /tmp/ see the note on ‘Folder for temporary files’.

If you have problems, please read the section on troubleshooting in the manual.

Upgrading from version mPDF 5.x

mPDF 6 has changed significantly from earlier version and it is recommended that a fresh install is used. You may wish to copy your previous config_* files and use them to update the new config files.

config_fonts.php - values of “indic” and “unAglyphs” from previous versions are now redundant.

config_lang2fonts.php - this is similar to the previous config_cp.php file; note however that $unifont (NOT $unifonts) must be only one font (not a comma-separated list as before).

Included fonts - the Indic fonts e.g. ind_bn_001.ttf are no longer required (nor do they work properly with mPDF 6).

useLang - this configurable variable, which used to be true by default, is now redundant. You may need to set: $mpdf->autoLangToFont = true; for the same results.

SetAutoFont() - is now redundant. You may need to set: $mpdf->autoScriptToLang = true; for the same results.

Indexes - have been largely redefined. See the section above.

Lists - have been rewritten. See the section above.

Headers and Footers - have been rewritten. See the section above.

A number of old depracated aliases will no longer be supported. Warning errors have been added to prompt you to change to the updated form:

  • $mpdf->useOddEven - should now use - $mpdf->mirrorMargins
  • $mpdf->useSubstitutionsMB - should now use - $mpdf->useSubstitutions
  • $mpdf->AliasNbPg - should now use - $mpdf->aliasNbPg
  • $mpdf->AliasNbPgGp - should now use - $mpdf->aliasNbPgGp
  • $mpdf->BiDirectional - should now use - $mpdf->biDirectional
  • $mpdf->Anchor2Bookmark - should now use - $mpdf->anchor2Bookmark
  • $mpdf->KeepColumns - should now use - $mpdf->keepColumns
  • $mpdf->UnvalidatedText - should now use - $mpdf->watermarkText
  • $mpdf->TopicIsUnvalidated - should now use - $mpdf->showWatermarkText
  • $mpdf->Reference - should now use - $mpdf->IndexEntry

The following functions have been removed:

  • setUnvalidatedText - should now use - SetWatermarkText()
  • AddPages - should now use - AddPage() or HTML code methods
  • startPageNums
  • CreateReference and CreateIndex - cf. Index section above

Default style sheet

A new mpdf.css file includes defaults for LISTS top/bottom margins, and also examples for Indexes and ToCs. This now acts like a normal CSS file, including cascading selectors i.e. not just main tags. This is always read (if present), so acts as a secondary default CSS, but one which allows selectors. Styles added to this act like a user stylesheet when considering precedence e.g. cellSpacing and border-spacing.

Direct writing methods and OTL

WriteText() WriteCell() Watermark() AutoSizeText() and ShadedBox() DO support complex scripts and right-to-left text (RTL).

Write() does NOT support complex scripts or RTL (NB this is a change - Write() used to support RTL).

CircularText() does NOT support complex scripts or RTL.

MultiCell() DOES support complex scripts and RTL, but complex-script line-breaking MAY NOT be accurate.

MultiCell() does not support kerning and justification. NB This includes <textarea> in forms which uses MultiCell() internally.

<select> form objects also do NOT support kerning.

Page numbering

Page numbering i.e. by including {PAGENO} or {‌nbpg} in a header/footer, can use any of the number types as used for list-style e.g.

<pagebreak pagenumstyle=”arabic-indic”>

Short codes are recognised for the 5 most common:

  • "1" - decimal
  • "A" = upper-latin or upper-alpha
  • "a" = lower-latin or lower-alpha
  • "I" = upper-roman
  • "i" = lower-roman

or any of the following: arabic-indic, hebrew, bengali, devanagari, gujarati, gurmukhi, kannada, malayalam, oriya, persian, tamil, telugu, thai, urdu, cambodian, khmer, lao, cjk-decimal

Note: A suitable font must be used in the header/footer in order to display the numbers in the selected script.

You can now set the pagenumberstyle from the beginning of the document by changing the configurable variable:

$this->defaultPageNumStyle = “arabic-indic”; // in config.php

$mpdf->defaultPageNumStyle = “arabic-indic”; // at runtime

Other Minor changes in mPDF 6

‘hebrew’, ‘khmer’, ‘cambodian’, ‘lao’, and ‘cjk-decimal’ are recognised as values for “list-style-type” in numbered lists.

CSS “text-outline” is now supported on TD/TH tags

Text wrapping in tables has been improved when using CJK scripts (chinese-japanese-korean).

Text underline and strikethrough can be used together: Hallo world. Either <u><s>…</s></u> or <span style=”text-decoration:underline line-through;”>…</span> can be used

Added support for style=”opacity:0.6;” in SVG - equivalent to: style=”fill-opacity:0.6; stroke-opacity: 0.6;”

Added support for opacity=”0.6” (as attribute) in SVG - previously only supported fill-opacity=”0.6” stroke-opacity=”0.6”

CSS position:absolute or fixed - rotate extended now to include rotate: 180; (previously just 90 or -90)

The default value of $this->keep_table_proportions = true; in config.php has been changed (see effect on Example 6 - nested table in top right cell).

Limited support has been added for SVG fonts embedded in SVG images (but not using @font-face rules) - see the separate Images demo file.

When using columns, the top margin is now collapsed at top of every column (not just first column of page).

The way mPDF handles optional end tags has been updated to be consistent with the HTML5 specification - previously not well defined for HTML4.

Changes to the way lists are handled means that text-align:justify may be inherited by lists from surrounding block elements (which did not happen previously). See LISTS above for more information.