-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with Wagtail 2.11.x (definitely 2.11.3) #214
Comments
I've got a local fix i can offer up (that bit was easy), but making the test suite pass is proving a significant task - it's quite out of date, so moving it to include running tests on wagtail 2.11 is taking a bit of time Anyone have an opinion on what versions of Wagtail and Django should be supported? At the moment am trying to get LTS versions of both + previous release (Wagtail 2.10) passing |
I've been pointed at #212 which should also take care of this |
Looks like #212 was merged so this could probably be resolved? |
This is an old issue but I just submitted a PR to get it working up to Wagtail 2.16 #239 I'd appreciate a review of the code please. My plan is to build on that to get Wagtail 3.0 working. |
Am just moving a Wagtail project to 2.11.x from 2.10.x and hit this after upgrading:
It looks like that helper function has moved and
wagtail-personalisation
hasn't caught up yet (am on0.14.0
)See wagtail/wagtail@aa9c9d9#diff-08f48b8cf5b22209da61adb3fec00945b9849da17b25c1f78ad92c2c25165513 where
get_valid_next_url_from_request
was moved from the module/__init__
level to a.utils
moduleAlso see wagtail/wagtail-localize@a1b8454 as an example of where a similar import issue was fixed.
The text was updated successfully, but these errors were encountered: