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

Problem while Publishing....

eddie1

Our client is facing a weird problem in their production TS Server.

They login as user 'scb_pub' (editor)
Click on the branch from which the edition is to be cut out.
Execute the 'Publish' command.
Success !

But when the repeat the same process.... they get a permission denied....
'scb_pub(editor) is not permitted to publish the STAGING AREA owned by s_prod'

Where 's_prod' is the branch administrator. 'scb_pub' is in the share group for the branch and there arent any permission issues with this user.

Any ideas ?

OS: Solaris 2.8
TeamSite version: 552

Thanks !

IWOV Consultant

Find more posts tagged with

Comments

eddie1

still hopeful for some ideas ............... : )

Migrateduser

Could you post the permissions for the branch EDITION & STAGING directories; the groups that contain either user; and the users' primary group(s)?

eddie1

The branch name is scb2bex_prod and following are the folders in it:
dr-xr-xr-x 38 s_prod scb2bex_prod 512 Dec 10 18:58 EDITION
dr-xr-xr-x 5 s_prod scb2bex_prod 512 Aug 10 17:49 STAGING
dr-xr-xr-x 9 s_prod scb2bex_prod 512 Jul 10 10:11 WORKAREA

The user scb_pub (which has an editor role ) belongs to group 'scb2bex_prod' created on the OS. I have verified this by looking at the /etc/group.

Is there anything else i should look into as well ?

Thanks !

IWOV Consultant

13adam13

Can't tell from your explanation of the problem if this applies or not. I noticed that if you publish a branch, and then immediately try to publish the same branch again without performing any other actions within TeamSite, the GUI can get confused about which branch you are trying to act upon, and my experience has been that it will try to publish either the main branch or the parent branch of the current.
If this is the problem that you are describing, it is easily remedied by selecting the branch name again before trying to republish.

Otherwise, I have never experienced this problem, so I hope that was it. Smiley Happy

--Adam Wilson
Senior Programmer

eddie1

Hi,

Is there any other thing besides checking the folder permission and making sure that the user has rights to write into it that would keep him from creating the edition ?

13adam13

There are preferences that you can set to keep the editors from publishing globaly. I am not aware of anything else that might be causing you problems.

Have you gone to Interwoven support on this one?

--Adam Wilson
Senior Programmer