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; } } }

6.1 CGI Problems

jimk351c

I have discovered a problem with my CGI callouts while integrating from 5.0 to 6.1. Whenever I try to open or write to a DCR using a path determined by $cgi->{form}{iw_dcr_vpath}, I get an error of:

"Couldn't open //sun24/default/main/loc-al/WORKAREA/Content/templatedata/content/subject/data/aa/aa_karamanis_subj.dcr:
No such file or directory"

If I hard code the path leaving off the server name like this:

'/default/main/loc-al/WORKAREA/Content/templatedata/content/subject/data/aa/aa_karamanis_subj.dcr'

it works fine.

This same code works fine on a 5.0 implementation. Any ideas?

TIA.

Senior IT Specialist, The Library Of Congress
jika@loc.gov

Find more posts tagged with

Comments

brandon1

Yes,
add a regular expression to strip out the server name at the beginning.

Current Project: TS 6.1
Environment: Solaris

jimk351c

I have no problem doing that, but is there a mis-configuration on my 6.1 box leading to the problem? Or, is this just how CGI works in 6.1?

Thanks.

Senior IT Specialist, The Library Of Congress
jika@loc.gov

brandon1

It is not a miss configuration, it is just a quirk added by Interwoven, I am sure it has an explanation but I do not know what the explanation is.

Current Project: TS 6.1
Environment: Solaris

jimk351c

Thanks!

Senior IT Specialist, The Library Of Congress
jika@loc.gov

nipper

>It is not a miss configuration, it is just a quirk added by Interwoven

It is not a quirk. It is an undocumented feature.

brandon1

oops , sorry I forgot

quirk => free
undocumented feature => $$$$$

Current Project: TS 6.1
Environment: Solaris

gzevin

the 'new' vpath is everywhere, staring with the CC PRO lttle vpath field.

and, I think in the upgrade guide it was mentioned somewhere...

actually - if anyone from IWOVcould explain as to why this server name was introduced, I'll be really grateful. I doubt this is a first step in having a multiserver (distributed) TeamSite.. in addition to muliti-store TeamSite

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

cliff1

Greg is on target as to why the ContentCenter webapp tries to consistently use fully qualified vpaths. At some point in the future, we hope to be able to attach to multiple different teamsite servers. This is also why the topmost node in the branch navigation tree (in CCPro) is the servername.

The definition of a valid vpath has always allowed for the //servername at the beginning. A vpath and the filesystem path (directory path) are not defined to be equal. The vapth "/default/mail/mybranch/myworkara/foo.txt" is a correct vpath for Solaris and Windows, even though on windows the "directory path" will generally have a drive letter (like y Smiley Happy

and the slashes will be reversed. Likewise a vpath that begins with //server has always been valid. Please note, the servername can also be a fully qualified server name (server.domain) or an IP address. So //10.192.4.213/mystore/main is valid.

At the risk of being flamed, I will submit that a program that does not handle vpath's correctly has programming errors. If the API says that it returns a URL, consumers of the API need to handle URLs according to the spec, not based on a particular style of URLs that have been witnessed. I'm not throwing stones because some of our codebase had vpath bugs that had to be fixed.

For reference, here is a snippet from the 5.5 CLT Guide that talks about vpaths (I could not find the 4.x docs, but I think it has the same definition):

Page 15
Version Paths
Most CLTs require that you use a version path (vpath) to specify the location of a branch,
workarea, staging area, edition, file, or directory in TeamSite. Vpaths are only used for items
within TeamSite; all other files (for example, configuration files) must be specified with a
directory path (see page 18). Vpaths have the following form:
To specify a server:
//servername
For example, the default vpath for the TeamSite server is:
//IWSERVER
Overview of CLTs and Command Triggers
16 TeamSite Command-Line Tools
To specify an archive:
//servername/archivename
For example, the default vpath for the TeamSite archive is:
//IWSERVER/default
To specify a branch or sub-branch:
//servername/archivename{[/branchname]+}
//servername/archivename{[/branchname]+}/subbranchname
For example, the default vpath for the main branch is:
//IWSERVER/default/main
The vpath for a sub-branch named dev off of the main branch would be:
//IWSERVER/default/main/dev
To specify an edition:
//servername/archivename{[/branchname]+}/EDITION/editionname
For example, the default vpath for the initial edition on the main branch is:
//IWSERVER/default/main/EDITION/INITIAL
The name of an edition on the subbranch dev would be:
//IWSERVER/default/main/dev/EDITION/ed_0001
Before Using CLTs
To specify a workarea:
//servername/archivename{[/branchname]+}/WORKAREA/workareaname
For example, the vpath for a workarea named eng on the main branch would be:
//IWSERVER/default/main/WORKAREA/eng
The vpath for a workarea named qa on the sub-branch dev would be:
//IWSERVER/default/main/dev/WORKAREA/qa
To specify an individual file within a workarea:
//servername/archivename{[/branchname]+}/WORKAREA/workareaname/
directory-pathname/filename
For example, the vpath for a file named logo.gif in the directory /htdocs/gifs in
workarea eng on sub-branch dev would be:
//IWSERVER/default/main/dev/WORKAREA/eng/htdocs/gifs/log0o.gif