idlesign / django-sitegate Goto Github PK

Hi,
it seems that after latest changes in models.py (1 month ago) Django started complaining about a missing migration when running python ./manage.py migrate on a vanilla project (after installing django-sitegate using pip and after adding django-sitegate to the installed apps):

out:   Your models have changes that are not yet reflected in a migration, and so won't be applied.
out:   Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

it's a minor issue, I can run manage.py makemigrations on every virtualenv as suggested and "patch" the installed PyPi package, but maybe you would add the migration in django-sitegate itself.

thanks
Stefano

self.fields.insert(1, 'email', forms.EmailField(label=_('Email')))

Using django 1.7
self.fields is OrderedDict instance without insert method

Hi!

When running manage.py migrate on Django 1.8 and django-sitegate 0.10.2, it tells me

Your models have changes that are not yet reflected in a migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

When running makemigrations, the output is:

Migrations for 'sitegate':
  0002_auto_20150929_1728.py:
    - Alter field code on emailconfirmation
    - Alter field code on invitationcode

But in general sitegate seems to work. Could you please add these migrations to a repository?

With the email / password signup flow, the email address is inserted as the username. The max length for email address is 75 characters while the max for username is 30. What happens if an email address longer than 30 characters is used?

I tried this on my local machine with SQLite and it silently inserted the a > 30 character username but on other backends I think this will raise an exception.

This approach is used throughout the documentation.

from django.shortcuts import render
from sitegate.decorators import sitegate_view

@sitegate_view  
def entrance(request):
    return render(request, 'entrance.html', {'title': 'Sign in & Sign up'})

But the request variables don't flow to the templatetag context. Fail!

This works:

@signup_view(flow=ModernSignup)
def register(request):
    return render(RequestContext(request), 'enter.html', {'title': 'Sign up'})

summary:

request -> RequestContext(request)

On consecutive hits @redirect_signedin issues AttributeError: 'function' object has no attribute 'get'.

Is there a recommended way to create a new signup/signin flows?

My use case is doing case-insensitive matches on the username followed by the email address, where the username can be different from the email address.

Hi. Thanks for the work.
Kindly tell me how to change the Default redirect URL from /.
I have scoured the docs but can't find a setting key or API.

Thanks in Advance.

Maybe app should use https://pypi.python.org/pypi/django-crispy-forms/1.4.0 ?