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

Shared IWTemp?

PaulD

I'm working with a team that currently relocated their \IWTemp diectory to a shared drive and now they are all using the exact same IWTemp directory. Is this supported? Has any one seen this used and if so were there any issues with it? Any info/helpful comments are welcome.

Find more posts tagged with

Comments

nipper

I think that is a bad idea. If you peruse the structure, you wil see some potential for
conflicts (say 2 people edit the same file). Not super likely but it could be a pain in 8 months
when it happens and you are trying to figure it out.

Andy

iwovGraduate

If you really want to share the TS filesystem, why not share /IWServer of TS directly ?
It has its drawbacks as already mentioned earlier in the thread.

PaulD

Interesting you mention 8 months -- seems they've been doing this for almost that long. Also, it they are complaining about files they haven't touched showing up as edited in their launchpad(s).

btw, we have TS552 on AIX

nipper

Also, it they are complaining about files they haven't touched showing up as edited in their launchpad(s).

That is a minor issue compared to what could happen.

Samir's idea is a good one if you have Samba running. Otherwise make the users use different IW-TEMP

TFG

I thought IWTemp was exactly what it implied, a temporary copy of a file while it is being edited by a user that has it locked. Use of a shared repository of files bypasses TeamSite's security and locking and invalidates the whole business purpose of a Content Management system, controlling the collaborative development of content. Sharing the IWTemp directories allows multiple authors to modify the same content without any control of conflicts or concurrent development.

Or am I missing something?

info.rptdesign

iwovGraduate

I am not sure what you are implying here. Your understanding on IWTemp is correct though.

If you want your (multiple) authors to modify (the same) content without any control of conflicts, locks, etc., why use TS or even any version control in the first place ? It defeats the purpose.

PaulD

Ok, all points taken. Then what I need to know definitively is if this supported by Interwoven. Anyone?

Migrateduser

The IWTemp directory should be treated as opaque.

Sharing it, manual changes to it, etc is not a good idea.

The only manual modification that is ok is to quit your browser and
remove the entire dir, in the unlikely event it should become corrupt.

Jason Heirtzler
Interwoven Engineering

TFG

Is there any way to either force IWTemp to the C: drive, or force that the IWTemp file is deleted on upload? That way we can prevent users from using IWTemp this way.

PaulD

Ok, the question is HOW do we force the use of a different IWTemp location (say.. C:\IWTemp)? Is this server configuration or business policy? Or something else?

Migrateduser

If you mean the temporary launchpad location, that is set up per user.

In CCPro,
if you change the view to "My local Files"
you will see a "settings" button on the right side of the display.

if you click on it, it shows you the Temp file directory under the "general" tab.

hth,

lissa