Assessment: DIY Django mini blog

需要顯示的頁面與對應的 URLs 和需求提列於下表：

另外你應該要寫一些基本的測試來驗證:

• 所有的模型欄位都有正確的標示和長度。
• 所有的模型都有期望的物件名稱(例如 __str__() 回傳期望的值)。
• 模型有期望的 URL 給每篇文章與回覆。(例如get_absolute_url() 回傳期望的 URL)。
• BlogListView (所有文章的頁面) 可以從期望的位址進入(例如/blog/blogs)。
• BlogListView (所有文章的頁面) 可以從期望的位址名稱進入(例如'blogs')。
• BlogListView (所有文章的頁面) 使用期望的模板(例如預設值)。
• BlogListView 以每頁 5 筆項目分頁(至少第一頁是如此)。

下一區塊顯示符合以上需求的網頁截圖。

The following screenshot provide an example of what the finished program should output.

這個頁面會列出所有部落格內的文章(可以從側邊選單的「所有文章」連結進入)。 幾項提醒：

• 側邊選單也要列出目前登入的使用者。
• 每篇文章與部落客都能透過連結的方式進入。
• 必須要有分頁(每頁 5 筆資料)。
• 文章排列順序由最新至最舊。

可以由側邊選單的「所有部落客」進入此頁面，並於頁面上提供連結至每一位部落客。 從截圖可以發現到，並沒有任何一位使用者登入。

顯示某篇特定部落格文章的詳細內容。

請注意每個評論都有日期與時間，並且由最後至最新排列(與部落格文章相反)。 我們可以看見最底下有個連結連到新增評論的表單。當使用者沒有登入時，我們改以要求登入的連結代替。

這張表單用來新增評論，且使用者必須是登入狀態。當表單送出成功之後，我們必須回到相對應的部落格文章內容頁。

這頁顯示部落客的介紹資料以及列出他們所發表的部落格文章。

以下說明實作的步驟。

1. 建立一個此網站的專案及 app 骨架(可以參考Django 教學 2 : 建立一個網站骨架)。你也許會用『diyblog』作為專案名稱，『blog』作為 app 的名稱。

2. 建立部落格文章、評論與其他任何所需物件的模型。當你在思考怎麼設計的時候，請記得：

   • 每一個評論都只屬於一篇部落格文章，但每一個部落格文章可以有很多筆評論。
   • 部落格文章必須要依照發布時間排序(新至舊)，評論要依照發布排序(舊至新)。
   • 不是每位使用者都是部落客，但是每一位使用者都可以留下評論。
   • 部落客必須有介紹資訊。

3. 跑 migrations 以及創建一個新的超級使用者(superuser)。

4. 透過 admin 網站新稱一些部落格文章和評論。

5. 幫部落格文章列表頁與部落客列表頁建立視圖、模板及設定 URL。

6. 幫部落格文章詳細頁與部落客詳細頁建立視圖、模板及設定 URL。

7. 建立一個頁面包含可以新增評論的表單(記得只有已登入的使用者可以進入此頁!)

This project is very similar to the LocalLibrary tutorial. You will be able to set up the skeleton, user login/logout behaviour, support for static files, views, URLs, forms, base templates and admin site configuration using almost all the same approaches.

Some general hints:

1. The index page can be implemented as a basic function view and template (just like for the locallibrary).

2. The list view for blog posts and bloggers, and the detail view for blog posts can be created using the generic list and detail views.

3. The list of blog posts for a particular author can be created by using a generic list Blog list view and filtering for blog object that match the specified author.

   • You will have to implement get_queryset(self) to do the filtering (much like in our library class LoanedBooksAllListView) and get the author information from the URL.
   • You will also need to pass the name of the author to the page in the context. To do this in a class-based view you need to implement get_context_data() (discussed below).

4. The add comment form can be created using a function-based view (and associated model and form) or using a generic CreateView. If you use a CreateView (recommended) then:

   • You will also need to pass the name of the blog post to the comment page in the context (implement get_context_data() as discussed below).

   • The form should only display the comment "description" for user entry (date and associated blog post should not be editable). Since they won't be in the form itself, your code will need to set the comment's author in the form_valid() function so it can be saved into the model (as described here — Django docs). In that same function we set the associated blog. A possible implementation is shown below (pk is a blog id passed in from the URL/URL configuration).

     python

         def form_valid(self, form):
             """
             Add author and associated blog to form data before setting it as valid (so it is saved to model)
             """
             #Add logged-in user as author of comment
             form.instance.author = self.request.user
             #Associate comment with blog based on passed id
             form.instance.blog=get_object_or_404(Blog, pk = self.kwargs['pk'])
             # Call super-class form validation behaviour
             return super(BlogCommentCreate, self).form_valid(form)
     

   • You will need to provide a success URL to redirect to after the form validates; this should be the original blog. To do this you will need to override get_success_url() and "reverse" the URL for the original blog. You can get the required blog ID using the self.kwargs attribute, as shown in the form_valid() method above.

We briefly talked about passing a context to the template in a class-based view in the Django Tutorial Part 6: Generic list and detail views topic. To do this you need to override get_context_data() (first getting the existing context, updating it with whatever additional variables you want to pass to the template, and then returning the updated context). For example, the code fragment below shows how you can add a blogger object to the context based on their BlogAuthor id.

class SomeView(generic.ListView):
    ...

    def get_context_data(self, **kwargs):
        # Call the base implementation first to get a context
        context = super(SomeView, self).get_context_data(**kwargs)
        # Get the blogger object from the "pk" URL parameter and add it to the context
        context['blogger'] = get_object_or_404(BlogAuthor, pk = self.kwargs['pk'])
        return context

The assessment for this task is available on Github here. This assessment is primarily based on how well your application meets the requirements we listed above, though there are some parts of the assessment that check your code uses appropriate models, and that you have written at least some test code. When you're done, you can check out our the finished example which reflects a "full marks" project.

Once you've completed this module you've also finished all the MDN content for learning basic Django server-side website programming! We hope you enjoyed this module and feel you have a good grasp of the basics!

page(Doc) not found /zh-TW/docs/Learn/Server-side/Django/web_application_security