VCM 8 sp1 Inline Link Context

William_Thayer

Anyone know how to change the context from vgn-ext-templating, to anything else in ePhox Inline Link widget?

Thanks in Advance!

Will

Find more posts tagged with

Comments

Mario_DAnna

The context should be hardcoded. If you have deployed the vgn-ext-templating under a different context such as /cds you should define a permanent redirect to all pages to /vgn-ext-templating/* to /cds/*. I don't have the code in front of me but I think that a search and replace of /vgn-ext-templating in the ephox inlink code might break the parser.
M

From: eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com>
To: eLink Recipient <devnull@elinkkc.opentext.com>
Sent: Fri Mar 04 06:45:37 2011
Subject: VCM 8 sp1 Inline Link Context

VCM 8 sp1 Inline Link Context

Posted bythayerw@avalonconsult.com (Thayer, William)On 2011/03/04 00:41

Anyone know how to change the context from vgn-ext-templating, to anything else in ePhox Inline Link widget?Thanks in Advance!Will

[To post a comment, use the normal reply function]
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

William_Thayer

This is an interesting answer, yes - I was thinking about using proxies to redirect to our Context say /company instead of /vgn-ext-templating.

Within lddDispatcher.jsp and ldfDispatcher.jsp, "/vgn-ext-templating" is Hardcoded. But within the distributed examples - say CPSInlineLinkAndImageBuilder, there's a line that gets the context with

TemplatingConstants.REQUEST_CONTEXT_VGNEXTTEMPLATING

I thought, we might be able to change the above code points. OR, I think maybe in the configConsole - you can change the properties on

Vignette Content Delivery Services -> Content Management Stage
-> Resources -> Generic -> VgnExtLinks

There's a lot of properties there, and wondered if we could set context there.

Mario_DAnna

The problem might be the parser which might be unable to understand the link. So the link might be built correctly but then it might not been recognized when you edit it.
So you can attempt the exercise of modifying the inlink code with a global search and replace but I won't guarantee that everything will work afterwords. If you give it a try let me know and please, for your next project do not change the vgn-ext-templating context....
Ciao
Mario

From: eLink Entry: Vignette V7 and V8 Web Content Management <v7webcontentmanagement@elinkkc.opentext.com>
To: eLink Recipient <devnull@elinkkc.opentext.com>
Sent: Fri Mar 04 18:38:35 2011
Subject: Re VCM 8 sp1 Inline Link Context

Re VCM 8 sp1 Inline Link Context

Posted bythayerw@avalonconsult.com (Thayer, William)On 2011/03/04 12:33

This is an interesting answer, yes - I was thinking about using proxies to redirect to our Context say /company instead of /vgn-ext-templating.Within lddDispatcher.jsp and ldfDispatcher.jsp, "/vgn-ext-templating" is Hardcoded. But within the distributed examples - say CPSInlineLinkAndImageBuilder, there's a line that gets the context withTemplatingConstants.REQUEST_CONTEXT_VGNEXTTEMPLATINGI thought, we might be able to change the above code points. OR, I think maybe in the configConsole - you can change the properties on Vignette Content Delivery Services -> Content Management Stage
-> Resources -> Generic -> VgnExtLinksThere's a lot of properties there, and wondered if we could set context there.

[To post a comment, use the normal reply function]
Topic:	VCM 8 sp1 Inline Link Context
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

William_Thayer

Actually this is an existing "Context" that VPS enabled in 2006, on a 7.3 implementation. We're trying to recreate in v8. : )

I think you are right about the parser and I have tried to use the scheme they used in 7.3. Only problem is that it's not saved to the INLINK table.

I'll take a look at the parser, thank YOU for the direction.

Will