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

Editor role cannot revert to previous version

Kevin Butcher

TS 6.7.2/Windows 2003 SP2

For some reason even though the Editor role explicitly gives the permission to Revert files, my users are getting permission errors when trying to do so on files that are "Marked for Delete". They can delete it and write to it, but they can't Revert to the previous version even if they are the one who deleted the file.

They are being added to the branch as Editors using the "iweveryone" group so they should all be Editors on the branch with permisson to Revert files. If I add the user explicitly as an Editor it still doesn't work.

The only thing that seems to fix this is to add them as Administrator but I'm not considering that as an option at this point.

Find more posts tagged with

Comments

ChrisCiesielski

Hi,

Have managed to resolve this issue?

Thanks,
Chris

Kevin Butcher

No it's currently still a problem.

Rick Poulin

What you can do is Edit > Undo Changes. That, or Get Latest on that file. Once the file is restored, then you can access the past versions.

Kevin Butcher

I'll have an existing user try this and let you know if it worked.

Slype

We were running into the same issue and even though the editor role had the revert ability enabled, it was greyed out and was causing us issues.

Afters scouring DevNet, I could not find anything... A compatriot of mine thought to use the customer service area and search the "solutions" are on a lark and lo and behold, it actually had a fix for it.

You can read it for yourself but I've posted the answer here as I know that HP/Interwoven/Autonomy make it **** to try and get access to that info..

I'm not sure of any repercussions of us not having that setting but hopefully we will be upgrading to 7.2.1 soon and (fingers crossed) maybe it's fixed.

Apologies for the weird code sections, for some reason, I had to take out the opening brackets for all the lines. I don't have time to figure it out as I have stuff to do. Just thought I would share though.

Best wishes...
---------------------------------------------------------

Permission denied trying to execute the command iw.ccpro.undelete - Editor can't 'Restore'

Product: Teamsite - Core Version: 6.7.2 SP2
Created: 07/12/2010 Category:

Problem:

Permission denied trying to execute the command iw.ccpro.undelete - Editor can't 'Restore'

Solution:

Edit the iw-home/private/etc/userops.xml file. You will need to

comment out the

role-based-check value="HasFileWritePermission"/>

entry for the “RevertFile” operation alone changing from:

operation id="RevertFile" display-name="Revert File" description="Revert File">
    category id="FilesFormsAndFolders"/>
    object-type value="file"/>
    object-type value="hole"/>
    object-type value="symlink"/>
    required-check value="InWorkarea"/>
    role-based-check value="IsWorkareaMember"/>
    role-based-check value="HasFileWritePermission"/>
  /operation>

To:

operation id="RevertFile" display-name="Revert File" description="Revert File">
    category id="FilesFormsAndFolders"/>
    object-type value="file"/>
    object-type value="hole"/>
    object-type value="symlink"/>
    required-check value="InWorkarea"/>
    role-based-check value="IsWorkareaMember"/>
    !--
role-based-check value="HasFileWritePermission"/>
    -->

Please restart TeamSite server for the changes to be reflected.

currentReport.pdf

ModulplanHochformat.rptdesign

sampleData.csv

Migrateduser

Does this solution work in 7.2.1? That is a great find - I have a support case opened for this same exact issue and they are trying to tell me it's a designed "feature" to not allow anyone with role beneath Admin revert a deleted file. I called BS on them, but still they haven't come back with this (already documented) solution. Evidently I got the trainee support guy for this one...

Slype

Not sure... From what you are saying, I guess this is still an issue (feature - HA!) in 7.2.1. Smiley Sad

Thanks for the heads up - hope this fix resolves your issue.

Migrateduser

I will test out the solution in 7.2.1 (Linux) and update this thread. Thanks for posting it!

ISCBorisB

I will test out the solution in 7.2.1 (Linux) and update this thread. Thanks for posting it!

In case you need a Link to prove your BS conclusion - here it is...
(Although I admit, one has to be very green to claim that it's a *feature*)

Migrateduser

This worked in 7.2.1 as well. I will now school my support engineer...

Thanks again!