Django
Django comes with two methods for handling data or output across multiple templates: Template Tags and Context Processors. But why would you use one over the other? Let's take a look at their main strengths and some examples to help you make the choice. Custom Template Tags You
Django
When starting a new app, I recommend immediately creating a models folder and using that to hold files for each model. The advantage in doing this at the start is that your app is easier to maintain as it grows. It's a lot easier to find the model
Django
We can use the classic, {{ forloop.counter }} trick to output the number of the loop iteration (each time we go through the loop, it outputs that number), but it what if your designers want leading zeroes added to those numbers? Just to be clear these are numbers with leading zeroes:
Django
Often you'll end up with several test cases in just one app. Instead of putting all of your tests into one large tests.py file, we can separate them into multiple files within a tests folder. Whether your app continues to grow, requiring more tests, or you just
Django
The foreign key (or many-to-many) gives you a way to access/connect another model. related_name is how you can access the reverse relation: from that other model back to the one you've added the field to. If related_name is not set, the default is the model
Django
This error typically relates to trying to add a field to your search_fields, but the field is not actually text—perhaps it’s a ManyToManyField or a ForeignKey. Given the following, we want to be able to search our tags when we're in the Blog List View