Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 540513
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T10:14:53+00:00 2026-05-13T10:14:53+00:00

I have been intending to use django-notification in my django app. The docs are

  • 0

I have been intending to use django-notification in my django app.

The docs are a little sparse for someone with my limited level of experience. I need a couple of clarifications about its usage.

  • In the project’s usage.txt, under the
    section “Creating Notice Types” it
    says:

You need to call create_notice_type(label, display, description) once to
create the notice types for your application in the database.

After debating this with myself quite a lot, I feel like I don’t really “need” to do that. The objective is to create records for notice types in the database, so I can very well do that using django-notification’s options in the admin section. Am I right?

I think create_notice_type is useful when one is distributing apps so that they are pluggable.

  • In the project’s usage.txt, under the
    section “Notification templates” it
    says:

There are four different templates that can to be written for the actual content of the notices: ………. Each of these should be put in a directory on the template path called notification/<notice_type_label>/<template_name>. If any of these are missing, a default would be used.

What are these default templates? Where do they need to reside? Is putting the four templates mentioned in the docs in a “notification” directory in the template loader path sufficient?

  • As can be seen in the project’s
    views.py line 43, the template
    “notices.html” is used. Line 53 uses “single.html” . But the
    project does not provide these
    template anywhere in its directory
    structure. What is going on there?
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T10:14:53+00:00Added an answer on May 13, 2026 at 10:14 am

    I can very well do that using
    django-notification’s options in the
    admin section. Am I right?

    Yes. You can add or remove them via the admin later. It just makes it easy to use the same notice types in your code without worrying about getting them exactly right every time. For example if you are using the same notice types and constantly resetting your app while you’re developing (like me) this can be a big time saver.

    What are these default templates?
    Where do they need to reside? Is
    putting the four templates mentioned
    in the docs in a “notification”
    directory in the template loader path
    sufficient?

    django-notifications includes most of the basic templates you need in notification/templates, however it is still missing single.html. To use your own templates, put them in your usual template directory under /template-path/notification/template_name. This will override the defaults. You can also add granular templates for each notice type by using the format /template-path/notification/noticelabel_noticeformat.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This may be a bit of a nooby question, I have been trying to
I know this question has been done but I have a slightly different twist
I have a CMS with a WYSIWYG editor which produces pretty good xhtml. Based
Why would I want to use PHP's filter library? Why wouldn't I? It seems
I've been going through the process of cleaning up our controller code to make
I am writing a Firefox extension. I would like to search the current webpage
I am shortly starting a project, which requires messages to be held in a
I'm trying to do a bit of facebook integration with a website, and there's
My company is looking to replace all websites in the group with a new

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.