wagtail-personalisation
wagtail-personalisation copied to clipboard
Rule-based personalisation for Wagtail CMS
I was using Django default configuration for session and database, i.e. SQLite and storing sessions in database. `visitor_count` session entry would cause the default Django development server to crash due...
This updates the package to support Wagtail v4.2 Drops support for wagtail < 4.1 The following PR's have been included here. - https://github.com/wagtail/wagtail-personalisation/pull/244
# This work adds support and testing for Wagtail 5.2 It includes the following PR's that are not yet merged. #250 #247 #246 #244
[Wagtail 5.1 release notes](https://docs.wagtail.org/en/stable/releases/5.1.html) **Includes PR for upgrades** Changes: - [wagtail.contrib.modeladmin is deprecated ](https://docs.wagtail.org/en/stable/releases/5.1.html#wagtail-contrib-modeladmin-is-deprecated)
This updates the package to support Wagtail v5.0 The following PR's have been included here. - https://github.com/wagtail/wagtail-personalisation/pull/244 - https://github.com/wagtail/wagtail-personalisation/pull/246
This upgrades the package to use up to Wagtail 4.1 and Django 4.1 It drops support for Wagtail < 2.15 and Django < 3.2
https://github.com/wagtail-nest
and, potentially, you should be unable to move a variant page to a tree position not shared by it's canonical page. I'm not 100% sure but I don't think this...
This could be specific to current usage, but I noticed that even if a page variant is unpublished, it still gets served to users that match that variant
Bumps [elliptic](https://github.com/indutny/elliptic) from 6.5.0 to 6.5.7. Commits 3e46a48 6.5.7 accb61e lib: DER signature decoding correction 03e06e1 6.5.6 7ac5360 Merge commit from fork 7570078 6.5.5 206da2e lib: lint 0a78e03 [Fix] restore...