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

Site map alias length limit?

Bowker

There appears to be limit of 81 characters for an alias in the sitemap.

Has anyone been able to extend it?

Find more posts tagged with

Comments

Garth McMillan

I've just checked ours and we have aliases greater than 150 characters (the first one I checked was 156).

However, we generate these aliases programmatically via the workflow. Perhaps the character limit is only when entering via the TeamSite interface - in which case it would likely be done via JavaScript, which you should be able to alter.

Garth McMillan

I was curious on this and looked into adding long aliases via the TeamSite interface. I can add aliases longer than 81 characters via the interface in both 6.7.2 and 7.3.1.

I'm not sure why you are unable to.

Bowker

Maybe it was removed in 7.3.

I opened a case yesterday with Interwoven and received the response quoted below this morning.

I tried these changes (I also increased the field size from 15 to 50 so it's a little more user friendly) and TeamSite picked up the changes as soon as I saved it (JSP's have their advantages sometimes).

The rationale for this limit is that the idea of the url alias is to have a short/simple version of the long urls. That's the reason behind having a limit in the number of characters. There is no way official around this.

As that doesn't help, there is a workaround that I have seen to work on a TeamSite 7.1 system and seems to be still usable. The character limit is enforced in the Sitemap node details window only, using an field defined as:

| <input type="text"
| id="alias.name"
| size="15"
| maxlength="80"
| value=""
| onkeyup="handleKeyUp(event)"
| onFocus="if ( !this.getAttribute('alreadyFocused') ) { this.setAttribute('alreadyFocused', true); this.value=''; }"
| />

The maxlength attribute in here is the culprit. An alias name like "thisisaverylongaliasnamethatwontfitinthealiasinputfieldasitismorethaneightycharacterslong" (90 characters) will be truncated to "thisisaverylongaliasnamethatwontfitinthealiasinputfieldasitismorethaneightychara" (80 characters) on input because of the constraint.

As I said, there is no supported way of changing this, but it is technically possible to change this maxwidth value or to remove the constraint altogether. The Node Details window is defined by \ApplicationContainer\server\default\deploy\iw-cc.war\livesite\Site\SiteMap\NodeDetailsForm.jsp. If you open that file in an editor and search for the string "alias.name" you will find the line where the constraint is set. If you remove it and save the file, then the next time the Node Details form is pulled up it won't have the maxlength attribute anymore and any string will be accepted.

As mentiioned before, this is a workaround only. Any software updates could overwrite the changed NodeDetailsForm.jsp file, and future TeamSite versions might invalidate this approach altogether.