> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Andrew Savory > Sent: vrijdag 7 maart 2008 10:28 > To: Hippo CMS development public mailinglist > Subject: Re: [HippoCMS-dev] community apps > > Hi, > > On 07/03/2008, Calcus david <[EMAIL PROTECTED]> wrote: > > > > The reason to throw a pipeline when we send a newletter is to make > > some modifications in the repository (typically rename a folder, > > create a folder and a new file in it). > > > Don't do this :-) > > It might be better to modify the newsletter manager itself, > since you only want to rename the folder as an atomic part of > the sending process (you don't want the newsletter to fail > but rename the folder, and you don't want the newsletter to > succeed but not rename the folder etc)
I'll explain how the process works: 1) You create a document in the repository that is the raw XML content for the newsletter 2) You create a mailing from the community apps. During the creation (and when you click on the refresh or test mail button), the raw XML is transformed into the final HTML and text versions. This transformed versions are stored 'as is' in the database. 3) The mailing is triggered from the spring cron. The content for the mailing is retreived from the database. No call to the repository is done at this moment. This is done to be sure that the latest content generation has been done in the newsletter manager (e.g. when sending a test mail), not in the CMS editor. We're working on the Javadocs but we have to arrange some other things first before we can publish them. You can checkout the code from the public svn [1] Jasha [1] http://svn.hippocms.org/repos/hippo/hippo-components/hippo-community-app s/tags/Release-HCA-v2_01_01/ ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
