Custom cgi script not working in 6.7

We just upgraded to 6.7 and our custom cgi deployment script is no longer working. We get the error message that the DCR that we're tying to deploy is not a valid file.

The error message appears in the CGI file:

sub showerrors {
my $errordcr;
foreach $errordcr (@errordcrs) {
print "
$errordcr is a directory or unkown data type, only plain dcrs and files in files directory can be immediately deployed.";
}
}

and here's where the value for $errodcr is defined in the cgi file:

foreach $dcr (@dcrs) {
if (!(($dcr =~ /\/templatedata\// || $dcr =~ /\/files\// || $dcr =~ /\/subs\//) && (-e $dcr) && (-f $dcr))) {
$filetest=0;
push @errordcrs, $dcr;

So anything in the templatedata, files or subs directory should be a valid file. Does anyone know if something changed in Teamsite 6.7 that would break this script? Thanks.

Find more posts tagged with

Comments

nipper

What rev of TS did you upgrade from ?

Can you include the error itself so one can see why it failed your (rather ugly) regex ?

JoeS

We just upgraded from TeamSite 6.5.0 Service Pack 1.

Here's the actual error:

//comcmd1.mfs.com/default/main/mfs/WORKAREA/mfsemc/templatedata/internet/article/data/sales_tools/aa_complete_investor is a directory or unkown data type, only plain dcrs and files in files directory can be immediately deployed.

The only variable that has changed is the server name: comcmd1.mfs.com

Thanks.

nipper

Put some more debugging statements in. Either the regex is incorrect (but it looks fine) or your -e or -f are failing. I suspect one of those, and probably because the share is not available to the user running. You may want to output the $USER environment variable as well.

Also to make your code more readable you can use something like this:

if ($dcr =~ m|/templatedata/|) instead of /\/templatedata\//

I suspect you are having an impersonation issue.

Frederik

Here's the actual error:

//comcmd1.mfs.com/default/main/mfs/WORKAREA/mfsemc/templatedata/internet/article/data/sales_tools/aa_complete_investor is a directory or unkown data type, only plain dcrs and files in files directory can be immediately deployed.

well, the error is right there under your nose.

The path you are trying to test (-e $dcr && -f $dcr) is a VPATH *with* the server prefix. As such, that is not a legitimate FILESYSTEM path.

Drop off the

//server_name

and (unless you really know what you're doing) you probably wanna stick a

/.iwmnt

to the front of the path. (this is assuming you're on Unix)

=>

/.iwmnt/default/main/mfs/WORKAREA/mfsemc/templatedata/internet/article/data/sales_tools/aa_complete_investor

Interwoven has been messing with the syntax of (V)PATHs for some time now... each release brings a little change here and there. And (on Unix) the way that they create a symbolic link from /default -> /iwmnt/default just helps to confuse people as to what is a VPATH and what is a proper filesystem path.

JoeS

Thanks Frederik. That did turn out to be the issue.

I replaced the following line in my script to get it to work in 6.7:

$vpath =~ s/(\/\/\w*)(\/\w*)/\/.iwmnt$2/;

to:

$vpath =~ s|(//[^/]+)?(/\w*)|/.iwmnt$2|;

gzevin

Interwoven has been messing with the syntax of (V)PATHs for some time now... each release brings a little change here and there. And (on Unix) the way that they create a symbolic link from /default -> /iwmnt/default just helps to confuse people as to what is a VPATH and what is a proper filesystem path.

they are not 'messing', but rather getting close to some bigger 'picture' where there will be a distributed TeamSite....

But I agree, 'gifts from IWOV' like that are not nice, even though it's not something I am terribly surprised about.

edit_2.tiff

run_2.tiff

run_pdf.tiff