Closed pHilgarth closed 1 year ago
Hi @pHilgarth,
terms with spaces should be no problem and I couldn't reproduce this, how does the slug generated for the term look like? If the detailpage page is callable I see no problem if the url matches the slug.
Have you done some adjustments on the typoscript configuration for the term rendering?
Greetings Daniel
Hi Daniel,
Ihave a RouteEnhancer looking like this:
And a typoscript configuration looking like this:
With this configuration I get an URL like this for a term "Design Thinking":
As you can see, the Thinking
is cut off and for some reason placed in the target-attribute. The field url_segment
in the backend is "design-thinking" but I can't reference that field in the typoscript. Since I build an URL with the parameter-option and pass the name-Field I think it makes sense, that the part after the whitespace is cut off because URLs cant have whitespaces. So I thought I simply could use the url_segment
field but then the resulting URL is just "..../detail/" and stops there.
If I remove the typoscript-line parameter = glossar/detail/{field:name}
, I get an URL like this, that leads to a 404 (because of the RouteEnhancers we habe in place)
If I remove both the lines parameter = glossar/detail/{field:name}
and additionalParams >
, I get an URL like this:
This URL is working, but I would like to remove the additional /#Detail
, because it's not needed and it's looking weird and wrong.
Greetings Philly
Hi @pHilgarth,
Ah it's your TypoScript configuration breaking the link rendering, you may take a look at the extensions default settings or look at the core documentation about Typolinks. I know it's a not very beginner friendly topic, you may ask an experienced colleague.
Also it looks like you missed to configure the detailpage, it is used to render links for detailpages automatically. So you don't really have to adjust the typolink settings anyway.
I hope I could help.
Greetings Daniel
Hi,
if there is a term with multiple words, the extension doesnt parse it correctly!
"Not Good" is just replaced with a link to "Not", and the target attribute of that link then is the second word.
-->
Would appreciate some advice here or a hotfix.