Skip to end of metadata
Go to start of metadata

Internal stuff, mailing lists etc

  • sendmail cleanup, tokens [???]
  • CRM-domain preferences to save field settings?, domain address stuff (CRM-700) [done]
  • figure out 'templates' feature in send mail wizard - eliminate functionality for 1.4 [done]
  • need to expose contact.is_opt_out to interface [done]
  • hide Process mailing queue menu (URL driven) - and set status msg on return page. [done, r4669]
  • probably set do not email flag on opt-out (why didn't we do that to begin with?) [done]
  • shell script to run jobs and doc for cron setup [done, bin/civimail.cronjob.php]
  • per derek annares, include/exclude mailings box doesn't work [works for me, except a mailing can't be another mailing's base - i.e., a mailing requires at least one group]
  • CiviMail / derek issues: opentrack, forward (where's the code, is it implemented), ongoing support... [opentrack should work in v1.3, forward is fixed in trunk, ongoing support means...?]
  • Fen's Verp Separator Issue and brian's reply NOT ADDRESSED - f/up CRM-720, etc. [CRM-720 closed, for Fen's issue see re-subscribe below]

From CivicActions

Show stoppers:

  • do_not_email: interplay of is_opt_out and do_not_mail is confusing and perhaps even incorrect; not at all sure this is working properly (CRM-768) [done]
  • is_opt_out needs a profile setting or should be combined with do_not_mail (CRM-769) [done]
  • re-subscribe (after un-subscribe) does not appear to work [it works, but AMaViS's Mail::Verp by default assumes the VERP separator to be a dash]
  • access to the preferred_mail_format setting (CRM-773) [done]
    • admin sets default, probably to 'Both' [deferred - for now, update the db default]
    • user profile settable personal value [done]

Nice to haves:

  • Header & footer (CRM-733) [done]
    • Can't be disabled [done]
    • HTML breaks table layout [done]
  • Better (e.g., one that exists) UI for token (replacement) values
  • Send.module integration would be cool (start with a node as the content). This would need a CiviMail API to the back end to add mails to the queue (or jump to the the CiviMail schedule page).
    • It would also be cool for the front end UI to be able to use TinyMCE and image modules as helpers when building the mail.
  • preview pane for text, HTML messages
    • ability to generate text message from HTML as a default
  • copyright assignation to civicrm.com (once we get this set up) for code contributions to CiviCRM
  • multi-site friendliness (low priority, most of this is done)
  • Drupal 4.7 compatibility [done]
  • CiviMail APIs for integration w/ Allie M's MLM module
Labels:

Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.