marshalc / emencia-django-newsletter Goto Github PK

Have removed in the short term to get 1.0 out quickly, but this is a high priority reimplementation that's needed.
Able to generate a blank (template) excel sheet for signups, and then ingest the same sheet again for mass import. Should be able to export existing contacts, and then pattern match them against existing ones on reimport so as to avoid failing on duplicates.

As the title says. Needs further investigation though first.

Plain text emails are all fine, or even ones with html in them, but if you provide a url to pull content from, then that is presently causing a silent failure.

Customise the output by including Full Name and email address, etc in the newsletter by variable inclusion

As title says. Some statistics are coming through like links clicked, messages sent, etc. But the "message viewed/opened" stat isn't registering yet.

Hi @marshalc, I hope you remember me still. I've looked into your notes for the cleanEDN branch, and while I like the idea to create something new on a solid base (loosing ties with Emencia the company), I feel that you are slightly off the target on several points:

• Please consider making a new project for this. There is virtually no chance of merge to the original project, and thus there will probably be no new releases under the old name. Every possible upgrade path is broken too, so there is no need to keep this new codebase somehow related to the original EDN. I'm currently using a git snapshot of EDN, which is not really properly maintainable and would gladly replace it with a proper released version of the new product.
• Please allow at least Django 1.6 as minimum version, since that's the last version which supports Python 2.6. I'm stuck at SLES11 right now and they only have Python 2.6.9.
• Dropping private newsletters is a mistake. If anything, I'd drop public ones and work from there. The original Emencia idea (if I understand it correctly) is that a public newsletter can be linked to from the e-mail and is also published elsewhere, i.e. accessible without subscription. Also, a subscription form will allow a user to subscribe to all public newsletters. If your use case is anything like mine, you'd like to send newsletters to a group of people and only to them, which is exactly the use case for private newsletters. But in any case, both should probably be possible.
• Attachments: I need them. We send PDFs as attachment to our newsletter, since nobody wants to hack HTML and CSS for different mail clients (it's a different, more demanding version of IE6 hell). The newsletter itself is more like "look into attachment".
• Internationalization: a must for any software project. If you need help with that, I can help, but don't throw it out unconditionally.
• Workgroups: I can see the need that Emencia had (large marketing deparments, several dozens of newsletters per week, different people for different newsletter etc.), but there is probably indeed not much need for that in the first iteration.

Those are initial thoughts. More probably to come...

Most content for newsletters I foresee coming from the associated Mezzanine CMS setup, and specifically certain blog posts. Make selecting of blog posts easy, and use it for both newsletter content, and as a location to allow people to view it online.

When presented with a list of available subscribers on creating a mailing list, that list should take account of the contact.subscriber attribute. Presently it is ignoring it an presenting all contacts as available.

Allow files to be uploaded to a newsletter, and then mailed out in the newsletter (with the appropriate links back to the website hosting the attachments). Try to avoid sending attachments in the mail as this tends to cause some problems with spam filters, mail size limits, etc.

Allow there to be a specified rate at which mails are sent on command, or a specific number processed each time send_newsletter is called.

For an as yet unknown reason, the admin submenu list is one pane and covering the graph in the View Statistics template (but not in any other that I can see).

When I try to export a MailingList to an .xls file, I encounter the following error:

TypeError: can't subtract offset-naive and offset-aware datetimes

As it is explained is this thread https://github.com/python-excel/xlwt/issues/23, xlwt does not handle offset-aware datetimes, so we should convert datetimes to be offset-naive before an .xls export.

I will probably submit a pull request soon.

I recall issues in using the stats package in recent times with layout issues. Likely caused by not being in sync with Bootstrap and the admin base any more.

Fix: cleanEDN/edn/templates/views/newsletter_statistics.html
& newsletter_density.html
& newsletter_historic.html

As a shortcut, have skipped the test work for the time being (wrist slapped), but want to understand this more fully for later on.

Given a URL, ingest that and clean it for use as HTML email content for sending

Have some form of WYSIWYG editor in place (likely TinyMCE) for the creation of HTML emails

All newsletters will be generated from a django template, and a list of available ones should be presented to the user when creating/editing the newsletter. If there is a theme_app installed in a project, then the edn should be able to scan for suitable templates and add those to the list.

Goes without saying :-/