Render Wagtail pages and models as PDF document using Weasyprint or LaTeX.
The goal of this extension is to provide a flexible but easy to use way to render Wagtail pages and Django models as PDF. With this extension you can utilize all the benefits from the wagtail page system (previews, drafts, history) as well as the power of StreamField and RichText for your generated PDF document. Models may be easily rendered as PDF and will be accessible either through the admin interface or through a public URL.
Currently weasyprint (for HTML to PDF conversion) and latex is supported. If you are undecided which one to use, weasyprint is recommended.
Install the latest version from pypi:
pip install -U wagtail-pdf-view
# and either this for HTML -> PDF
pip install -U django-weasyprint
# and/or this for Latex -> PDF
pip install -U django-texand add the following to your installed apps:
INSTALLED_APPS = [
...
'wagtail_pdf_view',
'wagtail.contrib.routable_page',
...
]While weasyprint is installed as dependency of django-weasyprint and works out of the box, a working latex interpreter (lualatex) must be installed on your system if you want to use django-tex.
If django-weasyprint and django-tex is installed, weasyprint is selected by default.
For django-tex you should set DEFAULT_PDF_VIEW_PROVIDER = WagtailTexView in your settings.
All you need to do to render your Wagtail page as PDF, is to inherit from PdfModelMixin.
If you want to render a model instead, read the section ModelAdmin below.
If you want to use latex, read the latex section below.
Further configuration options include:
ROUTE_CONFIGto enable rendering of the default HTML view and the PDF view at the same timestylesheetsresp.get_stylesheetsto include CSS stylesheets for weasyprintattachmentto control the file attachment (i.e. whether to download the PDF or open it in the browser)
A very simple example page using Wagtails StreamField.
Like for a regular Wagtail page, the template should be located under: <app_dir>/templates/<app>/simple_pdf_page.html
If you're using django-tex the template extention .tex is expected.
from wagtail.core.models import Page
from wagtail.core.fields import RichTextField, StreamField
from wagtail.core import blocks
from wagtail.admin.edit_handlers import FieldPanel, StreamFieldPanel
from wagtail_pdf_view.mixins import PdfViewPageMixin
# Inherit from PdfViewPageMixin
class SimplePdfPage(PdfViewPageMixin, Page):
# you can create fields as you're used to, e.g. StreamField
content = StreamField([
("heading", blocks.CharBlock(form_classname="full title")),
("text", blocks.RichTextBlock()),
], blank=True)
# content panel for the CMS (same as always)
content_panels = Page.content_panels + [
StreamFieldPanel("content"),
]
# OPTIONAL: If you want to include a stylesheet
#stylesheets = ["css/your_stylesheet.css"]Default configuration:
class PdfOnlyPage(PdfViewPageMixin, Page):
# PDF only
ROUTE_CONFIG = [
("pdf", r'^$'),
("html", None),
]
By default only the pdf-view is available, i.e. you may only view this page as pdf. This is useful when you just want to display a generated pdf document easily.
A HTML first page: You can access the wagtail page as you're used e.g. 127.0.0.1/mypage. The PDF version will be available under pdf/ e.g. 127.0.0.1/mypage/pdf
class HtmlAndPdfPage(PdfViewPageMixin, Page):
# HTML first
ROUTE_CONFIG = [
("html", r'^$'),
("pdf", r'^pdf/$'),
]
Note that the order of html and pdf is not arbitrary: The entry you set first, will be displayed by default when using wagtails preview function. Depending on your case, you may want to put pdf in the first place, so your editors get the pdf-view by default, while html-page url stays the same for the users. In both cases your editors may access both views through the drop-down menu integrated in the preview button.
A PDF first page: The PDF version is displayed with the regular url and you can access the wagtail page under /html, e.g. 127.0.0.1/mypage/html
class HtmlAndPdfPage(PdfViewPageMixin, Page):
# PDF first
ROUTE_CONFIG = [
("pdf", r'^$'),
("html", r'^html/$'),
]
ROUTE_CONFIG is build on wagtails routable_page, you can specify routes as you want (e.g. ("html", r'^web/$'))
As of version 0.2 reversing url patterns is supported.
This feature is useful in cases when you are serving multiple views (i.e. html and pdf).
You can access the URLs for the different views by using routablepageurl from the routable_page module:
{% load wagtailroutablepage_tags %}
<!-- HTML Page URL-->
{% routablepageurl page "html" %}
<!-- PDF Page URL-->
{% routablepageurl page "pdf" %}
<!-- When looping over Page.get_children, you need to use the specific Page object -->
{% for subpage in page.get_children %}
<li>{% routablepageurl subpage.specific "pdf" %}</li>
{% endfor %}In most cases you don't need the full functionality of routablepageurl. To make things easy you can simply access the different views by the custom URL attributes url_pdf and url_html:
<!-- HTML view url -->
{{page.url_html}}
<!-- PDF view url -->
{{page.url_pdf}}
<!-- When looping over Page.get_children, you need to use the specific Page object -->
{% for subpage in page.get_children %}
<li>{{subpage.specific.url_pdf}}</li>
{% endfor %}If you are just interested in the extention to the normal page url:
# this will be 'pdf/' in HTML-first mode
page.reverse_subpage('pdf')Version 0.2 introduces rendering for models via ModelAdmin.
The model needs to inherit from PdfModelMixin to enable rendering on the models side.
To make incorporating PDF-views as simple as possible this module offers two ModelAdmin mixins
ModelAdminPdfViewMixin and ModelAdminPdfAdminViewMixin.
If you are not using ModelAdmin you may add a view for the model manually.
If you want to access PDFs from outside of the admin area, you need to hook in wagtail_pdf_urls into your projects urls.py.
If you are unsure whether you need this, it is recommended use the hook below:
# urls.py
from wagtail_pdf_view import urls as wagtail_pdf_urls
urlpatterns = urlpatterns + [
# hook in the 'live'-view PDFs under "pdf/"
path("pdf/", include(wagtail_pdf_urls)),
...
# IMPORTANT: This must be below the "pdf/" include
path("", include(wagtail_urls)),
...
]Your model needs to inherit from PdfModelMixin:
# models.py
from wagtail_pdf_view.mixins import PdfViewPageMixin, PdfModelMixin
class YourPdfModel(PdfModelMixin, models.Model):
# the admin view uses a different template attribute to
# prevent you from publishing sensitive content by accident
# template for non-admin view
template_name = "path/to/your_model.html"
# template for admin
admin_template_name = "path/to/your_model_admin.html"Unlike for PDF-Pages where everything is done in the Page-model, the hooks for ModelAdmin need to be extended:
By inheriting from ModelAdminPdfViewMixin or ModelAdminPdfAdminViewMixin you
automatically make the model accessible through a live url or through the admin panel respectively.
This separation should make it easy to choose a view to according to your security needs:
ModelAdminPdfViewMixinis suited for non-sensitive public models.ModelAdminPdfAdminViewMixinmakes the view only accessible to users withviewpermissions on the model.
# wagtail_hooks.py
from wagtail.contrib.modeladmin.options import ModelAdmin, modeladmin_register
from .models import YourPdfModel
# OPTION 1)
# Creating a public view model (accessible for everybody through a url)
# MAKE SURE YOU HOOKED IN THE URLs PROPERLY
from wagtail_pdf_view.modeladmin.mixins import ModelAdminPdfViewMixin
@modeladmin_register
class YourPdfModelWagtailAdmin(ModelAdminPdfViewMixin, ModelAdmin):
model = YourPdfModel
# OPTION 2)
# Creating admin-restricted view model
from wagtail_pdf_view.modeladmin.mixins import ModelAdminPdfAdminViewMixin
@modeladmin_register
class YourPdfModelWagtailAdmin(ModelAdminPdfAdminViewMixin, ModelAdmin):
model = YourPdfModel
This is an example how you can hook in the models PDF-view manually (without using ModelAdmin).
# urls.py
# This will be either WagtailWeasyView or WagtailTexView depending on your installation
from wagtail_pdf_view.mixins import DEFAULT_PDF_VIEW_PROVIDER
from .models import YourPdfModel
urlpatterns = [
...
# URL path for the DetailView with primary key pk
re_path(r'^some/path/(?P<pk>\d+)/$', DEFAULT_PDF_VIEW_PROVIDER.as_view(model=YourPdfModel)),
...
]This library implements an easier extendable ButtonHelper.
If you are using a custom ButtonHelper, you should inherit from ExtendableButtonHelperMixin or PdfViewButtonHelper,
otherwise you will not see a button for the PDF-view of the object in ModelAdmins ListView.
Example:
class MyCustomButtonHelper(PdfViewButtonHelper):
# simplified button registration
# (action, properties)
custom_object_buttons = [
("custom", {"label": 'Custom Label'}),
("some_action", {"label": 'Another Action'}),
]Note that custom_object_buttons is defaulted with the actions pdf and live in PdfViewButtonHelper.
If you are setting a custom PermissionHelper, you need to inherit from CustomActionPermissionHelperMixin.
When you want to use latex instead of HTML, you should be aware of the following:
You need to add django_tex to INSTALLED_APPS:
INSTALLED_APPS = [
...
'django_tex',
...
]You need to add the jinja tex engine to TEMPLATES in your settings.py:
TEMPLATES += [
{
'NAME': 'tex',
'BACKEND': 'django_tex.engine.TeXEngine',
'APP_DIRS': True,
'OPTIONS': {
'environment': 'wagtail_pdf_view.environment.latex_environment',
},
},
]Set DEFAULT_PDF_VIEW_PROVIDER in your settings:
from wagtail_pdf_view.views import WagtailTexView
DEFAULT_PDF_VIEW_PROVIDER = WagtailTexViewIn case you just want to use latex for a specific model settings you can overrite PDF_VIEW_PROVIDER:
from wagtail_pdf_view.views import WagtailTexView
class SimplePdfPage(PdfViewPageMixin, Page):
# render with LaTeX instead
PDF_VIEW_PROVIDER = WagtailTexViewIn general you should include wagtail_preamble.tex, which provides required packages and commands for proper richtext handling.
{% include 'wagtail_preamble.tex' %}
You can set custom width for the richtext image insertion
{% raw %}
\renewcommand{\fullwidth} {0.8\textwidth}
\renewcommand{\partialwidth} {0.5\textwidth}
{% endraw %}
A very useful block is raw, this prevents the jinja rendering engine from interpreting everything inside. This is nice if you want to create a latex command
{% raw %}
{% endraw %}
For further information read the django-tex github page