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

What role property needed for New Node in Site Map?

Adam Stoller

Environment[indent]TS 7.2.1 on Linux CentOS 5.5[/indent]
Issue[indent]I recently assigned one of our customer TS Groups the role of "Site Manager" in
the content (/default/main/****) branch - on the assumption that that
would allow members of that group to add new Nodes to the site map to create
things like vanity urls.

However, they still see the New Node option as being grayed-out when they go
to the Site Map and right-click on one of the Primary node elements.

We don't want to make them all Masters - but I cannot figure out what role
property they're missing from the OOTB "Site Manager" role - or why that role
doesn't work for them.

Note: I ran a simple iwreset (no flags) after assigning the group to the role, and
the users have tried both browser refreshing and logging out and logging back
into TeamSite with no improvement.[/indent]Any ideas?

Find more posts tagged with

Comments

nipper

I was looking at the Role Details for Site Manager and it says edit sitemap.

Do they have normal edit access to the branch/workarea ?

nipper

Could the Sitemap be locked ?

nipper

FYI

I just ran a test myself. Could not get write access to the component guide sitemap but when I created a new site with that user I was able to change nodes without a problem.

I expect it is a permissions issue.

crosstabchart.rptdesign

Adam Stoller

I was looking at the Role Details for Site Manager and it says edit sitemap.

Do they have normal edit access to the branch/workarea ?

Yes, they have normal edit access in the branch / workarea

Could the Sitemap be locked ?

I don't think so, or at least I don't think that's the issue - I (as Master) could see the New Node option not grayed-out.

FYI

I just ran a test myself. Could not get write access to the component guide sitemap but when I created a new site with that user I was able to change nodes without a problem.

I expect it is a permissions issue.

Ah - yes, perhaps it's at the OS-level permissions - didn't think the check that. I'll check that tomorrow morning.

nipper

I don't think so, or at least I don't think that's the issue - I (as Master) could see the New Node option not grayed-out.

Well if you have new node access, you *may* own the lock. Maybe we can get someone to explain locking to you. Smiley Very Happy

Adam Stoller

Well if you have new node access, you *may* own the lock. Maybe we can get someone to explain locking to you.

That's the sort of response I'd expect from Smitty ;-)
I seriously doubt that I have the lock on anything in the SiteMap since I've not done anything in the SiteMap (or pretty much anywhere else within the branch - my focus on this project is administrative assistance) - however, it is conceivable that the I may be a member of the group that owns those files or just by mere fact of being a Master may enable the menu option for me.

Thus I'll check tomorrow morning to see whether that be the case ...

Adam Stoller

Well, I looked at the following files:

/default/main/branch/WORKAREA/wa/sites/*/default.sitemap

It doesn't look like a permissions thing, since every one of those files is protected 666 with a group ownership of iwEveryone.

Any other ideas?

nipper

That is normal. I assume you checked the Edit Sitemap ability in the role.

Try assigning a specific user to that role, just in case.

Adam Stoller

That is normal. I assume you checked the Edit Sitemap ability in the role.

It's the OOTB Site Manager role, and yes, I verified that was in there:

% iwroleadm all-operations | egrep -i "\.site"
iw.livesite.create.site
iw.livesite.edit.site
iw.livesite.edit.site.map
iw.livesite.webtrends.sitereports
% iwroleadm operations "Site Manager" | egrep -i "\.site"
iw.livesite.create.site
iw.livesite.edit.site
iw.livesite.edit.site.map
iw.livesite.webtrends.sitereports

Try assigning a specific user to that role, just in case

I truly don't think that's it:

% iwaccess all-permission-entries-of-user astoller Master
//ts-server/default/main/branch-name     Content Editor,Content Manager,Content Reviewer,Site Manager,admin
//ts-server/iwadmin/main/workflowModels        workflowUser
//ts-server/iwadmin/main/livesite/component    Site Manager
//ts-server/iwadmin/main/livesite/template     Site Manager
% iwaccess all-permission-entries-of-user another_user Non-Master
//ts-server/default/main/branch-name     Content Editor,Content Manager,Content Reviewer,Site Manager,admin
//ts-server/iwadmin/main/workflowModels        workflowUser
//ts-server/iwadmin/main/livesite/component    Site Manager
//ts-server/iwadmin/main/livesite/template     Site Manager

(Yes, those are custom roles shown there - I don't believe that has any bearing on this)
I have access to the New Node menu option, another_user does not.

Adam Stoller

FYI - to make things more interesting (perhaps) I now find that of the dozen-or-so sites defined in the Site Map tab, I have access to the Add Node option for all-but-one of them.

I cannot find any aspect of file system access rights within the branch/.../sites/* folders and files to explain this.

I had some interaction with Support, but due to things going on at the customer site I was unable to follow-through on their request for getting more data. Hopefully next week I'll be able to do some more tests... even better, get the issue resolved...

Adam Stoller

The answer to the question posed in the thread title is, I still believe, "Site Manager"

The answer to the problem being encountered was determined by me, on a whim - instead of looking at the site from the Site Map view and the permissions from the file system interface - I decided to look at the sites/site-name/ directory (in the Content tab of CCPro) and I noticed that those files that had the correct owner, and group, and permissions - were all marked as modified and locked ... i.e. they had not been submitted since the site was created and/or last modified and TeamSite was [correctly] protecting them from being modified by two people at the same time -- unfortunately there's nothing in the Site Map UI to provide any kind of clue to this being the issue.

Once I submitted the files - the people who wanted access to New Node had it.