Classified Ad Web Site - Milestone 3

In this assignment, you will expand your classified ads web site to add functionality equivalent to:

We will add a favoriting capability to your previous milestone by borrowing more parts and pieces from the code that runs:

Do All of the Challenges

At this point all of the challenges should be working - not all will be tested by the autograder - but we will separately check them.

(1) Make yourself a gravatar at - 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 any thing you like - it does not have to be a picture of you.

(2) Change your home/static/favicon.ico to a favicon of your own making. I made my favicon at - 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 up update the file and press 'Refresh' and.or switch browsers.

(3) Make social login work. Take a look at, copy it into adlist/adlist/ 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/ and make sure that the "Switch to social login" code is correct and at the end of your adlist/adlist/

# The code below dynamically switches between non-social login.html 
# and social_login.html when we notice that social login has been
# configured in (later in the course)
# Or just uncomment the path above when you enable social login

from django.contrib.auth import views as auth_views
    from . import github_settings
    social_login = 'registration/login_social.html'
        path('accounts/login/', auth_views.LoginView.as_view(template_name=social_login))
    print('Using',social_login,'as the login template')
    print('Using registration/login.html as the login template')

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 instead of 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.

Adding Favorites to the Ads Application

In this section, you will pull bits and pieces of the favs sample application into your ads application to add support for logged in users to "favorite" and "un-favorite" ads.

(1) Add this to your ads/, talking inspiration from dj4e-samples/favs/

class Ad(models.Model) :


    # Favorites
    favorites = models.ManyToManyField(settings.AUTH_USER_MODEL,
        through='Fav', related_name='favorite_ads')

class Fav(models.Model) :
    ad = models.ForeignKey(Ad, on_delete=models.CASCADE)
    user = models.ForeignKey(settings.AUTH_USER_MODEL, on_delete=models.CASCADE)

    class Meta:
        unique_together = ('ad', 'user')

    def __str__(self) :
        return '%s likes %s'%(self.user.username,[:10])

Of course do the migrations once you have modified the model.

(2) Add two routes to your for the favorite features

    views.AddFavoriteView.as_view(), name='ad_favorite'),
    views.DeleteFavoriteView.as_view(), name='ad_unfavorite'),

(3) Look at how ThingListView from dj4e-samples/favs/ retrieves the list of favorites for the current user and add code to your AdListView to retrieve the favorites for the current logged in user.

(4) Alter your ad_list.html by looking through favs/templates/favs/list.html. Make sure to add the parts that show the stars based on the list of favorites for this user and the favPost() JavaScript code at the end.

(5) Pull in and adapt AddFavoriteView, and DeleteFavoriteView from dj4e-samples/favs/ into your

Manual Testing

It is always a good idea to manually test your application before submitting it for grading. Here are a set of manual test steps:

The most common problem is that when you click onthe star if looks good on the screen but the fact that this is not a favorites (or not) did not get recorded in the server.
Often you will need to check the developer network console in your browser to find errors in the AJAX code.