In this assignment, you will expand your classified ads web site to add functionality equivalent to:
The primary additions from the previous milestone are to add an image to each ad and add comments for each ad.
You will build this application by borrowing parts and pieces from the code that runs
and combining them into a single application.
In this section, you will pull bits and pieces of the
pics sample application
ads application to add support for an optional single picture per ad.
(1) Add this to your
ads/model.py, talking inspiration from
class Ad(models.Model) : ... # Picture picture = models.BinaryField(null=True, editable=True) content_type = models.CharField(max_length=256, null=True, help_text='The MIMEType of the file') ...
Do not include the entire
Pic model. Of course do the migrations once you have modified the model.
(2) Copy in the
pics/forms.py as well as
(3) Take a look at
pics/views.py and adapt the patterns in
PicUpdateView and replace the code for
These new views don't inherit from owner.py becuase they manage the
owner column in the
(4) Alter your
templates/ads/ad_form.html by looking through
pics/templates/pics/form.html. Make sure to add the
enctype="multipart/form-data" and the
attribute to the
(5) Alter the
templates/ads/ad_detail.html template by looking through
to add code to include the image in the output if there is an image associated with the ad.
Make sure not to lose the
price field in your UI. If you don't see the
in your UI it is likely a mistake in your
(6) Add a
ad_picture route to your
urls.py based on the
pics_picture route from
path('ad_picture/<int:pk>', views.stream_file, name='ad_picture'),
(5) Add the
stream_file() view from
pics/views.py and adapt appropriately
Test to make sure you can upload, view, and update pictures with your ads.
In this section, you will pull bits and pieces of the
forum sample application
ads application to add support for comments for each ad.
(1) Update your
models.py adding the comment feature from the
class Ad(models.Model) : ... owner = models.ForeignKey(settings.AUTH_USER_MODEL, on_delete=models.CASCADE) comments = models.ManyToManyField(settings.AUTH_USER_MODEL, through='Comment', related_name='comments_owned') ... class Comment(models.Model) : text = models.TextField( validators=[MinLengthValidator(3, "Comment must be greater than 3 characters")] ) ad = models.ForeignKey(Ad, on_delete=models.CASCADE) owner = models.ForeignKey(settings.AUTH_USER_MODEL, on_delete=models.CASCADE) created_at = models.DateTimeField(auto_now_add=True) updated_at = models.DateTimeField(auto_now=True) # Shows up in the admin list def __str__(self): if len(self.text) < 15 : return self.text return self.text[:11] + ' ...'
Do not add the Forum model - simply connect the
Comment model to the
Ad model. Of course do
the migrations once you have modified the model successfully.
(2) Pull the
CommentForm class from
forums/forms.py into your
(3) Adapt the
get() method from
ForumDetailView to your
AdDetailView to retrieve the list of comments
and create the
CommentForm and pass them into your
templates/ads/ad_detail.html template through the context.
(4) Adapt the
templates/ads/ad_detail.html template to show comments and show a delete icon
when a comment belongs to the current logged in user.
(5) Also add the ability to add a comment to an ad in
ad_detail.html when the user is logged in by looking
at the techniques in
(6) Add a route in
urls.py for the
forums/urls.py. Make sure to use the same URL patterns as shown here:
urlpatterns = [ ... path('ad/<int:pk>/comment', views.CommentCreateView.as_view(), name='ad_comment_create'), path('comment/<int:pk>/delete', views.CommentDeleteView.as_view(success_url=reverse_lazy('ads')), name='ad_comment_delete'), ]
(7) Adapt the comment related views from
forums/views.py and put them into your
(8) You will have to adapt the
forums/templates/forums/comment_delete.html template to work in your ads application.
You will have to finish these by the next assignment - so you might as well work on them now. And they are fun.
(1) Make yourself a gravatar at https://en.gravatar.com/ - it is super easy and you will see your
avatar when you log in in your application and elsewhere with gravatar enabled apps. The gravatar can be
anything you like - it does not have to be a picture of you. The gravatar is associated an email address
so make sure to give an email address to the user you create with
(2) Change your
home/static/favicon.ico to a favicon of your own making. I made my favicon
at https://favicon.io/favicon-generator/ - it might not change instantly after you update the favicon
because they are cached extensively. Probably the best way to test is to go right to the favicon url
after you update the file and press 'Refresh' and/or switch browsers. Sometimes the browswer caching
is "too effective" on a favicon so to force a real reload to check if the new favicon is really being served
you can add a GET parameter tho the URL to forc it to be re-retrieved:
x value to something else if you want to test over and over.
(3) Make social login work. Take a look at
github_settings-dist.py, copy it into
mysite/mysite/github_settings.py and go through the process on github to get your client ID and
secret. The documentation is in comments of the file. Also take a look at
dj4e-samples/urls.py and make sure that the "Switch to social login" code is correct
and at the end of your
You can register two applications with github - one on localhost and one on PythonAnywhere. If you are
using github login on localhost - make sure that you register
http://localhost:8000/ and use that in your browser to test your site. If you
use localhost, you probably will get the
The redirect_uri MUST match the registered callback URL for this application. error message when you use social login.