Hi Markus,

thank you for your code-snippet. That's great! Thank you!

But now I have the problem, that parameters.Newsletter.ContentNodeId is NULL...

Here the pictures from the Content-Node and from the Newsletter:

Is there one more thing to do, that the ContentNodeId gets saved in the parameters?

Hi!

Thank you!

This will only work if you are sending from the content-section, in other words if the newsletter is created from a umbraco node.

That war my problem. I added the Newsletter Sendout to the Documenttype and it works :)

Thank you for helping!

Cool!

The thing is that when you send from the content section, the newsletter will be connected to the node that is used to create it. When you are using the "insert url content"-feature there is no real connection except for the URL that is entered - this could even be an external URL on another website.

Great that you got it working =D

Please let me know if you have any other questions etc.

// m

Hi!

No, not at the moment as we're not passing the MailMessage-object to the pre-render methods.

My tip would be to send a "real" message to a list of test-subscibers (like your self and some collegues or something).

// m

Ok. No problem. Thank you!

Hi Keilo,

of course! Here is my RenderTask to attach the file:

public class RenderNewsletterMarker : RenderTask {
private IMemberService ms;
string _attachmentPath = String.Empty;

public RenderNewsletterMarker()
{
    ms = ApplicationContext.Current.Services.MemberService;
}

public override void ProcessPreRender(RenderResult renderResult, RenderTaskParameters parameters)
{
    try
    {
        if (parameters.Newsletter.ContentNodeId.HasValue && parameters.Newsletter.ContentNodeId.Value > 0)
        {
            // Get this node as a IPublishedContent-object
            var helper = new UmbracoHelper(UmbracoContext.Current);
            var node = helper.TypedContent(parameters.Newsletter.ContentNodeId);

            if (node.HasProperty("nl_attachment") || node.GetPropertyValue("nl_attachment") != null)
            {
                var attachment = node.GetPropertyValue<IPublishedContent>("nl_attachment");

                if (attachment.GetType().Name == "Image")
                {
                    var _attachment = (Image)attachment;
                    _attachmentPath = HttpContext.Current.Server.MapPath(_attachment.Url);
                }
                else
                {
                    var _attachment = new KomXCms.Models.Generated.File(attachment);
                    _attachmentPath = HttpContext.Current.Server.MapPath(_attachment.Url?.ToString());
                }
            }
        }
    }
    catch (Exception e)
    {
        LogHelper.Info(this.GetType(), e.Message);
    }
}

public override void ProcessPreview(RenderResult renderResult, RenderTaskParameters parameters)
{
    //renderResult.MessageBody = renderResult.MessageBody.Replace("[anrede]", "ProcessPreview");
}

public override void ProcessUniqueItem(RenderResult renderResult, RenderTaskUniqueItemParameters parameters)
{
    if (!string.IsNullOrEmpty(_attachmentPath))
    {
        // add new attachment to the e-mail;
        parameters.MailMessage.Attachments.Add(new Attachment(_attachmentPath));
    }
} }

I use the newsletterstudio like this: I have a content-Node which is rendering the whole content for the Newsletter:

On the same page I have the sendout: This is necessary, that the the RenderTask knows from wich page he should take the Attachment.

I hope this helps you!

it's also helpful to watch the last two videos on this page:

https://www.newsletterstudio.org/videos/

(Send newsletters from the content section, Work with the content using Render Tasks)

That looks cool Jeremias!

Many thanks for sharing your use case and rendertask !

I was using the Newsletter standalone section and wasnt quite sure on how to operate the RenderTask only when its used in Content Section. Looking for ContentId and perhaps a flag within RenderTask should not disturb Newsletter Section standalone usage along with occasional Content section usage.