Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Hi,
I am using NewsletterStudio version 1.4.1 and Umbraco (6.2.4 specifically), I cannot change the render values in my render task class above:
Any help would be really appreciated.
public override void ProcessUniqItem(RenderResult renderResult, RenderTaskUniqItemParameters parameters) { renderResult.MessageBody = renderResult.MessageBody.Replace("[antao]", "joao.antao"); }
Thanks.
Hi!
The code looks right... except that the line is commented out...
Did you add your RenderTask to the configuration file in /config/newsletterStudio.conig?
If you debug with a breakpoint - does the execution hit your code?
// m
Hi Markus,
This is the .config line, for the custom render task:
< task name="UnsubscribeRenderTask" type="Bril.Umbraco.NewsletterStudio.UnsubscribeRenderTask, Bril.Umbraco.NewsletterStudio" />
I could not get a hitting execution there as well, any help is really appreciated.
EDIT - The ProcessPreRender() override methods get in the hitting execution, and work A ok. (they are in the same class)
Upgraded to version 1.4.5.1 (latest to be release for v6.x versions, I believe) when in 'Send test email' mode the custom unique attribute does not change. It will only happen in a 'real' send-out.
Thanks right!
Since a preview is not a "real" representation of the newsletter the preview can't render something that is tied to a specific receiver.
In preview mode you can use the "ProcessPreview()"-method to replace a placeholder with some generic information to illustrate the feature.
public override void ProcessPreview(RenderResult renderResult, RenderTaskParameters parameters) { string html = renderResult.MessageBody; html = html.Replace("[email]", "email@example.com"); html = html.Replace("[name]", "Subscriber Name"); renderResult.MessageBody = html; }
I always tend to recommend that you send a "real" send out to a "real" list (with test-emails) when you build your custom render tasks.
Cheers!
And =D I'll make sure to improve the documentation about this as well. Thank you for making me aware.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion
ProcessUniqItem() in CustomRenderTask
Hi,
I am using NewsletterStudio version 1.4.1 and Umbraco (6.2.4 specifically), I cannot change the render values in my render task class above:
Any help would be really appreciated.
Thanks.
Hi!
The code looks right... except that the line is commented out...
Did you add your RenderTask to the configuration file in /config/newsletterStudio.conig?
If you debug with a breakpoint - does the execution hit your code?
// m
Hi Markus,
This is the .config line, for the custom render task:
< task name="UnsubscribeRenderTask"
type="Bril.Umbraco.NewsletterStudio.UnsubscribeRenderTask,
Bril.Umbraco.NewsletterStudio" />
I could not get a hitting execution there as well, any help is really appreciated.
EDIT - The ProcessPreRender() override methods get in the hitting execution, and work A ok. (they are in the same class)
Upgraded to version 1.4.5.1 (latest to be release for v6.x versions, I believe) when in 'Send test email' mode the custom unique attribute does not change. It will only happen in a 'real' send-out.
Hi!
Thanks right!
Since a preview is not a "real" representation of the newsletter the preview can't render something that is tied to a specific receiver.
In preview mode you can use the "ProcessPreview()"-method to replace a placeholder with some generic information to illustrate the feature.
I always tend to recommend that you send a "real" send out to a "real" list (with test-emails) when you build your custom render tasks.
Cheers!
// m
And =D I'll make sure to improve the documentation about this as well. Thank you for making me aware.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.