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

Changing file Permissions

lizn

Does anyone know if it's possible to change a windows file permssions (security) on a file/folder and not have the file show up as modified in Teamsite?

Find more posts tagged with

Comments

shanon

In reply to:

Does anyone know if it's possible to change a windows file permssions (security) on a file/folder and not have the file show up as modified in Teamsite?

if you can associate it with a submit event, then i'm pretty sure that you can assign permissions with the submit filtering. search the teamsite admin guide for "submit filtering" and/or "submit.cfg"

-shanon

lizn

We are assigning them with our submit.cfg, but needing to switch a permission from full access to read access so it modifies all the files. We'll have issues if all the files say they are modified when the only things that changes is a permissions. we submit all our files because some of them are actually modified and can't be pushed to our production

shanon

sorry , i'm not really understanding ... can you give me more specifics ?

-shanon

Adam Stoller

Any change to a file's (or directory's) attributes (permissions, access rights, etc) is a modification of the asset and will necessitate submitting the files so that the change can be recorded in the backing store.

That's the bad news.

The good news is that ever since 5.5.2 (and I believe improved in 6.x) the changes to attributes like this does not represent a complete new version of the asset which was modified. It used to be that a change to a files permission would create a copy of the file to be associated with the new permission. Now it is essentially like a reference pointer to the unchanged version of the file with a reference pointer to the new attributes. Far more efficient.

All that being said - you could probably write a script that compared the modified file in the workarea with the version of the file in staging. If the files are identical - you can submit it as an attribute modification. If the files differ - skip it, and the attribute changes will be picked up when the content modification is actually submitted.

Something like:use File::Compare;
my $branch = "/some/branch/path";
my $wa = "$branch/WORKAREA/some_workarea";
my $stg = "$branch/STAGING";

my @mod = grep { /^f\+/ }qx($iwhome/bin/iwlistmod $wa);
@mod = map { chomp; s/^f\+\s*//; $_} @mod;
foreach(@mod){
if (compare("$wa/$_", "$stg/$_") == 0){
# submit it - or store it in a list for a batch submit
}
}

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

lizn

When I use the above script it's telling me that the files are different even though the only thing different is a permission group. Any other ideas to get the compare to only look at the source?

Adam Stoller

I think I know what may be wrong - I forgot you were on Windows - try changing the code to:use File::Compare;
use TeamSite::Config;
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;
my $iwmount = TeamSite::Config::iwgetmount();
my $branch = "insert-branch-path-here";
my $wa = "$branch/WORKAREA/insert-workarea-name-here";
my $stg = "$branch/STAGING";

my @mod = grep { /^f\+/ }qx($iwhome/bin/iwlistmod $wa);
@mod = map { chomp; s/^f\+\s*//; $_} @mod;
foreach(@mod){
my $cmp = compare("$iwmount$wa/$_", "$iwmount$stg/$_");
if ($cmp == 0){
print "$_: files appear to be the same\n";
}
elsif ($cmp == 1) {
print "$_: files differ\n";
}
else {
print "$_: something went wrong?";
}
}

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

lizn

Thanks so much! That's exactly what I needed.