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

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Doc names with special characters

Eric_Ace

In the PathSegmentServiceDefault class the method generatePathSegment has some logic to replace a doc name composed entirely of special characters (e.g. -.,;?!:'-.,;?!:'-.,;?!:') with a random number, but then it allows the doc to be created anyway with the name as originally provided. Is there any particular reason one should preserve this functionality if overriding the default path segment service?

Find more posts tagged with

Comments

Florent_Guillau

What do you mean by then it allows the doc to be created anyway with the name as originally provided? The idea here is to generate the path segment only (visible in the url or in the database as the "name" column, and unique per folder). This service does nothing about changing the document's title.

Eric_Ace

I guess what I'm asking is - if I save a document "FOO" the name field in the hierarchy table is "FOO" but if I save a document called (odd name from above) then the name field in the hierarchy table is "123523452345425764"... So the question is - am I in peril if I modify this behavior

Florent_Guillau

No there's no danger in changing this behavior. Nuxeo only does it to avoid ugly URLs with lots of escaped characters in the rare cases where documents have strange names without alphanumeric parts.