[EMAIL PROTECTED] wrote: > > We have also tested the multilang feature. We created a MidCOM Site and > > then set the lang field of the created host for testing purposes. But > > now we get the following error: > > > >> Failed to list Snippets in /de/linkm/taviewer/_midcom : MGD_ERR_OK > > > > It seems that *all* localizable objects must have a corresponding lang > > content if the lang is set for a host. > > > > Is it possible to set a "trigger" that if no localized content exists > > for an object, the lang=0 content will be loaded? Or is multilang not > > (yet) compatible with MidCOM?
Can you provide code which was used? And the code which returned debug message? > > Actually we would also need topic_i tables since our cms solution uses > > topics as content-pages and articles are just parameters of that page. > > Unfortunately we are not c-programmers and cannot contribute it... Are > > there any plans to support multilang also for topic objects? Current plans are to support everything for everything , even code for attachment :) You may fill request for topic at midgard.tigris.org. > MidCOM currently does not support Midgard-style multilang. It has its own > L10N system, which is completly independant of Multilang Midgard. Primary > reasons for this is the fact, that I personally[1] still count > Multilang as an experimental, not yet complete feature, which I don't use > in production. If it reaches that state in my personal opinion, I will > integrate this with MidCOM - if it is feasible. If not, I might very well > make the Datamanager language-aware, and implement this on my own. > > > [1]: It is my very personal opinion here. I know, that there are people > out there, using multilang in a productive envrionment, but until now it > does not hold up to the requirements I have to it, besides the fact, that > there are far more important problems there are right now with the core. > You all know my Mail regarding a fresh start. I personally (!) just don't > see the benefit in investing in another legacy technology, It is some kind of nature of every software which would like to be an Application Server. Many technologies and many solutions. We won't be ready for big (even huge) changes with next releases when we do not start to test it now. Of course I do not want to force anybody to use every features :) > which will be > deprecated when Midgard 2 starts to arise. Already started. I call it 1.7 as 7 is just after 6 ;) Piotras --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
