(sorry wrong button)

What a pity Greg! One tiny detail here. When starting the app this is shown in 
the log:

---------------------------------------------
MAGNOLIA LICENSE
---------------------------------------------
Version number : 4.3.4
Build          : 23. ?ervenec 2010 (rev. 35958)
Edition        : Enterprise Edition
Provider       : Magnolia International Ltd. ([email protected])


The name of the month in the build is quite special.
Bye, Bert
________________________________________
Van: [email protected] [[email protected]] namens 
Grégory Joseph [[email protected]]
Verzonden: maandag 26 juli 2010 14:58
Aan: Magnolia User-List
Onderwerp: Re: [magnolia-user]  Magnolia 4.3.4 released

Hi Bert,

Both valid points which we've noticed moments after we announced the release, 
probably at the same time you did :-/
We're issuing yet another bugfix release soon.

-g

On Jul 26, 2010, at 11:15, Bert Leunis wrote:

>
> Hi Grégory,
>
> Thanks for the quick release of stk 1.3.3!
>
> I tried it out and ran into the adaptations needed for MGNLSTK-653, -657 and 
> -658. I adjusted our templates as needed, and updated the site configuration 
> where needed (adding the 'enabled' property in three places). Two questions.
>
> 1. Is it not necessary to update the bootstrap in standard-templating-kit for 
> the default site configuration so that the three 'enabled' properties are 
> added there too?

> 2. Without these properties in the site config, the templates give freemarker 
> errors ("Expression def.header.branding.enabled is undefined" etc). Is it an 
> idea to change the getters of 
> info.magnolia.module.templatingkit.templates.Area to return defaults that are 
> not null? That is 'false' if the enabled-property is not set, and 
> Collections.emptyList() for getParagraphs if not set?
>
> Best regards, Bert
>
> ________________________________________
> Van: [email protected] [[email protected]] 
> namens Grégory Joseph [[email protected]]
> Verzonden: maandag 26 juli 2010 9:11
> Aan: Magnolia User-List; Magnolia Dev-List
> Onderwerp: [magnolia-user]  Magnolia 4.3.4 released
>
> Hi list,
>
> Magnolia CMS 4.3.4 has just been released. This is fixing a last minute bug 
> introduced in STK templates and is a recommended update for all users of 
> Magnolia 4.3.x
>
> See the release notes for more details:
>  http://documentation.magnolia-cms.com/releases/4-3-4.html
>
> Download:
>  Community Edition: http://sourceforge.net/projects/magnolia/files/
>  Enterprise Edition: http://www.magnolia-cms.com/home/top-level/download.html
>
> These are of course also available through our Maven repositories:
>  http://repo.magnolia-cms.com/m2/
>  http://repo.magnolia-cms.com/enterprise/
>
> Maven generated sites: (incl. javadoc)
>  http://dev.magnolia-cms.com/ref/4.3.4/
>
> The Magnolia team would also like to thank everyone who reported issues, 
> contributed patches, or simply commented on issues for this release. Your 
> continued interest helps us make Magnolia CMS better.
>
> Cheers,
>
> -greg
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to