AW: Breaking links [1 Attachment]
"Dr. Frank Hoffmann" <[email protected]>
| Newsgroups | gmane.comp.cms.zms.devel |
|---|---|
| Message-ID | <53ECD362EE454E83A4C4F920F5EE3E39@hal1> |
Hi, is there an apache "in between"? Please try the 'Misc.-Option' "Coherent URL" (screen shot). Best regards fh -----Ursprüngliche Nachricht----- Von: [email protected] Gesendet: Donnerstag, 28. Mai 2009 16:49 An: [email protected] Betreff: [zms-developers] Breaking links Hi, there are some wired things with breaking links. I have this structure i.e.: TopZMS - e1 recursive embedding link to e11 (Sub ZMS) - e2 Text + SubZMS ..- e11 Folder ....- e21 Text ..- e12 Something ..- e13 Text 1) I move into TopZMS Backend. There I have the sub-ZMSs listed below. Here is the first strange thing: The links to the sub-ZMSs here look like that: http://www.xyz.at/zopepath/TopZMS/content/SubZMS/content/manage_main... There is 'content' in the path two times! I guess, the first occurence of 'content' is unnecessary - if not even bad as shown next. 2) I click on a link to SubZMS and get there. The url line in the Browser shows 'content' two times as expected. 3) I move into e13-Textarea, mark some text and klick on the link-symbol (the small globe). Doing point 3 breakes the link whithin e1. The trigger here, is the unnecessary 'content' within the path. When moving though breadcrumbs the first 'content' disappears from the actual url. After repairing e1 and trying it again with an 'one content url' it works fine. But I think, the double 'content' in the sub-ZMS-Links are more a cosmetically problem. Sometimes links break in situations without two 'content' strings too. Afaik, the real problem lies somewhere in ZReferableItem.getRefObjPath, PathHandler.getVirtualRootPhysicalPath or ObjAttrs._getObjAttrValue. These script should be more robust against wired urls. But I am not as familiar with this code to fix this without unwanted side effects. Can you please give a short-term advice how to stop breaking links like that? Regards PeterZ ZMS 2.11.1-51 (Build #131k)