greyhare

I've been using [crispy forms](https://github.com/django-crispy-forms/django-crispy-forms). Is `django-formset` compatible with that? And we're performing validation at the backend, too, right?

As for decoupling Django-Shop from Django-CMS, I think we'll need documentation explaining what Django-shop does itself, because the current "run the cookiecutter (which is frequently unstable)* and read the source"...

Django 2.2 has been out for about three months now. It's already up to 2.2.2. Django CMS... is taking its time, apparently. As for reparsing the settings file, it's not...

I wasn't suggesting using cookicutter-django itself, merely the cookiecutter tech it's built on. It would be a significant change, though.

Django 3.2 is out as well (It's already up to 3.2.5) and djangoCMS 3.9 supports it.

I'm getting the feeling this installer is abandoned. There has been no activity in all of 2021.

So I've spent two days hunting down a bug related to this one. The behavior was: 1. Go to sign in page. 2. Enter username and password. 3. Redirected to...

Looking through `django-otp`, there's a `OTPAuthenticationFormMixin` in `forms` that could put everything on the login page and possibly fix this, but I'm at a loss as to where to mix...

I think the minimum set of steps to reproduce would be something like: 1. Set up a minimal Django project with django-allauth-2fa and its dependents. Leave the `socialaccount` stuff out...

The `/static/` stuff might not be the trigger. Safari, at least, looks for `/apple-touch-icon.png`, though there are equivalent Android and other files that can trigger it the same way. Here's...