Okay I realize a can clarify somewhat here.
The login field reads.
{BLOGNAME} has posted a new item, ‘{TITLE}’
{AUTHORNAME} has added a new post:
The resultant email looks like this
Tuesdays with Deborah has posted a new item, ”
has added a new post
Gifts of Peace (Author: Paul Zohav)
That doesn’t seem right. AM I doing something wrong?
I jist notice something else strange:
Our Subscribe2 post email use to be:
{BLOGNAME} has posted a new item, ‘{TITLE}’
{POST}
You may view the latest post at
{PERMALINK}
but our resultant email was:
Tuesdays with Deborah has posted a new item, ”
Gifts of Peace
http://www.authenticwritingprovokes.com/inspiredwriting/2012/04/gifts-peace/
“content of post”
You may view the latest post at
Is that right?
@itechieguy,
I’m guessing here because you have said explicitly but you seem to be using Subscribe2 in digest mode. As you’ll see from the settings page (Subscribe2->Settings) digest emails cannot use the {TITLE} keyword.
If you leave {AUTHORNAME} in here the title of the post with have (Author: AUTHORNAME) after it.
You are right I am talking about digests.
So my Subscribe2 email field looks like this:
{BLOGNAME} has posted a new item,
{AUTHORNAME} has created a new post:
{POST}
but my preview look like this:
Tuesdays with Deborah has posted a new item,
has created a new post:
Gifts of Peace (Author: Paul Zohav)
@itechieguy,
Okay, perhaps I wasn’t clear enough in my comment above. If you put {AUTHORNAME} anywhere in the template, for digest emails it’s position will be ignored and the Author details will be added next to the Post Title, just as you pasted above:
Gifts of Peace (Author: Paul Zohav)
The digest code collects all posts made between 2 dates and then loops through them all creating a text block containing details of the post title, link, author, categories, tags and content.
I’m not 100% sure of my maths but given that some people won’t want all six while others would and people will want different order that could be 720 different email results from those 6 parameters alone.
If you use Digest mode your control over the final format is more restricted so that the code will actually work before running out of execution time.
I can’t help to wonder if it would be better to separate the digest email from the post email. If you ask me, that adds confusion. As a matter of fact, when I went into the Subscribe2 settings area I first looked up and down for a digest setting and found none. A digest e-mail could be accomplished with three fields.
Digest Email Information
Header Field– This stuff would go at the top of the digest
Per Post Field– This is where the per post message could be built
Footer Field– This stuff would go at the bottom of the digest.
This would clear up the confusion between the per post and digest emails.
Just my 1/50 of of dollar.
