Link Issue #2
Peter Zechmeister <[email protected]>
| Newsgroups | gmane.comp.cms.zms.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi ZMS-Developers,
Issue #2:
Our site is reachable (internal) with the url i.e.
www2.jku.at/content/e123/e234
Subsites (Sub-ZMSs) have urls i.e.
www2.jku.at/SubsiteId/content/e1/e2/e3
Someone is working under i.e. www2.jku.at/subsite/manage_main
When someone sets a link from one subsite to another, the linkstring is
i.e.: {$Kinderbuero@e3055} and it works
When setting a link from a subsite to a page of the top ZMS, the
linkstring is i.e.: {$@content/e363} which obviously can not work and
gets marked as broken after saving: {$__@content/e363__}
So we have also a testdomain which points to the same ZMS-setup whithout
Apache-rewriting which works with the full zope-path. I.e.
zopev.jku.at/JKU_Site/JKU/subsite. Where the top ZMS is
zopev.jku.at/JKU_Site/JKU/content and one sub-ZMS is i.e.
zopev.jku.at/JKU_Site/JKU/subsite/content.
If setting a link under this path from a subsite-ZMS to a page of the
top-ZMS the linkstring is i.e.: {$JKU@e363} and this one works.
But this is bad. We want our editors to work under the common url
www2.jku.at/subsite/ where they have only to put 'manage_main' at the
end to get to their interface.
Why doesn't this work? I think, there should be a lot of implementations
with a similar setup?
Regards
PeterZ