Hi,
How do we remove "file_source" directory as the prefix from the resolved inline links?
thanks,
Chinmay
Chinmay,
Is this on the mgmt stage? If so, then you will need to set “useCDAViewer=false” in the vgn-ext-templating generic resource for the mgmt stage, push the changes, run cfgsync if necessary. Then stop the mgmt stage appserver, delete the cache and start the mgmt stage appserver.
Thanks,
Bill
From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]Sent: Tuesday, July 31, 2012 9:51 AMTo: eLink RecipientSubject: Resolved inline links
Resolved inline links
Posted bychinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 07-31-2012 10:47
[To post a comment, use the normal reply function]
Forum:
Discussion Group - Web Experience Management
Content Server:
Knowledge Center
eLink : Resolved inline linksResolved inline links Posted by chinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 07-31-2012 10:47 Hi,How do we remove "file_source" directory as the prefix from the resolved inline links?thanks,Chinmay[To post a comment, use the normal reply function]Forum: Discussion Group - Web Experience ManagementContent Server: Knowledge Center
Thanks for the responses. Yes, we are on the 8.1 platform.
Ideally, we want to have the same resolved url for inline file links. For mgmt stage, it is putting /file_source as the prefix.
For delivery stage, we've set the URL_PATH_PREFIX to empty string, but even then it is prefixing a '/' so our inline links have 2 slashes like //placmenent_path
What do we need to do so that resolved link is just /pacement_path on both preview and delivery stage?
thanks
eLink : Re Resolved inline linksRe Resolved inline links Posted by chinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 08-02-2012 12:44 Hi,Thanks for the responses. Yes, we are on the 8.1 platform.Ideally, we want to have the same resolved url for inline file links. For mgmt stage, it is putting /file_source as the prefix. For delivery stage, we've set the URL_PATH_PREFIX to empty string, but even then it is prefixing a '/' so our inline links have 2 slashes like //placmenent_pathWhat do we need to do so that resolved link is just /pacement_path on both preview and delivery stage?thanksChinmay[To post a comment, use the normal reply function]Topic: Resolved inline linksForum: Discussion Group - Web Experience ManagementContent Server: Knowledge Center
Thanks. Can you provide some details on what the bug was?
The bug was exactly what you observed: when defining a URL path prefix value such as "/" the system was building links starting with "//".
Same problem if one was defining any path ending with a slash: "/images/"
-m
From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]Sent: Thursday, August 02, 2012 8:03 PMTo: eLink RecipientSubject: Re Re Resolved inline links
Re Re Resolved inline links
Posted bychinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 08-02-2012 14:01
Topic: