wagtail-personalisation
wagtail-personalisation copied to clipboard
Rule-based personalisation for Wagtail CMS
The forms.py still uses some "old" code from Django 2.x, which has been deprecated in 3.0. I got the following errors and have added my solution to them, which made...
If a page has multiple segment variants and a user matches more than one of those segments, how does the module choose which variant to show to the user? This...
Any ideas about what's going on here? ``` (wagtail-personalisation) ~/c/p/wagtail-personalisation (master | 🔍 8962) > make sandbox pip install -r sandbox/requirements.txt Obtaining file:///Users/technical/code/pb/wagtail-personalisation (from -r sandbox/requirements.txt (line 4)) Collecting Django=2.1...
I've been wondering what's the best practice for displaying variant pages that are children of an index page and are displayed on that index page. Currently the best solution in...
Is anyone successfully using wagtail-personalisation in a project that also includes wagtailtrans? I've come across two issues using the two together... 1) My variant pages never show. Stepping through the...
`TimeRule` and `DayRule` use naive datetimes so don't work as expected for me here in Australia.
In our segment admin view at `/admin/wagtail_personalisation/segment/edit/1/` the page chooser in the Visit Count Rule does not pop up the modal because `wagtailadmin/js/page-chooser.js` and `wagtailadmin/js/page-chooser-modal.js` are missing from the media....
wagtail-personalisation claims to require wagtail
It's confusing when we have a count for variants and personalised pages. I am not quite sure if you need anything except variants, otherwise it juts seems to bring confusion.