Skip to main content

Create an agenda on top of djangocms-blog!

Project description

Add an Agenda to your blog that displays upcoming events!

Easy! CheapFree! Not seen on TV!


Install

  • Install the package

    python3 -m pip install djangocms-blog-agenda
    
  • Add it in your INSTALLED_APPS:

    "djangocms_blog_agenda",
    "recurrence",
    
  • Run the migration:

    python3 manage.py migrate djangocms_blog_agenda
    
  • Update the djangocms-blog urls by the ones in this module, by using this lovely setting:

    BLOG_URLCONF = "djangocms_blog_agenda.patched_urls"
    
  • Create a new blog configuration.

    • Instance namespace: put what you want.
    • Application title: put what you want.
    • Object name: put what you want.
    • [...]
    • Click on Layout (Show):
      • [...]
      • Template prefix: djangocms_blog_agenda.

      That's very important since this application will check this value multiple times (to update the queryset, to check the templates, to add the post extension "event date" only to the Agenda app...).

    • Save this config.
  • that's all folks!


Explanations/Views/Misc

  • A new Event date DateTime field has been added to blog posts that have the template prefix set to djangocms_blog_agenda.
  • A new post list view was created for the Agenda view, it includes all the posts where the event_date is set to a date in the future.
  • Another view is available at _("/past/"), that will display each post where the event_date is in the past.
  • The templates are not in djangocms_blog/templates anymore, but in djangocms_blog_agenda/templates. Something's not appearing on your templates? Try to edit the file in djangocms_blog_agenda/templates/!
  • We removed the mention of comments & liveblog in the admin form, because we're not using this.
  • We use some very special bits of code that are using some internal features of djangocms-blog (see misc.py, and apps.py). Try the module before pushing an update.

Config

Settings

DJANGOCMS_BLOG_AGENDA_HIDE_UPCOMING_EVENTS_AFTER_CHOICES

a tuple of choices describing when AgendaUpcomingEntriesPlugin will hide events.

Default choices are:

(
    ("start", _("just after event start date")),
    ("start+1h", _("1 hour after event start date")),
    ("start+4h", _("4 hours after event start date")),
    ("start+1d", _("1 day after event start date")),
    ("start+2d", _("2 days after event start date")),
    ("start+3d", _("3 days after event start date")),
    ("start+7d", _("7 days after event start date")),
    ("end", _("just after event end date")),
)

DJANGOCMS_BLOG_AGENDA_RECURRENCE_MAX_DAYS_SEARCH

a number of days (int) to limit the search of recurring events. Defaults to 365.

DJANGOCMS_BLOG_AGENDA_TEMPLATE_PREFIXES

You may need to add multiple agenda blogs with different template prefixes, in order to have different html content or styles for each agenda.

Add this list in your settings so that djangocms-blog-agenda will work (display start_date & end_date in add/update views of the articles):

DJANGOCMS_BLOG_AGENDA_TEMPLATE_PREFIXES = [
    "djangocms_blog_upcoming_calendar",
    "other_djangocms_blog_template_prefix",
    "...",
]

The default template prefix (djangocms_blog_agenda) will still be recognized even if you had this setting, you don't need to add it in the list.

Multisite

This modules handles multisite just fine; just add BLOG_MULTISITE = True in your settings, and our module will inject the get_site function directly inside the class returned by get_user_model()! (it is done in AppConfig ready() method)

You will then need to create a new "Global Page Permission" entry with your user/group, and to select the site where the user/group will have the right to post new articles/agenda posts.

If you're curious about this function, here it is.

Recurrences

Recurring events are handled with the help of django-recurrence package. Only the first event is saved into database, and following recurring events are added into querysets just before they are displayed. Only events that occurs n days after the first event are displayed. You can change this n with the setting DJANGOCMS_BLOG_AGENDA_RECURRENCE_MAX_DAYS_SEARCH.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

djangocms_blog_agenda-0.11.0.tar.gz (37.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

djangocms_blog_agenda-0.11.0-py3-none-any.whl (45.7 kB view details)

Uploaded Python 3

File details

Details for the file djangocms_blog_agenda-0.11.0.tar.gz.

File metadata

  • Download URL: djangocms_blog_agenda-0.11.0.tar.gz
  • Upload date:
  • Size: 37.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.0.1 CPython/3.11.10

File hashes

Hashes for djangocms_blog_agenda-0.11.0.tar.gz
Algorithm Hash digest
SHA256 0818fb1863959ba3093703d37b0d5f04a7b1565a614dff03edf6acadc3d1ef0a
MD5 06f5a2012c14b187f89b85fd871772d5
BLAKE2b-256 ed5577e5d2bfe653223950d547767d3e3fba85ba428dd55e8bbfc39f7d3ec03e

See more details on using hashes here.

File details

Details for the file djangocms_blog_agenda-0.11.0-py3-none-any.whl.

File metadata

File hashes

Hashes for djangocms_blog_agenda-0.11.0-py3-none-any.whl
Algorithm Hash digest
SHA256 012f41c629dc656836a532dc56aa20361fca8587e15dbe7df287c851c50f1004
MD5 a8d25cba46bab24daf01a9aeeb1ab0a5
BLAKE2b-256 c49aeba5976654f34dd626338e975b11ac3366bd2ea7bbb369882452e4d73e5b

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page