On Wed, 2006-01-18 at 12:22 +0100, Andreas Hartmann wrote: > Josias Thoeny wrote: > > On Mon, 2006-01-16 at 18:39 +0100, Joern Nettingsmeier wrote: > > > >>another small gotcha: > >> > >>when i try to create a new language version of a document i just created > >>after applying your patch, i get this (url is > >>http://localhost:8888/UniDuE-Design/authoring/index.html?&lenya.usecase=site.createLanguage&lenya.exitUsecase=tab.overview&;): > >> > > > > > > There is a known bug about creation of new language versions: > > http://issues.apache.org/bugzilla/show_bug.cgi?id=36960 > > > > As a temporary workaround, you could apply the following diff: > > [...] > > I added the method SiteManager.isVisibleInNav() to allow CreateLanguage > to use the value of the existing language version. In fact, IMO the > DocumentManager.add() and SiteManager method signatures should be changed, > as the visibility attribute belongs to the node and not to the document.
Ok. I also think the visibility belongs to the node. And there may be other attributes which are properties of the node, this is why the idea to use meta data for the node came up some time ago. What about about having a method contentNode.getMetaData(...), just like document.getMetaData(...)? Or is it better to use specific methods like isVisibleInNav()? > > The CreateLanguage usecase should work now, though I often get the > metadata-related "invalid UTF-8" exception :( That's bug http://issues.apache.org/bugzilla/show_bug.cgi?id=36341 I'm currently working on it, but I still have some troubles... Josias > > -- Andreas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
