One of the first things this site is missing is requiring users to be logged

in to get to the Create a Message view.

I talked about how to do this a bit in the Django class based views course

if you've seen that one.

If you haven't, you should probably check it out as this course is going to use

only Class Based Views.

Django provides a mixed in for its generic view to mark a view as requiring the user

to be logged in before the can access it.

Seems like a simple fix, so it's time to get to it.

If you remember the mix ins part of the Class Base Views course,

this part here should be mostly a refresher.

So Django provides decorators for marking a view as requiring a login, but

decorators are iffy with class-based views.

So Django also provides mix-ins to use with your class-based views.

Before I can use that mixin though, I have to import it.

So here in posts and then views.py,

up here at the top I'm going to add in my mixin.

So mixins comes before models, so from django.contrib.auth.mixinins,

import LoginRequiredMixin.

And then I need to use that.

And so I need to add it to my views.

To start I have two views that definitely need to be locked down.

So first is this one right here that lets users create new messages,

create new posts.

And there's one a little further down that lets people delete messages.

So I'm gonna go ahead and add LoginRequiredMixin

to this view, which that'll force people to be logged in.

And then on the DeletePost I'm also gonna add in

LoginRequiredMixin as the first item and I'm gonna go ahead and save.

So those two are good, those are important.

There's a select related mix in here which is from Django braces and

that lets me do select related queries without having to

actually change the query set myself to do select related.

I can just do it as an attribute in the view.

I'm actually putting LoginRequiredMixin before SelectRelated, so

that the SelectRelated isn't even considered thought about at all

unless the login is valid.

So just saving a little tiny bit of time there.

Okay, so that should prevent me from being able to

get to any of those views if I'm logged out.

So right now I'm not even running the server.

So if I was to go in here and try to make a new post,

which I know that URL is posts/new, then I should get yep, I get a 404.

I get redirected to somewhere else.

And then if I try to go to say posts/delete/1,

then that should also get me a 404, yep another 404, which I can't do that.

And I get, it's trying to redirect me to this login page which it doesn't have, so

I'll handle that a little later.

Okay, so I can't do either of those things.

I should be able to run my tests and get a good expected result.

So let me try that, Python managed.py test and we have a u.

All right, so see how now we have we have a u there and

we have this unexpected successes.

So if I go look at my tests which are right here and I scroll down through here.

Where did that go?

Right here.

I have a test that I have marked as expected failure.

I'm expecting this test to fail.

But now though, I get, the test doesn't fail, right?

When I try to go to post create while I'm not logged in, I do not get a 200.

So this is correct.

So I can take this line out.

And I do believe that's the only place I'm using unit test.

Yep, just one result, so I can take that out and that's a little shorter now.

And then, let's check this read me.

Okay, so sign up, log in, log out, no.

Only able to post messages when logged in, done.

All right, and then I have some other stuff that needs to be locked down too.

So I may run the server again.

And now I'm gonna go to this other app which is communities.

I'm gonna go to the views.py in here.

And I need to import the mixin again,

django.contrib.auth.mixins import LoginRequiredMixin.

And I need to add this to the views in here.

So obviously I don't want people to be able to create communities

unless they are logged in.

Viewing a single community, viewing all the communities, those I think are fine.

Joining a community, should require a login and

leaving a community should as well.

Because you can't exactly leave or join a community unless I know who you are.

So all right, that's pretty good, I think that's all of those.

Now should be able to get to any of those views without being logged in.

So for example, if I was to come back over here to this Minecraft community.

Let's click on Minecraft, there we go.

And I clicked Join and now I should get the log in required thing.

Yeah, great.

Well, that wasn't too difficult.

But now that some of these views require a user to log in I have to deal with

the fact that I haven't yet made a way for them to actually log in.

Seems like a good feature to add next.