* State the requirement for Node.js up-front (since it's required by everyone, not just front-end devs)
* Point to vagrant-wagtail-develop instead of making people set up a Vagrant instance manually
* No need to fiddle with python paths via local.py - 'setup.py develop' handles that
* Skip instructions for virtualenvs (anyone who decides against the Vagrant route is expected to know how to use them)
The following tags and filters are supported:
* `wagtailcore`:
* `pageurl()`
* `slugurl()`
* `wagtail_version()`
* `|pageurl`
* `wagtailimages`:
* `image()`
Django template tags have been translated to Jinja functions, rather
than custom tags. Functions are easier to use compared to template tags,
and can be composed and combined for greater flexibility.
The template tag libraries have been grouped as Jinja Extensions, which
are loadable via the `extensions` option. An example Django Jinja2
configuration is:
```python
TEMPLATES = [
# ...
{
'BACKEND': 'django.template.backends.jinja2.Jinja2',
'APP_DIRS': True,
'OPTIONS': {
'extensions': [
'wagtail.wagtailcore.templatetags.jinja2.core',
'wagtail.wagtailimages.templatetags.jinja2.images',
],
},
},
]
```
Old code that does not properly extend `Page.get_context()` for context
generation will not get the new `PAGE_TEMPLATE_VAR` in their contexts,
which did not play nicely with the `wagtailuserbar`. Now, the template
context is checked for both `PAGE_TEMPLATE_VAR` and `self`, in that
order, for a Page.
From a comment by @gasman on #1684:
> It appears the try/catch in ImageEmbedHandler was added here: 74b9f43
>
> Since the rest of the commit doesn't deal with images at all, and the
> commit makes it clear that the corresponding change to
> MediaEmbedHandler was intended to preserve the existing 'fail
> silently' behaviour in the light of the new exceptions added for media
> embeds - I think this try/catch is redundant. `Format.image_to_html`
> does its own catching of image IO errors, which seems to be
> sufficiently robust (if it wasn't, we'd be seeing errors on front-end
> page rendering), so I think this try/catch can reasonably be deleted.
https://github.com/torchbox/wagtail/pull/1684#issuecomment-140695060
