Everybody knows about permalink, but it's usually used only in get_absolute_url. I prefer to use it for all related model urls.
class Event(models.Model):
# ...
@models.permalink
def edit_url(self):
return ('event_edit', (self.pk, ))And then in template:
Редактировать событиеSubscribe for the news and updates
Once we received an interesting task from a client. They needed to allow their users to upload a 3D model of the building and show it in a timelapse video from the construction site.
File upload works differently from simple form inputs, which can be somewhat troublesome for beginners. Here I'll show you how to handle uploads with ease.
Quite often we have to write paginated or filtered blocks of information on page. I created a decorator that would automate this process.
In order to check if user is authentcated in test, you can run:
It appears that not everyone knows that in python you can create classes dynamically without metaclasses. I'll show an example of how to do it.So we've learned how to use custom QuerySet to chain requests:Article.objects.old().public()Now we need to make it work for related objects:user.articles.old().public()This is done using use_for_related_fields, but it needs a little trick.
Usually users' profiles are stored in single model. When there are multiple user types, separation is made by some field like user_type.Situation is a little more complicated when different data is needed for each user type.In this article I'll describe how I solve this task.