django-widgy-blog 0.2.3

Quickstart

(This guide assumes that your project is already using widgy. Please see this tutorial if this is not the case.)

1. Install the package

   $ pip install django-widgy-blog

2. Add widgy_blog to your INSTALLED_APPS.

3. Run python manage.py migrate in order to generate the relevant models in the database.

4. Configure the urls:

   1. If you’re using widgy’s contrib.urlconf_include package, you can opt to use widgy_blog as a plugin. This allows admin users of the site to take advantage of plugin-specific features, such as editing the url route of the blog and customizing its addition to menus. See urlconf_include for more information.

   2. Alternatively, you can include the widgy_blog urls within your urls.py file as you normally would. Just remember to add them before the included Mezzanine urls if you’re editing the root conf!

5. That’s it. Log in to the admin center and start adding blog posts!

0.2.3 (2019-07-15)

• Blog views with pagination will now calculate appropriate rel=prev and rel=next links.

• Added Django 1.10 support.

0.2.2 (2016-02-08)

• Fix subclassing view name bug

0.2.1 (2016-01-14)

• Fix PyPI bug

0.2.0 (2016-01-14)

• Support for Django 1.8

• Blog archives are now shown in reverse chronological order.

• Blogs now have date and time rather than just date published.

• Tags are now supported

• Various small bugfixes.

• Blog views with a page querystring equal to 1 will now have a canonical_url in the template context pointing to the same page without that querystring.

0.1.0 (release 2014-12-03)

• Add model attributes to AbstractBlogLayout and BlogAdmin that make them easier to subclass. Update AbstractBlogLayout published queryset function to use fewer queries [Scott Clark, #18]

• Backwards Incompatible: Registered the BlogLayout model with widgy. If you weren’t using this as your Blog layout, you will need to unregister it:

  import widgy
  from widgy_blog.models import BlogLayout
  
  widgy.unregister(BlogLayout)

  If you were already registering the BlogLayout yourself, you can just remove that code.