Implement basics of blogentry-alert

[Paul Everitt]

Implement the basics of sending an alert when a new blog entry is posted in the community.

Details
=========

- Read the UAT at https://bugs.launchpad.net/karl3/+bug/336495 (which leads to the writeup at http://carlos.agendaless.com/dko/policies/blog.html#blog-entry-alert)

- First success case is: create a new blog entry via a browser, all users in the community get an email per the formatting rules in the UAT

- Second success case is: ditto, but with attachments on the blog entry

Implementation Details
==================

- Blog is in src/karl.content

- Use get_setting for system name, system email domain

Postpone
===========

To keep this task manageable, let's carve parts out so we can get to a known success point without overload.

- Handling per-user, per-community tri-state (now, digest, never) preferences on alert sending

[Paul Everitt (paul-agendaless)]

Here's the first task. I fully expect this to lead to a bunch of questions on details I omitted. Let's do our best to pick a manageable part of the problem as the first step and defer as much complexity until that part is tackled.

[Paul Everitt (paul-agendaless)]

I just realized that attachments to a blog entry (or blog comment) aren't sent as email attachments. Instead, a hyperlink goes in the email to point at each attachment.

I'll update the UAT writeup to denote this.

[Paul Everitt (paul-agendaless)]

Here is a screenshot of an alert sent when a blogentry has multiple attachments.

[Chris Rossi (chris-archimedeanco)]

Extraneous bug found: "Cancel" button does nothing in edit_profile view. Can probably fold fix into this bug.

[Chris Rossi (chris-archimedeanco)]

Actually strike that last. I see I'm not doing anything with the user preferences on this go around so I'll likely not touch the cancel button code.

[Chris Rossi (chris-archimedeanco)]

First milestone checked in.

[Chris Rossi (chris-archimedeanco)]

Unit test now fails after svn update. May be weird merge interaction caused by my forgetting to check in code yesterday. Investigating.

[Chris Rossi (chris-archimedeanco)]

Yep, someone was trying to triage my only half checked in code. Sorry about that! Fixed now.

[Paul Everitt (paul-agendaless)]

That was me, sorry, should have let you know.

--Paul

On Mar 4, 2009, at 10:31 AM, Chris Rossi wrote:

> Yep, someone was trying to triage my only half checked in code. Sorry
> about that! Fixed now.
>
> --
> Implement basics of blogentry-alert
> https://bugs.launchpad.net/bugs/336863
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Porting KARL to a new architecture: In Progress
>
> Bug description:
>
> Implement the basics of sending an alert when a new blog entry is
> posted in the community.
>
> Details
> =========
>
> - Read the UAT at https://bugs.launchpad.net/karl3/+bug/336495
> (which leads to the writeup at http://carlos.agendaless.com/dko/policies/blog.html#blog-entry-alert)
>
> - First success case is: create a new blog entry via a browser, all
> users in the community get an email per the formatting rules in the
> UAT
>
> - Second success case is: ditto, but with attachments on the blog
> entry
>
> Implementation Details
> ==================
>
> - Blog is in src/karl.content
>
> - Use get_setting for system name, system email domain
>
> Postpone
> ===========
>
> To keep this task manageable, let's carve parts out so we can get to
> a known success point without overload.
>
> - Handling per-user, per-community tri-state (now, digest, never)
> preferences on alert sending