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

TeamSite 6.7.2 UI Customization

System

We are trying to elminate a couple of changes in the Administration Console. We are wanting to remove some items from the Custom User operations from the Manage Roles screen.

I have nothing in the userops_custom.xml file and when I do a make_toolkit the items are gone. But once TeamSite restarts the items return.

My initial thought is I am not coding correctly. Then my understanding of the doc on the userops.xml file is not to remove code but to enable/restrict access by roles...

Anyone know of a reason that items would re-appear after TeamSite restarts?

Windows 2003 Servers.

Find more posts tagged with

Comments

santosh013

Hi,
From where you are running the make_toolkit?
I mean to say from customer toolkit or from customer-sample.

When You have nothing in the userops_custom.xml,then how
come you are going to the Custom User operations(it must be blank).

Kindly elaborate.

Thanks,

Migrateduser

Here is the userop_custom.xml file

[html]

PUBLIC "-//Interwoven, Inc.//DTD Custom User Operations 1.0//EN"
"../../../../reference/etc/conf/userops_custom.dtd">

[/html]

I ran the make_toolkit from customer_src

I am trying to remove operations from the custom user operations section under manage roles. What I am getting at is if I want to remove operations that are listed out as part of role management so they can never be selected in any role. Where do you code that? If I run the make_toolkit it works until the TS application restarts....Then they are back..

Thanks

Adam Stoller

I'm a bit confused. Your original post says:

I have nothing in the userops_custom.xml file and when I do a make_toolkit the items are gone. But once TeamSite restarts the items return.

In your last post, you showed your userop_custom.xml which has five entries. So - I don't understand what your actual problem is

If the options are listed, but unchecked in the Admin GUI for each of the various roles that you have defined on your server - then the options should not be available to any of those roles (except, perhaps, Master - which is more of an attribute than a role). If you don't want those custom options anymore - remove then from both the ui_custom.xml and userop_custom.xml files and rebuild the toolkit.I'll also assume that you are doing these edits in IWHOME/local/config/lib/content_center/customer_src - and not somewhere within IWHOME/httpd/webapps/...

Migrateduser

My apologies on my posts...

Thanks for your help....

Our problem is I am trying remove a couple of the check boxes from the Administration Console under roles administration. I am specifically wanting to remove 3 items from the Custom User Operations section.

I am making the changes in the IWHOME/local/config/lib/content_center/customer_src and then running the make_toolkit.ipl. They are not listed in the userops_custom.xml and when I do a make_toolkit.ipl the options disappear.

When the application is reset the options reappear, I can then re-run the make_toolkit.ipl and the options disappear.

I haven't made any changes to the ui_custom.xml as fish indicated and maybe that is why they are still showing up.

santosh013

My apologies on my posts...

Thanks for your help....

Our problem is I am trying remove a couple of the check boxes from the Administration Console under roles administration. I am specifically wanting to remove 3 items from the Custom User Operations section.

I am making the changes in the IWHOME/local/config/lib/content_center/customer_src and then running the make_toolkit.ipl. They are not listed in the userops_custom.xml and when I do a make_toolkit.ipl the options disappear.

When the application is reset the options reappear, I can then re-run the make_toolkit.ipl and the options disappear.

I haven't made any changes to the ui_custom.xml as fish indicated and maybe that is why they are still showing up.

Hi,
Anything which You want to add or delete in Custom User Operations is being goverened by ui_custom.xml and userops_custom.xml.
Try to change as per your requirement in ui_custom.xml as well as in the userops_custom.xml(basically for displaying in the Custom User Operations) and run make_toolkit.ipl.
You will definitely get your desired result.
If you want to check then empty the ui_custom.xml and userops_custom.xml in the customer directory and run the toolkit from customer directory.
You will not be able to see anything in the Custom User Operations.
If still you are getting the problem then attach both the xmls and the requirement and I will try to sort it out.

HTH

Thanks,
Santosh

Adam Stoller

One "gotcha" that gets a number of people is that they rename one of the existing config files in .../customer_src/etc/conf/customer and create a new one (empty perhaps) in its place - make_toolkit.ipl will compile all the files it finds in that directory tree - regardless of whether they are named correctly - so if you want to remove something temporarily make sure to move the entire file completely out of the customer_src directory tree before running make_toolkit.ipl

arti1

Hi,

1) I have added custom menu items in Teamsite by making changes in ui_custom.xml.
Now I have to add headings for the group of menu items.
ui_custom has the option to add link. can we add plain text for a menu item that is not a link.

2) I have to restrict visibility/functionality of some menu items for specified workarea only.

can someone tell how to do this?

Adam Stoller

Hi,

1) I have added custom menu items in Teamsite by making changes in ui_custom.xml.
Now I have to add headings for the group of menu items.
ui_custom has the option to add link. can we add plain text for a menu item that is not a link.

2) I have to restrict visibility/functionality of some menu items for specified workarea only.

can someone tell how to do this?

I don't believe that '1' is supported, though you might open a case with Support to try to get an official response (and/or to file a Feature Request for some future release).

Restricting access to a workarea is, I believe, not possible.
There was a recent posting that proposed a method of potentially restricting a menu item to a branch (utilizing custom roles), though I'm not sure if that process has been verified.

Generally, in such cases, you build the intelligence into the CGI itself (preferably via a config file) so that when someone selects the menu item, the code determines who/where/etc. and if it's not the right person or in the right place, presents an informative error message (e.g.: "Sorry, but this option can only be used within the **** workarea on the yyy branch")