nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

'Content Items' of a space: how to only show &quot

hbf

Hi!

How can I tell the Web Client to only show the children of the space's "cm:contains" association?

It seems that when you click on a space in the Web Client and the space has additional child-associations (from a custom model) then not only the children of "cm:contains" but also the children of the custom child-associations are shown. Is there a way to tell the Web Client to just show "cm:contains"?

Many thanks,
Kaspar

P.S. The behaviour of the Web Client is actually a little strange: When I create children for my space's custom child-association, they do not appear immediately in the Web Client's "Content Items" view of my space. But after clicking around a little, they eventually show up there, together with the "cm:contains" children.

Find more posts tagged with

Comments

kevinr

This is a known issue with the FileFolderService - as since 2.0 it now uses Lucene to retrieve folder children rather than the nodeservice directly (for performance). Hopefully we will have a solution to restrict the child association type ASAP.

The other issue is also due to Lucene indexes, they are not always as up-to-date as using the nodeservice directly.

Kevin

kevinr

@cm\\:name:\"._*\"

might work, but i haven't tried it

hbf

The other issue is also due to Lucene indexes, they are not always as up-to-date as using the nodeservice directly.

Can you clarify on this, please? I thought Alfresco uses transactions. Is this a caching issue of the Web Client or is only querying the nodeervice transaction-safe, and Lucene not?

Thanks,
Kaspar

kevinr

Yes we use transactions - but because of that, if one user indexes documents, the other user will not see the results until after the first user transaction is completed.

If you are talking about a single user instance, then it sounds more like a browser caching issue - are you using IE with the default cache settings?

Kevin

hbf

Dear Kevin,

Thanks a lot for the clarification. If it's a browser isssue (Ã¢â‚¬â€œ I am using Safari Ã¢â‚¬â€œ) it is not a problem for me. The sentence

The other issue is also due to Lucene indexes, they are not always as up-to-date as using the nodeservice directly.

just sounded as if Lucene and NodeService could give contradicting search results. If that were the case, I would have wanted to know. But glad to here that both are transaction-safe (up to properties that are not indexed atomically, of course).

Thanks,
Kaspar