nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

issue with manual FURL feature

Shrishail_Kurundkar

Hello,

We are using VCM 7.6. One user had created a manual FURL CI with friendly name '/carfinance'. Using 'target URL' option, this FURL was supposed to point to a URL(/loans/car-loans/support) within our site. So on hitting www.site.com/carfinance , users should be taken to www.site.com/loans/car-loans/support page.

A channel with name 'carfinance' was present at path /Sites/<site-name>/Home path in VCM. So /carfinance FURL was pointing to this channel instead of /loans/car-loans/support (even though 'target URL' option was selected and not 'channel' in FURL CI). To avoid the conflict, we
unpublished this carfinance channel, deleted it and cleared cache. Now when we hit www.site.com/carfinance, we are getting 404 error. We also tried to use 'target channel' option and selected /site/Home/loans/car-loans/support channel. Still get 404 error.

This means the FURL is still pointing erroneously to a channel that does not exist. Do FURLs get cached somewhere in the system? How to get /carfinance FURL correctly point to relative URL /loans/car-loans/support ?

Thanks,
Shrishail

Find more posts tagged with

Comments

Shilpa Vodapalli

Hi Shrishail,

Yes, the FURL mapping isstored in the cache and reused.

For this cache to bemaintained and up to date, we need to properly setup the
"cluster.nodes" property in the VgnExtTemplating resource. In this,the FURL
application will act as another node of the DPM/DSM application. So, if you
have a site with FURL implemented in a server like:
http://furlserver:8080/furlsite

you'll need to setup:
cluster.nodes=http://furlserver:8080/vgn–ext–templating,http://furlserver:8080/furlsite

Please refer to Opentext ArticleNumber: 17552729 (link below) for more on this.

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=17552729&objAction=ArticleView&viewType=1

Thanks,
Shilpa

From: eLink Entry: Vignette V7 and V8 Web ContentManagement [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, June 02, 2010 11:25 AM
To: eLink Recipient
Subject: issue with manual FURL feature

issue with manual FURL feature

Posted by shrishail.k@tcs.com (Kurundkar, Shrishail) On 2010/06/02 01:53

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

Shrishail_Kurundkar

Hi Shilpa,

Thanks for your reply and KB link.

We have two sites - mysite1 and mysite2. Are you suggesting us to use following value in cluster.nodes, so that our problem with manual FURL CI will be solved? When we update any existing FURL, will the changes reflect immediately?

http://furlserver:8080/vgn–ext–templating,http://furlserver:8080/mysite1,http://furlserver:8080/mysite2

Please advise.

Regards,
Shrishail

Shilpa Vodapalli

Shrishail,

That’s correct, each FURL-enabled site’s context hasto be registered in the cluster.nodes parameter. With this setting in place, FURLis updated each time the object is changed.

Thanks,
Shilpa

Open Text Technologies IndiaPvt. Ltd.

From: eLink Entry: Vignette V7 and V8 Web ContentManagement [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, June 02, 2010 12:46 PM
To: eLink Recipient
Subject: issue with manual FURL feature

issue with manual FURL feature

Posted by shrishail.k@tcs.com (Kurundkar, Shrishail) On 2010/06/02 03:11

Hi Shilpa,

Thanks for your reply and KB link.

http://furlserver:8080/vgn–ext–templating,http://furlserver:8080/mysite1,http://furlserver:8080/mysite2

Please advise.

Regards,
Shrishail

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

image001.gif

Shrishail_Kurundkar

Hi Shilpa,

On adding "http://furlserver:8080/vgn–ext–templating,http://furlserver:8080/mysite1, http://furlserver:8080/mysite2" to cluster.nodes, the problem with manul FURL CI got resolved; but both the sites becamew very slow.

We removed site names from cluster nodes, and the performance of live site looks good now. In case any user changes any of the existing FURL CI's, then we may again face the same problem.

Any idea whether adding site names in cluster nodes properties slows down the site performance?

Thanks
Shrishail