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

Pathing Issue?

InterDevelop

We recently migrated from a Unix/Solaris (TS 5.5) environment to a new Win 2003 (TS 6.5) environment. Most items have ported over "nicely"... However, the biggest challeng is reactivating .tpl files that relied on Unix paths & trying to upgrade a windows path... Am I missing something here?

TS 5.5 Old Environment:
# Add the new custom location
use lib "/usr/local/utils/teamsite/modules";
use Utils::XYZUtils;

TS 6.5 New Environment (Win 2003):
# Add the new custom location
use lib "F:/Program Files/Interwoven/TeamSite/ts_utils/legacy/utils/modules";
use Utils::XYZUtils;

I'm hoping this is not a "space in the path" issue for windows.

Thanks in advance for the help,

Jeff Baker
InterDevelop.com

Find more posts tagged with

Comments

nipper

you seem to be missing an " at the begining of the use statement

Adam Stoller

[... migrated from Unix/Solaris (TS 5.5) to Win 2003 (TS 6.5)....]

TS 5.5 Old Environment:
# Add the new custom location
use lib "/usr/local/utils/teamsite/modules";
use Utils::XYZUtils;
TS 6.5 New Environment (Win 2003):
# Add the new custom location
use lib "F:/Program Files/Interwoven/TeamSite/ts_utils/legacy/utils/modules";
use Utils::XYZUtils;
I'm hoping this is not a "space in the path" issue for windows.

Well - it is likely that you might be running into a "space in the path" issue - as it is highly recommended that you do not install TeamSite in "Program Files".

In addition, now that you're using 6.5 - you should place your custom modules in

iw-home/iw-perl/site/lib/

which is already on the

@INC

list for iwperl and then you don't need the

use lib

line at all.

iw-home/iw-perl/site/lib/

has been declared by Interwoven as the location for custom modules that will not be modified by upgrades and service packs. The only exception for this so far is for custom PT tags which currently only work if placed in

iw-home/iw-perl/vendor/lib/

- but there's a bug report filed on this ([post]74624[/post])