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

how to get workarea path??

rodigz

my $workarea_path = $ENV{"IW_WORKAREA"};

is this correct? Shows blank.

Find more posts tagged with

Comments

nipper

in the context of what ?

That works if you have an environment variable set, like maybe for a workflow.

rodigz

in the presentation template (tpl)

Migrateduser

I think you are confusing the documentation for inlines with that for PTs. Look at the iwpt_get_ofile_name() function. You can pull the area vpath from that.

rodigz

I need to generate the file in different location.
I want to get path.
e.g.
/iwmnt/default/main/TestBranch/WORKAREA/test/

ISCBorisB

I need to generate the file in different location.
I want to get path.
e.g.
/iwmnt/default/main/TestBranch/WORKAREA/test/

From PT try
(my $workarea_path = iwpt_get_flag_param('-iw_include-location')) =~ s|\\|/|g;

rodigz

great..i'm getting this now but how come there a period infront of iwmnt?
/.iwmnt/default/main/TestBranch/WORKAREA/test/

ISCBorisB

great..i'm getting this now but how come there a period infront of iwmnt?
/.iwmnt/default/main/TestBranch/WORKAREA/test/

Check Admin Guide for UNIX. "/.iwmnt" is IWOV NFS mounting point without caching, "/iwmnt" - with it.
If you need vpath you can drop prefix and start from (in your case) /default.
If you need NFS File you normally use /iwmnt (cached). Non-cached mount shoud be used in special cases only

Frederik

Non-cached mount shoud be used in special cases only

Actually, using cached mount is risky if you don't know what you're doing! Especially if you use map_secondary_to_primary_gid=yes in iw.cfg and are working with (somewhat) strict permissions on your files.

Do a search with these keywords: cached mount unix groups

ISCBorisB

Actually, using cached mount is risky if you don't know what you're doing! Especially if you use map_secondary_to_primary_gid=yes in iw.cfg and are working with (somewhat) strict permissions on your files.

Do a search with these keywords: cached mount unix groups

Agreed. Actually, last time I've tried to use "secondary_to_primary" trick was 4 years ago with 4.5.
In my particular case the cure happened to be much worse than a disease and we switched it back immediately.

Frederik

OFF-TOPIC (Re: map_secondary_to_primary_gid)

[INDENT]

In my particular case the cure happened to be much worse than a disease and we switched it back immediately.

It works fine here.... since 2,5 years. (Sorry, I wouldn't want the casual reader conclude that it's a bad thing ;-) ) But it definitely is something that you can't just change in the iw.cfg without having a thorough understanding of how it works, and what effect it has on your scripts (e.g. using cached mount is a no-no). It's impact can be very counter-intuitive for a while... [/INDENT]

ISCBorisB

Sorry, I wouldn't want the casual reader conclude that it's a bad thing

Please...I beleive i clarified "In my particular case". It had nothing to do to being "good/bad", it's just a tool.

The reason was that (subscription) publications had very serious legal and financial exposure.
Therefore Client had extra authorization and monitoring systems. Sure enough both went down the drain with secondary mapping

Frederik

OFF-TOPIC (Re: map_secondary_to_primary_gid)
[INDENT]

Please...I beleive i clarified "In my particular case". It had nothing to do to being "good/bad", it's just a tool.

Sorry to misrepresent your words... While I had read the "in my particular case", I didn't want to assume every one would ;-)
[/INDENT]