29 Sep
2010
29 Sep
'10
11:32 p.m.
Hi!
Thomas Mortagne wrote:
I've not used this kind of references yet, but I guessed it must work as
it also exists global visibility for users. After all, a "type" of document.
What I don't see that clear is if there will be an "extra" system to
control the scope of visibility (for instance, being in a given subwiki
A, we only able to reference documents in B and C but not in D), or if
this will be controlled by trustees right assignments as in search.
Considering a
wiki farm as an excellent metaphor for "ecosystem" of
groups with crossed interests, it will is feasible to expect that cases
will arise where contents on an given subwiki would be welcome in
another one. I'm currently using a 2.4.1 XE/XEM installation. Provided
I'm I in a controller, should I be able to see all subwiki documents
when creating links in the WYSIWYG editor? Must I be able to see
documents in the controller or other subwikis when I am in a given
subwiki? Is there a way of set the scope of visibility?
Sergiu forgot to say that your use case is already covered and since a
long time: the real full reference of a document include the wiki
identifier as in "wikiid:Space:Page" and is supported everywhere you
manipulate document references:
- in a link: [[wiki1:Space.Page]] tagets the page
"Page" in space
"Space" and wiki "wiki1"
- in include macro: {{include document="wiki1:Space.Page"/}} include
the content of page "Page" in space "Space" and wiki
"wiki1" in your
page
etc.
As said in a previous message, I see some incongruences between the
actual pages and the pages offered by the create link window in the
WYSIWYG editor. Or, even Firefox hangs when I go to All Pages tab.
Search gives me results on any subwiki, but search within create a link
window, doesn't. We are on the go to update to 2.4.3, so perhaps I must
try again when the migration is done.
Hope this makes some sense for you.
Greetings,
Ricardo
--
Ricardo RodrÃguez
CTO
eBioTIC.
Life Sciences, Data Modeling and Information Management Systems