Closed rolandgeider closed 4 years ago
speshak
commented
4 years ago I made some progress on getting django 2.0 support about a year ago: https://github.com/speshak/wger/tree/django-2 There are probably some rough edges, but I think my install has been running that branch since then. (I'll confirm that when I get a chance)
rolandgeider
commented
4 years ago Awesome, I'll take a look
speshak
commented
4 years ago It looks like I'm still running a Django 1.x build. (Specifically my master branch). At the very least there are a handful of commits that take care of a lot of the compatibility legwork. I vaguely remember having loads of issues getting django-mobile ripped out (IIRC it isn't supported any longer) and by the time I got that working things were good enough to get my install running. Let me know if you want any of the work I did chopped up and PR'd in.
rolandgeider
commented
4 years ago Yes, that would be great! I also wanted to remove djsngo-mobile and do everything via CSS (there's probably already an issue for that), so leave that in the PR
speshak
commented
4 years ago I opened #459 to address getting my changes merged so we don't further pollute the discussion here.
rolandgeider
commented
4 years ago Closed with commit above, application can bootstrap an sqlite DB again
There is a behaviour change with SQlite 3.26 that produces an error when the django migrations change a foreign key (there are
_oldtable references) and is not possible to bootstrap the application. Other DBs such as Postgres work, though.https://code.djangoproject.com/ticket/29182
Roadmap: Since the solution involves update to django 2.0 where this is fixed, with all the template and form rendering re-work needed, I'll do that, make sure the application works is installable, release 1.9 and call it a day. Any other features or open PRs will be pushed back.