From 43b10a4f129b3edfb9e8dea367378ea21f608ef5 Mon Sep 17 00:00:00 2001 From: Tobias Kunze Date: Thu, 4 Aug 2016 11:02:43 +0200 Subject: [PATCH] Add missing nav_event signal to docs (#158) --- doc/development/api/general.rst | 5 +++-- doc/development/implementation/urlconfig.rst | 2 +- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/development/api/general.rst b/doc/development/api/general.rst index 561f69004e..3eea3da595 100644 --- a/doc/development/api/general.rst +++ b/doc/development/api/general.rst @@ -25,7 +25,7 @@ Frontend -------- .. automodule:: pretix.presale.signals - :members: html_head, nav_event + :members: html_head, footer_links .. automodule:: pretix.presale.signals @@ -47,7 +47,8 @@ Backend ------- .. automodule:: pretix.control.signals - :members: html_head, footer_links + :members: nav_event, html_head + .. automodule:: pretix.base.signals :members: logentry_display diff --git a/doc/development/implementation/urlconfig.rst b/doc/development/implementation/urlconfig.rst index e44910fc7d..9f99db1a34 100644 --- a/doc/development/implementation/urlconfig.rst +++ b/doc/development/implementation/urlconfig.rst @@ -30,7 +30,7 @@ modules we do some magic to avoid duplicate configuration, but for a fairly simp only a handful of routes, we recommend just configuring the two URL sets separately. The file ``urls.py`` inside your plugin package will be loaded and scanned for URL configuration -automatically and should be provided by any plugin that provides any view. +automatically and should be provided by any plugin that provides any view. A very basic example that provides one view in the admin panel and one view in the frontend could look like this::