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

Problems setting multi-word values values with CLTs

tobias

Hi there,
this is with TS 6.7.1 SP1 on Solaris 10.

I recently tried to use various CLTs to add or modify users, groups and branches.
When trying to set the "display-name" or "description" attributes I received error messages as soon as the specified value consisted of more than one word. Is this a known issue or do I have to use a special syntax in order to escape the space characters in the strings?

I tried to escape the quotation marks that surround the strings, also I tried to use single quotes instead of double quotes, and I also escaped space characters (each time using the single backslash as escape character), but non of these attempts were successfull.

Here are some examples and the error messages that were returned:

iwmkbr /default/main/branch testbranch "description for new branch" INITIAL

Result:
ERROR: "INITIAL" is not a userid

iwgroup set-description testgroup "new description for existing group"

Result:
options for set-description
<group> <description>

Change the value of the "description" attribute of <group> to

iwuseradm set-display-name john "John Doe"

Result:
options for set-display-name
<user> <display_name>

Change the value of the "display-name" attribute of <user> to

(The "set-display-name" attribute of the "iwuseradm" CLT seems to be undocumented, however using a single word as value it works fine.)

Any experiences or thoughts about this issue?
Thanks,
Tobias

Find more posts tagged with

Comments

Adam Stoller

this is with TS 6.7.1 SP1 on Solaris 10.

I recently tried to use various CLTs to add or modify users, groups and branches.
When trying to set the "display-name" or "description" attributes I received error messages as soon as the specified value consisted of more than one word. Is this a known issue or do I have to use a special syntax in order to escape the space characters in the strings?

I tried to escape the quotation marks that surround the strings, also I tried to use single quotes instead of double quotes, and I also escaped space characters (each time using the single backslash as escape character), but non of these attempts were successfull.

Here are some examples and the error messages that were returned:
iwmkbr /default/main/branch testbranch "description for new branch" INITIAL
Result:
ERROR: "INITIAL" is not a userid

This is regardless of using a single word name (with or without quotes) or multi-word name (with quotes) - I believe this is because the information is coming from another source (in my case, /etc/passwd) and that it won't let me override that (though the error message could be a lot better).Looks like the command should be removed from the CLT (where it is documented in the 'usage' information) - this might be why it was removed (or not entered) into the CLT document. Feel free to open a case with Support about this last one.

tobias

Hi fish, thanks for the reply.

I just found out that the problem is related to the TS setup at the customers :-(

Due to security reasons some parts of the TS installations are not allowed to be located on their default locations. Also some server variables (like $PATH) needed to be modified due to security requirements.

That's why CLTs don't work they way they normally do. The customer created a little script to issue CLTs. For instance, in order to issue the "iwuseradm" CLT I have to call the custom "iwclt" script, followed by the actual "iwuseradm" CLT and its parameters.
Apparently the "iwclt" script was not programmed properly, thus not processing the actual CLT's parameters correctly.

Sorry for alarming you guys and unnecessarily stirring things up. After consulting with the customer I just confirmed that all the stated CLTs actually work fine, even the undocumented "set-display-name" flag of the "iwuseradm" CLT (however, I will ask Interwoven about the discrepancies regarding this parameter).

Frederik

Hmm - interesting, on the TS671 SP1 + P2 Solaris 10 system I'm currently working on - the command:
iwuseradm set-display-name userid "name"
returns:
ERROR:00048: Operation not supported
This is regardless of using a single word name (with or without quotes) or multi-word name (with quotes) - I believe this is because the information is coming from another source (in my case, /etc/passwd) and that it won't let me override that (though the error message could be a lot better).

Looks like the command should be removed from the CLT (where it is documented in the 'usage' information) - this might be why it was removed (or not entered) into the CLT document.

Feel free to open a case with Support about this last one.

ts.670.clt.unix.pdf mentioned the

iwuseradm set-display-name

command, but the release notes for 6.7.1 mentioned that this is a docbug (ts.671.rn.pdf). The new CLT guide for 6.7.1 SP1 (ts_671sp1_clt_unix_v01_en.pdf) no longer mentions the

iwuseradm set-display-name

, and the Release Notes of that version (ts_671sp1_rn_v02_en.pdf) also no longer mention the docbug.

EDIT: so if Tobias claims that

iwuseradm set-display-name

works for him, then that's -euhm- surprising Smiley Wink

tobias

Nevertheless the mentioned CLT works with the "set-display-name" attribute.
Due to the very special setup of TS at the customer, I have to believe the local administrators when they tell me that the installed version is TS 6.7.1 SP1 (which they do).

Also, Interwoven Support confirmed that the "iwversion" CLT does not necessarily need to return the correct SP of the installation.
However, I did not ask them whether there are any plans of getting rid of this parameter in the future.

Adam Stoller

Nevertheless the mentioned CLT works with the "set-display-name" attribute.
Due to the very special setup of TS at the customer, I have to believe the local administrators when they tell me that the installed version is TS 6.7.1 SP1 (which they do).

Also, Interwoven Support confirmed that the "iwversion" CLT does not necessarily need to return the correct SP of the installation.
However, I did not ask them whether there are any plans of getting rid of this parameter in the future.

You can get full details about the version by going through the GUI and clicking on the About link in the upper-right-hand corner.

tobias

Fish,
I know about the About button, of course. But as I mentioned the customer has a special way of setting up TS. Part of which is, to install TS on one server first, do some checks, then pack all the necessary files, transfer them to the actual TS server and unpack them there.
They didn't however bother to transfer the "install" directory, which holds the file iwov-inventory.xml which contains the version information that is displayed by the About button.

However, on the original TS server, I could confirm that the current version is TS6.7.1 SP1

Adam Stoller

Fish,
I know about the About button, of course. But as I mentioned the customer has a special way of setting up TS. Part of which is, to install TS on one server first, do some checks, then pack all the necessary files, transfer them to the actual TS server and unpack them there.
They didn't however bother to transfer the "install" directory, which holds the file iwov-inventory.xml which contains the version information that is displayed by the About button.

However, on the original TS server, I could confirm that the current version is TS6.7.1 SP1

That doesn't sound like an officially supported method for installing TeamSite - so I think you're pretty much on your own.
I can understand doing this with customizations / customized configuration files - but doing it with the entire application (instead of going through the full installation process) is, IMO, asking for problems. But that's their/your problem ...