Thursday 05 April 2007 3:22:02 am

Hello Ismael,

1. Short yes :).
You have several possibilities to achieve this. You must know that you will ever have to create a contentobject that represents the newsletter. The rendering is templated based so you can in your templates decide how and where to fetch the content.

The first is, using the newsletter_issue class and add the articles to the relation list attribute 'topics'. By using the designs those will be directly shown in the sent emails.

Another way is using a class with an XML field in it. There you could embed every object you want. Then you need to ensure, that you have overrides for those objects in your design (do not forget to use that design when running the cronjobs).

And last but not least you could use some attributes in the newsletter content object and a template that fetches its content based on that data. For example you could have a relation attribute that points to a folder. The template could fetch all childs of that folder and send them with the newsletter.

2. Hmm I need some more details about that.
Have you tried our upcoming installer [1] ?
You can send yourself a preview of the newsletter during editing. Just fill the "preview email" text field with your address and click on "send preview" button. If you do not recieve a preview then you should check your email server settings. By default it will use sendmail.
To send the newsletter have to execute the cronjobs like described in the install document [2]

[1] http://ez.no/community/news/ez_newsletter_1_5_beta_1_released
[2] http://ez.no/download/add_ons/ez_newsletter/installation_instructions_for_ez_newsletter_1_5beta1

Thursday 05 April 2007 5:14:45 am

Ah ok. I guess I understood now.

When you create a newslettertype it is not the actual newsletter. It just defines a frame for your newsletters. Like defining senderaddress, available templates, contentclasses that can be used for the newsletters, to define the subscriberlists that will recieve newsletters of that type and so on.
After you've created a newslettertype (dont forget to define the newsletter placement) you can create a newsletter.

To make it more understandable a little bit easier formulated. The newslettertype is something like a magazine and the newsletters are the actual issues of that magazine.

Please ensure that you have an override for each contentclass that should be used for sendouts
Example for the class newsletter_issue:

[edit_article]
Source=content/edit.tpl
MatchFile=edit_article.tpl
Subdir=templates
Match[class_identifier]=newsletter_issue

And I speak german right :)

Tuesday 10 April 2007 12:18:19 pm

Hi,

It seems your preferred language is german so I answer in two languages. So that other can partly follow.

English:
------------

You have to ensure that you selected the newsletter issue class as allowed content class in the newslettertype.

After that you navigate to the view of the type and at nearly the bottom of the page you should find a button "Create newsletter"

German:
------------

Du must sicherstellen, das Du beim Newslettertypen als erlaubte Contentklasse newsletter_issue auswählst.

Danach wechsel zur Ansicht des Newsletttertypen und ziemlich am ende der Seite sollte eine Schaltfläche mit der Aufschrift "Create newsletter" finden.

Wednesday 11 April 2007 3:32:07 am

Hi,

I guess you clicked on preview sendout and that error came up right?
But anyway there had been errors and I fixed them in trunk. It will soon be released. Until then you shouldnt use the SMS format.
Anyway you must know, when you use the SMS format you need to implement a class that handles the transport to your specific sms gateway. This is needed because every gateway has a different API.

I hope that helped you for now.

Cheers,
Tobias