@login_required def wishlist(request): context = {} items = wishlist.objects.filter(user__icontains=request.user.id) context["items"] = items if request.method == "POST": rid = request.POST["rid"] is_exist = wishlist.objects.filter(prod__icontains=rid, user__icontains=request.user.id, status=False) if len(is_exist) > 0: context["message"] = "Item already exists" else: prod = get_object_or_404(RentAd, id=rid) user = get_object_or_404(User, id=request.user.id) w = wishlist(user=user, prod=prod) w.save() context["message"] = "{} added in your cart", format(prod.r_name) pass return render(request, 'wishlist.html', context)

@login_required def wishlist(request): context = {} items = wishlist.objects.filter(user__icontains=request.user.id) context["items"] = items if request.method == "POST": rid = request.POST["rid"] is_exist = wishlist.objects.filter(prod__icontains=rid, user__icontains=request.user.id, status=False) if len(is_exist) > 0: context["message"] = "Item already exists" else: prod = get_object_or_404(RentAd, id=rid) user = get_object_or_404(User, id=request.user.id) w = wishlist(user=user, prod=prod) w.save() context["message"] = "{} added in your cart", format(prod.r_name) pass return render(request, 'wishlist.html', context)

I just changes icontains to id

I just changes icontains to id

Why did you use icontains instead of id. id and pk are very powerful way to validate things

Hey, I wanna know how to implement a view that checks if the user is authenticated (if True, then raise 403 HTTP error otherwise, render the template) Any Idea?? I have already done this: if user.is_authenticated: raise PermissionError() else: return render(..) It actually works properly but I see a TraceBack error in my console..! Is it ok to raise an exception inside an IF statement??

There's a really elegant way to do this using function decorators ​def​ ​authenticated_user​(​view_func​): ​    ​@​wraps​(​view_func​) ​    ​def​ ​wrapper_func​(​request​, ​*​args​, ​**​kwargs​): ​        ​if​ ​request​.​user​.​is_authenticated​: ​            ​return​ ​view_func​(​request​, ​*​args​, ​**​kwargs​) else: raise PermissionDenied ​    ​return​ ​wrapper_func Then you will be able to use it in this way: @authenticated_user def some_view(request): return render(...) Oh, and BTW, there's already built-in Django decorator for unauthenticated users. from​ ​django​.​contrib​.​auth​.​decorators​ ​import​ ​login_required @​login_required​(​login_url​=​"login"​) def view_func(request): return render(...) Where login_url is URL name of path to login page.

Thanks. You mean it's elegant just because of raising inside an if statement right??

I mean that you don't actually have to manually check if user's authenticated in every view function, you can re-use the decorator in other view functions as well.

I mean that you don't actually have to manually check if user's authenticated in every view function, you can re-use the decorator in other view functions as well.

Well, average generic views enjoyer... from django.core.exceptions import PermissionDenied if not request.user.is_authenticated: raise PermissionDenied return render(...)

Well, average generic views enjoyer... from django.core.exceptions import PermissionDenied if not request.user.is_authenticated: raise PermissionDenied return render(...)

Actually rocking in with this style.. but having that kind of issue.. But the thing is, EVERYTHING IS WORKING FINE.

Idk, I'm weird but I always use functional style for Django views and generic views for Django Rest Framework

However, functional ones provide you more control and they are easier to read and understand

Anyway, my personal preferences

My last personal Django project at first was using Django templates but as project was getting bigger, I've realized that I want more dynamic behavior and I've added VueJS to my project dependencies. I import Vue in a base HTML template, so what's actually happening is my webpage is firstly rendered by Django and then some data renders with VueJS. 😐 I'm really thinking of completely separating frontend and backend of my project and just do DRF stuff with Django and serve frontend with Vue CLI but rewriting everything is a complete hell. Bruh. This idea is good but awful at the same time. I othen literally wake up in the middle of a night because of terrible dreams where I refactor my Django code 😨

Not sure even give it a go. I would implement a DRF service running through a container and a vuejs service running on another container and then, close all DJango container service ports. It will only interact with the Vuejs container and the Vuejs container is exposed to the world.

Not sure even give it a go. I would implement a DRF service running through a container and a vuejs service running on another container and then, close all DJango container service ports. It will only interact with the Vuejs container and the Vuejs container is exposed to the world.

Yup, that's what I actually want to do. BUT some legacy code in my project still uses Django Templates 😥 Sorry, I'm crying... Programming destoys my life

I mean, I had a good social life and I was happy before I started coding

How should I get start with Django because I am newbie

Should i learn based view method ?

you mean class-based views?

Yes

It gives you tens of features. why not?

I think it's more difecult

Only if you don't have much knowledge about python classes and OOP in general

I'm good in oop

Then go through the source code for the various class based views. That's what I do before I use any of them.

Try again?

Like what?

I think it's more difecult

I have soved all oop problems in hacker rank

Maybe not familiar with Django class-based views. Like their structures.

Yeah i think that

Official docs would help. At least helped me. :)

I don't like docs

How should I get start with Django because I am newbie

I'll try it