Siburg

On second thoughts, trying to maintain compatibility with wagtail versions before 3.0 looks too hard. The trouble is the changes to module paths (https://docs.wagtail.org/en/stable/releases/3.0.html#changes-to-module-paths) in Wagtail 3.0. I started amending...

@bashu here is initial, incomplete PR. Running tests locally with `pytest` is not working for me. Would welcome your views on how to proceed, or I would be happy for...

See #306 . I actually prefer the interpretation of a string to be in the timezone from my settings. P.S. If it is changed, please treat it as a breaking...

Apologies for "me too" comment, but I just encountered this bug today when trying to upgrade wagtail from version 2.15. My first Googling of the issue led to this: https://stackoverflow.com/questions/74748261/issues-upgrading-from-wagtail-2-15-6-to-2-16-breaks-all-pages-except-home-page,...

>I get: File "/tmp/pip-req-build-xo1d0ymg/chroniker/**init**.py", line 1, in from django import VERSION as DJANGO_VERSION ModuleNotFoundError: No module named 'django' > Strange. I just tried installing my branch into the dev environment...

> Would you mind merging with master and resolving the conflicts so the test suite can run? Done. Haven't looked at it in almost a year, but hopefully I have...

> For those who are curious, the issue was that Django renamed django-admin.py to django-admin, and for some odd reason the build wasn't returning any helpful error message like "django-admin.py...

You beat me to it. I like the test with `-0`. As per the first comment on the ticket, you may want to tweak `docs/ref/contrib/humanize.txt` as well.