The user can't put files in extensions unless s/he has access to the file system. However the user doesn't have access either to the default repository location for the newsletter XSL files through the CMS.
Regards, Jasha Joachimsthal www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > ajankowska > Sent: dinsdag 12 augustus 2008 9:55 > To: 'Hippo CMS development public mailinglist' > Subject: RE: [HippoCMS-dev] newsletter layouts > > > A workaround is to use the extensions location instead of the > > repository. > > How cms user can put file into extensions using only hippo > cms interface? > > I have also noticed that in the environment with file system > as repository I don't have this problem. My xslt changes > dynamically after each download/remove file from binaries. > > Maybe it is possible to configure MYSQL connection to have > the same behavior like with file system? > > Regards > > Ola > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Jasha Joachimsthal > Sent: maandag 11 augustus 2008 12:02 > To: Hippo CMS development public mailinglist > Subject: RE: [HippoCMS-dev] newsletter layouts > > A workaround is to use the extensions location instead of the > repository. > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Ard > > Schrijvers > > Sent: maandag 11 augustus 2008 12:00 > > To: Hippo CMS development public mailinglist > > Subject: RE: [HippoCMS-dev] newsletter layouts > > > > > > > > > > The idea is to change newsletter layouts using repository > > (also easy > > > for cms user), I need to add newsletter-*-*.xsl file for > different > > > newsletter types I want to create. I didn't know that > this xslt is > > > cached. > > > > This is default cocoon behavior > > > > > > > > > If this is needed, I could take a look at it, but must be > > scheduled > > > > some way > > > > > > How it can be scheduled? > > > > Like a projectmanager who schedules time for me to look > into it :-))) > > > > -Ard > > > > > > > > Regards > > > > > > Ola > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of Ard > > > Schrijvers > > > Sent: maandag 11 augustus 2008 11:43 > > > To: Hippo CMS development public mailinglist > > > Subject: RE: [HippoCMS-dev] newsletter layouts > > > > > > > Hi, > > > > > > > > > I can now download into binaries new layouts for > > newsletter (.xsl > > > > > files), but somehow it is also stored in > > > > > /work/Jetty_0_0_0_0_50000__/cocoon-files/upload-dir > > > > > and I need to restart cms to load new transformation file > > > > > > > > > > Do you know how to prevent saving binaries into this place?? > > > > > > > > why would you like to prevent saving binaries into cache? > > > > > > This is just the jetty upload-dir which is totally > > irrelevant for your > > > problem. The problem is totally different, and that is that xslt > > > stylesheets get compiled, and then cached in the transient > > in memory > > > store. Only, this store is not eventaware, so won't > reload an xslt > > > stylesheet changed in repository. I think I must be able to > > fix this > > > quite easily, but will take some time, to cache xslt in the event > > > aware memory store. > > > > > > If this is needed, I could take a look at it, but must be > scheduled > > > some way > > > > > > Regards Ard > > > > > > > > > > > Met vriendelijke groet, > > > > Mathijs Brand > > > > Hippo > > > > > > > > [EMAIL PROTECTED] > > > > > > > > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam > > > > +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, > > > > suite Q Petaluma CA > > > > 94952-3329 +1 (707) 773-4646 > > > > > > > > www.onehippo.com [EMAIL PROTECTED] > > > > > > > > ******************************************** > > > > Hippocms-dev: Hippo CMS development public mailinglist > > > > > > > > Searchable archives can be found at: > > > > MarkMail: http://hippocms-dev.markmail.org > > > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > > > > > > > > > > ******************************************** > > > Hippocms-dev: Hippo CMS development public mailinglist > > > > > > Searchable archives can be found at: > > > MarkMail: http://hippocms-dev.markmail.org > > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > > > > > > > > > > > ******************************************** > > > Hippocms-dev: Hippo CMS development public mailinglist > > > > > > Searchable archives can be found at: > > > MarkMail: http://hippocms-dev.markmail.org > > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > > > > > > > ******************************************** > > Hippocms-dev: Hippo CMS development public mailinglist > > > > Searchable archives can be found at: > > MarkMail: http://hippocms-dev.markmail.org > > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > > > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
