This project has been archived by its maintainers, and is no longer receiving any updates.
Wagtail Events 
Events calendar management for wagtail, with tools for filtering by date.
This project is a hard fork of omni-wagtail-events, and we owe a debt of gratitude to those folks for getting us started. So why did I hard-fork (duplicate and start again) rather than fork from omni-digital?
- Well, github keeps the releases of the repo you fork from. I want to put this on pypi so it's easily available, and have control of the release versioning (which isn't close to ready for v1.x where it started with omni-digital), so it needs to be here.
- I'm basically about to break everything for django 2.x and wagtail 2.x, so I'd need a major version bump anyway, and figured that the chances of getting my changes merged into the upstream were nil.
- The rich text fields make
omni-wagtail-eventsa nightmare to use in headless API mode, and mean that most of the events data is unstructured. Here, we move to Wagtail'sStreamField... but that creates a migration headache unless we start fresh. - The migrations in the original project won't work with an in-memory database, so testing is slow.
- I've majorly simplified the model structure to singleton events. I think this is all that's reqiured in 99.9% of cases.
I'm extremely open to collaboration - in fact, I really don't want to be maintaining this (it's only for one client) so I'm open to transferring ownership or collaboration to anyone who wants to take this on and enhance it. @omni-digital, this originated as your baby so if you'd like to take back maintenance, please reach out and I'll help you.
Requirements
Wagtail events requires Django 2.1 or later and Wagtail 2.3 or later.
Supported Versions
Python: 3.6
Django: 2.1
Wagtail: 2.3
Getting started
Installing from pip:
pip install wagtail_events
Adding to INSTALLED_APPS:
INSTALLED_APPS = [
...
'wagtail_events',
...
]
Running the migrations:
python manage migrate wagtail_events
Models
EventIndex
An index/listing page for EventSeries instances, with optional pagination.
Event
A detail page for an event, with start_date and optional end_date, implementing a manager which allows filtering on those dates.
Metadata
Release files for wagtail-events 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wagtail_events-0.4.0.tar.gz | 12.2 kB | Without provenance | Details for wagtail_events-0.4.0.tar.gz |
Release files / wagtail_events-0.4.0.tar.gz
| Download URL | wagtail_events-0.4.0.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e18ff67677e70a27d90ac508d0ce5236e6a8f0c027c01c77c1374fb1bc66d710
|
|
BLAKE2b-256 checksum How to use checksums |
aecf166cc8f0d3f584d3cb91af16b131b56035fc49fb1b68e54d04e76c54d5c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.3
|
Security for wagtail-events 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.