search

mozillahispano / mozbuzz

Tracking tool for media mentions
http://www.mozilla-hispano.org
15 stars 25 forks source link

Home URL redirects to mozilla-hispano.org #38

Closed bernimel closed 10 years ago

bernimel commented 11 years ago

Hi,

When accesing https://www.mozilla-hispano.org/mozbuzz/ it redirects automatically to http://www.mozilla-hispano.org.

Best, Berni

nukeador commented 11 years ago

I'm redirected to login and then to error 500.

@sveggiani was changing stuff yesterday.

nukeador commented 11 years ago

I see this on mail log:

ImproperlyConfigured: SITE_URL incorrect. Settting is `https://www.mozilla-hispano.org/mozbuzz`, but request was `https://mozilla-hispano.org`

<WSGIRequest
path:/mozbuzz/browserid/login/,
nukeador commented 11 years ago

@bernimel can you check it again please?

bernimel commented 11 years ago

Checked and still happening @nukeador

nukeador commented 11 years ago

I can't reproduce the problem. Can you check cleaning your cache and cookies and using another computer or browser?

bernimel commented 11 years ago

I just log in (not Persona) and then the home of MozBuzz drives me to mozilla-hispano.org. It happens on all my desktop browsers (Firefox, Safari, Chrome), on iPhone and on iPad.

If I log in with Persona it works.

The thing is that some of our users don't have a PersonaID.

nukeador commented 11 years ago

Let's just use persona for now till we found what's going on. If they are mozillians they should have a PersonaID, they are going to need it sooner or later.

And it's just 1 step to confirm the email and it's done.

sebasmagri commented 11 years ago

Would we just drop non-Persona authentication on the site?

bernimel commented 11 years ago

Would that mean that we cannot choose who's in? Would be that mean public access?

sebasmagri commented 11 years ago

No. The current BrowserID setup for MozBuzz doesn't allow the automatic creation of new users. The users will still be created by an admin before they can login to the site.

bernimel commented 11 years ago

Then it sounds good for me :) It's a good way to promote PersonaID. @nukeador what do you think?

sebasmagri commented 11 years ago

To give more context to the discussion, recent changes in Django 1.5.x [0] include a new way of handling custom user models. Thus, the current mechanism used by Mozbuzz, AUTH_PROFILE_MODULE, is now deprecated in Django 1.5, and I'm almost sure this is why we're failing to authenticate with non-Persona login.

While we could migrate to the new Django's authentication model, it will represent schema and data migrations as stated by the Django docs.

Changing AUTH_USER_MODEL has a big effect on your database structure. It changes the tables
that are available, and it will affect the construction of foreign keys and many-to-many relationships.
If you intend to set AUTH_USER_MODEL, you should set it before running manage.py syncdb for
the first time.

If you have an existing project and you want to migrate to using a custom User model, you may
need to look into using a migration tool like South to ease the transition

OTOH, I agree with @bernimel that this is a good way to promote Persona, and, for example, webmaker apps and MDN use only Persona nowadays.

[0] https://docs.djangoproject.com/en/dev/topics/auth/customizing/#substituting-a-custom-user-model

nukeador commented 11 years ago

I think only Persona login should be OK.

bbotella commented 10 years ago

So, is this ticket still open? Are we going to just allow Persona login? If so, does this redirection matter?

bernimel commented 10 years ago

I guess it's open because the redirection issue it's not fixed. I think that just allowing Persona is fine. If we do this, we should quit the user identification boxes for user&pass from the MozBuzz homepage.

sebasmagri commented 10 years ago

Today we confirmed the new configuration options in BrowserID fix this so I'm closing this. This is fixed now in development.