I am trying to make nicely formatted (html), cross email client compatiable Order Confirmation and Shipping Confirmation emails.
The problem is that the notification message page uses a RTE for input and that throws away markup and also moves {{IterationStart[Invoice.Items]}} and {{IterationEnd[Invoice.Items]}} tags upon save (as the RTE doesn't think they are valid inside <table> markup).
For now I have updated the database directly in order to produce the desired emails, but run the risk that if anyone was to go to the message editor to change an email address or subject line text and save, it will save the now manipulated and incorrect email template.
Is there a quick hack that will allow me to change this field to a normal multi-row textarea field so that the markup will not become corrupted by the RTE on save?
Trevor - the RTE is validating the table and it is one of my to dos to give another option for formatting the message. Ultimate goal is to be able to create email messages with Razor views rather than using patterns.
We can't add a dependency that is not shipped with Umbraco ... that's one of the restrictions we've put on the Merchello project. It's just easier to stay on the same path if we don't introduce something that may not work in the future.
I've been thinking of something along these lines:
I think that we can read source code of Postal to have an idea or see the code. It's opensource and works very well.
Other commodity could be that "print views" must be edit from backoffice.
Notification Message Editor - changes markup
I am trying to make nicely formatted (html), cross email client compatiable Order Confirmation and Shipping Confirmation emails.
The problem is that the notification message page uses a RTE for input and that throws away markup and also moves {{IterationStart[Invoice.Items]}} and {{IterationEnd[Invoice.Items]}} tags upon save (as the RTE doesn't think they are valid inside <table> markup).
Eg, if your markup is
The RTE after save does this
For now I have updated the database directly in order to produce the desired emails, but run the risk that if anyone was to go to the message editor to change an email address or subject line text and save, it will save the now manipulated and incorrect email template.
Is there a quick hack that will allow me to change this field to a normal multi-row textarea field so that the markup will not become corrupted by the RTE on save?
For example, I tried to change....
To this
But the markup didn't appear in the textarea.
Thanks.
Whoops...ignore duplicate closing tbody/table tags in the example...copy/paste error!
Did you use the "source code" button (far left of RTE bar) to view/fix it? On the more complex emails, that is what I have to do.
Yep....did that but on save it moves the iteration tags. Did you manage to get repeating table rows? What version of Umbraco are you using?
Trevor - the RTE is validating the table and it is one of my to dos to give another option for formatting the message. Ultimate goal is to be able to create email messages with Razor views rather than using patterns.
With Razor view, I suggest to use Postal MVC
@Biagio - that is where I want to go with it but need to find some time to get it worked into the schedule.
If you want to take a stab at getting it going, I'd love to help you get it in there! =)
Hi,
I know Postal because I use it in some my project. How can I help you?
We can't add a dependency that is not shipped with Umbraco ... that's one of the restrictions we've put on the Merchello project. It's just easier to stay on the same path if we don't introduce something that may not work in the future.
I've been thinking of something along these lines:
http://forums.asp.net/t/1888849.aspx?Render+PartialView+without+ControllerContext
I'll give a read and try.
I think that we can read source code of Postal to have an idea or see the code. It's opensource and works very well. Other commodity could be that "print views" must be edit from backoffice.
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.