CMS MADE SIMPLE FORGE

Newsletter Made Simple

 

[#1184] newsletter archive tag

avatar
Created By: olaf noehring (olaf_noehring)
Date Submitted: 2006-11-29 10:42

Assigned To:
Resolution: None
State: Closed
Summary:
newsletter archive tag
Detailed Description:
Hi

I want to be able to show all newsletters that have been written so far.

Maybe use a tag:
mode='archive'

even better - show last 5 (example!) newsletters:
mode='archive' showlast='5'

or better - newsletters between dates:
mode='archive' showstart='UNIXTIMESTAMPHERE' showend='UNIXTIMESTAMPHERE'

Olaf

History

Comments
avatar
Date: 2006-11-29 10:43
Posted By: olaf noehring (olaf_noehring)

Hi

also: sorting would be nice:
mode='archive' showstart='UNIXTIMESTAMPHERE' showend='UNIXTIMESTAMPHERE'
sort='oldfirst'

oldfirst | newfirst

Olaf
      
avatar
Date: 2007-02-19 16:29
Posted By: David Streever (streever)

Hello Olaf & others,

this is a fantastic idea. I'd love to see something similar.

Is there any plan for such a feature: is it currently possible  considering the
way the module works?
      
avatar
Date: 2007-03-22 21:50
Posted By: Tim Poulsen (skypanther)

I've been working on adding this feature. It's roughly
working in the SVN version now. I need to decide what to do
with message template variables (like {$username} and
{$unsubscribe}). 

You would put this into a page to show the list of messages:
{cms_module module='NMS' mode='archive' show='2'}

the show='#' parameter controls how many are shown, newest
to oldest based on the date the message was first entered.

The database contains a date field called "entered" which
I'm thinking stores the datetime when the message was first
created and saved, not when it was sent. So, such dates
might not correspond to what you expect for the "most
recent" newsletters. For example, a message started but then
not sent for a month or two, then finally sent might not
show up within the range as you might expect. 

No sorting yet as suggested by Olaf.
      
avatar
Date: 2007-03-24 03:23
Posted By: olaf noehring (olaf_noehring)

Hi Tim,

I am not sure I understand what you are asking. Please rephrase it again. What
do you mean by $userbname /$unsubscribe?

Well I would think both dates would be useful in the backend (but I think the
"newsletter created date" ist already there?).
For the user in the frontend when he looks up the archive it would be much mor
usefull to show the date when the newsletter was actually sent. Admins could
create newsletters in advance, collect information and then decide to send a
newsletter once a month. This newly created, but not yet sent newsletter should
not be shown to the user.
We would need a new database field für the sending date.

Olaf
      
Updates

Updated: 2012-07-17 14:19
resolution_id: => 5
state: Open => Closed