Entry Mailing Documentation
Requirements
Entry Mailing requires ExpressionEngine 1.6.5 or newer and the jQuery for the Control Panel extension installed and enabled. This extension was introduced with 1.6.5 and if you carefully followed the update instructions you should have it.
If you don’t you can install it like outlined in the aforementioned instructions.
If you intend to send notifications to Mailinglists you obviously need a personal or commercial EE license. The Mailing List Module is not available in ExpressionEngine Core.
Installation
- Unzip the file.
- Upload the file ext.entry_mailing.php to the extensions-folder inside your EE system directory.
- Upload the file lang.entry_mailing.php to the language/english-folder inside your EE system directory.
- In your Control Panel navigate to CP Home › Admin › Utilities › Extensions Manager, find the Entry Mailing Extension and click Enable?
Updating
To update the Entry Mailing extension just act upon the installation instructions above, replacing the old files with the new ones.
Configuration & Usage
Supplement
Not yet shown in the screencast:
Beginning with version 1.1 you have the option to alternatively choose any regular EE template for creation of the message text.
To have access to the data of your weblog-entry use a normal {exp:weblog:entries}-tag without any parameters.
This template is treated like any other template you use to create webpages. That means you have all the usual templating-options at hand to create your email. You can use plugins, relations, embeds and even pull additional data from any other weblogs to supplement your mailing.
You can of course also pull data from weblog entries that are not related to the entry used to initiate the mailing. Just be sure to use dynamic=“off” in the exp:weblog:entries-tags used to do this. Something like
Dear subscribers!
Have you been following our weblog? Here are the topics we presented in July 2009:
<ul>
{exp:weblog:entries dynamic="off" weblog="blog" year="2009" month="7"}
<li><a href="{comment_url_title_auto_path}">{title}</a></li>
{/exp:weblog:entries}
</ul>
LG Addon Updater support
If you have the LG Addon Updater extension installed, it can check for Entry Mailing updates if you enable this feature in the Settings.
Changelog
1.2.3
• Added an option to display the entry-mailing-button directly on the publish form
mplates
1.2.2
• using $SESS->cache for parsing form fields. Just because (it saves some queries).
• fixed a bug that could occcur in conjunction with duplicate field names in MSM-sites
• To:, CC: and BCC: fields now accept variables (e. g. custom fields) in the mailing templates
1.2.1
• Re-added support for relative URLs when
is set.
1.2
• Extension settings are now separated per site if MSM is installed.
• Lowered the priority of one method to keep the FieldFrame extension from inserting data into generated mails.
1.1.1
• Fixed a bug occuring when the message-template contains javascript
• rewritten link-excerpt in plain-text generation
• relative links will be turned into absolute links if <base href> is set in the HTML
• small improvements to plain-text generation
1.1
• Added optional support for regular ExpressionEngine templates
• cosmetic changes applied to plain-text generation
1.0
• Initial release
Questions / bug reports
For general comments, brickbats & bouquets please use the form over here.Page 2 of 5 pages < 1 2 3 4 > Last »
User Talk
2010-06-29 22:49
Right, I did miss that part, thanks. So am I correct in my interpertation that:
1) I can’t use conditional variables in the subject line
2) To use conditional variables in the message, I need to use a template rather than the textarea in the config?
I’m not complaining, mind you…I think this is a great tool, but I’m kind of new to ee and just want to make sure I’m not missing something that more experience would teach me.
2010-06-29 20:54
Taking a look at the source code myself quickly showed my problem: I was using conditional variables in both the subject line and in the body, and the javascript was blowing up on the curly brackets in the subject line.
Removing
{if title != “”}{title}{if:else}New entry{/if}
as the subject line and replacing it with a simple {title} tag allowed it to populate the communicate form. So I guess it’s not possible to use conditional variables in the subject?
But now that the body is populating, I noticed related trouble with the body of the message:
In the “Message Template” textarea of the Entry Mailing config, I use the following codes:
There has been a entry added:
{comment_url_title_auto_path}
========================
{if title != “”}{title}
========================
{/if}
{body_pub}
So that it doesn’t show the empty title tag and an additional horizontal divider in case the title is left blank (which may happen sometimes with this particular blog). However, in the communicate tab, it renders the body between the horizontal dividers as:
========================
{if title != “”}Test of the mailing list system
========================
{/if}
Now, assuming that it was just a limitation on what I can put into the textarea template, I copy-n-pasted the codes from the textarea and instead made a page template and pointed the entry mailing config to that template. But it doesn’t seem to resolve the field variables…that is, {title} resolved to “” and {comment_url_title_auto_path} doesn’t get replaced at all…it comes through as the text “comment_url_title_auto_path” between curly brackets. Do I have to do something like extract the entry_id from somewhere and wrap the body in {ext:weblog:entry} tags pointing to that entry before they’ll resolve, or is it just not possible to use conditional variables in the e-mail message?
The documentation says we can use even other plugins as the input for the body, so I figured that would include the {if} syntax. For the time being, I can make do with a more static message, but I’d love to be able to have it be conditional, if there’s any way you can tell me to do it.
Thanks for your help, and for this tool!
2010-06-28 16:55
I’m trying to use our new entry mailing license to send the contents of a new post in a particular blog to a specific mailing list. I’ve set the e-mail template using the “Message Template” in the plugin configuration page, rather than using an existing template. Whether I use Automatic Mode or not, at the point where it should send out the message, it just takes me to ee’s “communicate” screen, with nothing filled out.
Am I missing a step somewhere? I’ve got ee v1.6.7, with jQuery for control panel enabled.
Thanks
2010-06-17 17:13
Hi - if I enter my code into a template, it doesn’t work. But if I enter the same code in the field within the settings and select “Use the Code Above” - it works. What’s happening is when I select “mail this entry” it takes me to the communicate tab and everything is blank. The template is using a WYGWAM field type. What’s going on? This worked on another site we purchased the extension for. Thanks for your help.
2010-04-06 00:01
Problem….
In creating entries, I am using a WYSIWYG editor, which uploads and inserts images into my entries providing HTML that looks like: /images/uploads/image.jpg
However, email clients are not able to view these images because they need the FULL URL and not just that half URL of where the image is located.
This is VERY important in mailing entries that are used as newsletters. I have a couple of clients that I have installed the entry mailer on and need for this part to work ASAP.
Any ideas or work arounds would be awesome!
Thanks 
