Hello
okay, we'll be patient! :)
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?
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?
Pascal
----------------------------------------------------------------
simplicity gmbh
ringstrasse 39 www.simple.ch tel: +41 61 721 50 40
ch-4106 therwil [EMAIL PROTECTED] fax: +41 61 721 50 41
----------------------------------------------------------------
> --- reply to ---
Von: [EMAIL PROTECTED]
Gesendet: Mittwoch, 11. August 2004, 12:47
An: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Betreff: [midgard-user] MidCOM component devleopment
tnn> -----BEGIN PGP SIGNED MESSAGE-----
tnn> Hash: SHA1
tnn> Hi,
tnn> - --- On 11.08.04 11:41 (+0200) Pascal Mayer wrote:
>> But I didn't clearly describe which "NAP" I am referring to :)
>>
>> tnn> NAP does distinguish between Admin- and Site-URLs. Either of the
>> tnn> two can be NULL, indicating the inavailability of a given leaf in
>> tnn> the corresponding mode. This is true only for leaves, not for
>> tnn> nodes. A leafe retrival might look like this:
>>
>> The taviewer component as an example has different "action-links"
>> depending on the current object (leaf/node) and current view.
>>
>> "View, Delete, Approve, Create Article, Settings"
>> or
>> "Edit, Delete, Approve, Create Article, Settings"
>> or just
>> "Settings"
>> ...
>>
>> Are those links/actions retrievable from the component? It seems that
>> they are hard-coded inside the styles of the components...?
tnn> Unfortunalety, they are. The NAP subsystem does not yet support different
tnn> links into the AIS per leaf. I have some ideas how to implement this
tnn> though, as it is on my todo list, but it involves rather extensive changes
tnn> on the NAP subsystem, as I want to integrate a generic metadata handler
tnn> (for things like approval or hiding of elements), which is not trivial. I
tnn> haven't found the spare time yet to implement this, and I can't give you
tnn> an ETA right now, as the stuff mentioned in mRFC 0006 (Midgard Website,
tnn> Community, Development) is on top of my priority list right now.
tnn> Live long and prosper!
tnn> Torben Nehmer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
