CGM_Public/pretix_cgo
1
0
Fork 0
forked from CGM_Public/pretix_original
Code Pull Requests Actions Activity

Add missing nav_event signal to docs (#158)

Browse Source
This commit is contained in:
Tobias Kunze
2016-08-04 11:02:43 +02:00
committed by Raphael Michel
parent 8dcb8193fa
commit 43b10a4f12
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/development/api/general.rst
View File

@@ -25,7 +25,7 @@ Frontend
-------- --------
.. automodule:: pretix.presale.signals .. automodule:: pretix.presale.signals
:members: html_head, nav_event :members: html_head, footer_links
.. automodule:: pretix.presale.signals .. automodule:: pretix.presale.signals
@@ -47,7 +47,8 @@ Backend
------- -------
.. automodule:: pretix.control.signals .. automodule:: pretix.control.signals
:members: html_head, footer_links :members: nav_event, html_head
.. automodule:: pretix.base.signals .. automodule:: pretix.base.signals
:members: logentry_display :members: logentry_display

2
doc/development/implementation/urlconfig.rst
View File

@@ -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. 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 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 A very basic example that provides one view in the admin panel and one view in the frontend
could look like this:: could look like this::