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.0 migration vpath and ceiling-dir

neski

We've testing a migration TS 5.5.2 SP3 -> TS 6.0. This is what we have done till now:

1. Installed a new TS 6.0 environment
2. Migrated the 5.5.2 default content store to a new content-store in TS 6.0 using iwmigrate
3. Converting users using iwidmap
4. Added data types to templating.cfg
5. Copied inline scripts in the new machine

Everything related seems to works ok. ACLs are Ok and content is migrated. But there are some strange behavior:

Every vpath posted to the inline scripts was in format "/default/main/... " in TS 5.5.2 but now is in format "//IWSERVER/default/main... " which force us to change the scripts.

The ceiling-dir attribute whitin a browser item in DCTs is not working as initial-dir. Ceiling-dir in TS5.5 also defined the initial-dir to look for files, so we didn't defined any initial-dir in our templates. Now it seems we need to change every datacapture to add an "initial-dir" attribute.

Maybe you know how can we work-around these two issues.

Thanks

Find more posts tagged with

Comments

Adam Stoller

The vpath issue is one I noticed with all my CGI scripts (apparently another non-backwards-compatible change that nobody thought to flag as significant?)

In Perl - I just do this (assuming you've already captured the value within $vpath):

$vpath =~ s|^//[^/]+/|/|;

Note: I ran into this in 6.0L - not sure if this was "fixed" in 6.1 (anyone know?)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

abackenr

a full vpath includes the server name at the start, and that's what we should be sending from now on. sorry for the incompatible change, but this won't be "fixed" by going back to partial vpaths. full vpaths are a good thing (especially if some day we do distributed or federated TS).

fish - thanks for posting the workaround.

ariel

staff engineer @ interwoven

Migrateduser

Wonderful. I guess I hadn't found this little gem yet. Which CGI scripts does this rear it's head in? cgitask scripts? Custom menu scripts? Can you give an example of a common usage of this - in other words, which standard parameters are we talking about?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

If you use a CGI script for a custom menu item - and you process the vpath form variable array - all entries begin with //server/archive/main/...

The "nice" thing about this is that [on Unix] you no longer have to worry about checking for both /iwmnt and /.iwmnt.

The "not-so-nice" thing about this is that you have to check all your code where you *assumed* you were getting something that could be used as a file system path (*) that now will no longer work as such.

(* there was a thread on this somewhere - that the symlink of /default to /iwmnt/default was a "bad" thing because [on Unix] this allowed people to use vpaths as file system paths when they really weren't the same thing )

The same thing applies to cgi-callout scripts in templating (though not in MDC since you can't get a handle on the file there - ARRRGH)

I don't believe this affects cgitask scripts or externaltask scripts in workflows (at least not yet) as the areavpath seems to still be the non-server-rooted vpath (i.e., "/default/main/...") - however, based on the previous statements this is something that could very well change in the not too distant future.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Sri

>The ceiling-dir attribute whitin a browser item in DCTs is not working as initial-dir. Ceiling-dir in TS5.5 also defined the initial-dir to look for files, so we didn't defined >any initial-dir in our templates. Now it seems we need to change every datacapture to add an "initial-dir" attribute.

where is the user taken first if the initial-dir is not set? Can you explain the probelm clearly?

Sri

neski

Thanks everybody for the answers, it's good to know how it's going towork the vpath from now, even if I'll need to check callouts and perl scripts ;-)

If the initial-dir is not set, the user is taken to the root dir within his workarea. This is the expected behavior, however, in TS 5.5.2 if only the ceiling-dir attribute was set, the user was taken to the "ceiling-dir" folder. Now it seems that both attributes need to be set in order to have it working properly.