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

ui_remove_menu_items does it work in 6.1

cc96ai

I read the 6.1 Admin Guide

"You can disable TeamSite menu items and buttons in WebDesk Pro on a per-role basis. To disable a TeamSite menu item, add a line to the [ui_remove_menu_items] section of iw.cfg"

It only can disable in WebDesk Pro ?
can we disable item in CCSTD ?

Thanks

--------------------------------------------
TS 6.1 W2K3
OpenDeploy 6.0
CC Pro/Std

Find more posts tagged with

Comments

nipper

That is for the OLD GUI, not cc_std or cc_pro.

Check out the GUI customization guide for this answer.

Migrateduser

The manuals are available on support (need support login):

https://support.interwoven.com/library/manuals/teamsite/teamsite.asp

hth,

lissa

cc96ai

I modified roles_custom.xml

<role id="author">
<operation id="cu.ccstd.common.delete.link" isPermitted="false"></operation>
</role>

and rebuild the apps

but author still can use "delete" link

--------------------------------------------
TS 6.1 W2K3
OpenDeploy 6.0
CC Pro/Std

gzevin

are you sure you referring to the operation id, not the link itself?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

cc96ai

actually, i did try it

<roles>

<role id="author">
<link id="iw.ccstd.common.delete.link" isPermitted="false"></operation>
</role>
...
</roles>

but it didnt work for me also

--------------------------------------------
TS 6.1 W2K3
OpenDeploy 6.0
CC Pro/Std

gzevin

no, this is not what I meant.

in ui xml you will have something like:

<link id="regenerate.custom_menu_item.link" label="Regenerate Site" description="Regenerate Site" url="/../iw-bin/wdpro_menu.ipl/regen.ipl" windowFeatures="width=200,height=200,scrollbars=yes,menubar=yes, titlebar=no,resizable=yes,status=yes,center=true,dependent=false" target="_blank" operationID="regenerate.custom_menu_item.link.op"/>

in roles_custom you need to refer not to the link id, but the value of the attribute operationID

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Adam Stoller

Also - to be "technically" correct - you need to add entries for all the other roles with isPermitted="true" for them, otherwise you may not [always] get the expected results for other roles.

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

gzevin

oh, yes, thanks for the remarks, I simply did not look at this aspect.

as a matter of fact, I think it's a must to do this

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

cc96ai

I opened the case in support.

the response is

"As I understand it from my research, restriction an OOTB link by role is not offically supported in TS6.01, meaning any changes you make could be overwritten by patches or service packs. As a workaround you can edit ui_custom.xml to remove the link and re-add it as a custom link which you can the restrict by role using roles_custom.xml."

so if i want to disable it, will it be any risk on it?

--------------------------------------------
TS 6.1 W2K3
OpenDeploy 6.0
CC Pro/Std

Adam Stoller

If you want to remove it - that's simple.
If you want to restrict it - that's simple, but not entirely "clean" - in that you need to do what has already been talked about in this thread - but for the users who will retain access to the menu item, the item will no longer be context-sensitive (e.g. greying out when you're not within an area for which it is applicable)

Other than that, there really shouldn't be much 'risk' involved -- assuming you know why you're disabling the menu function and how you expect users to do what they need to do without it.

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