- 🇩🇪Germany sunlix Wesel
Same with this structure
URL:
/service-departments/service-1- Service & Departments (Link:
<button>)- - Service 1
- - Service 2
Expected: Service & Departments / Service 1
Got: service deparments / Service 1 - Service & Departments (Link:
There is a workaround, but it's not the best. This should really get implemented.
I'll explain the workaround, but the problem is if you have a lot of menus and submenus with special characters it's a lot of work.
You have
Paths to replace with custom breadcrumbsconfiguration, and can use it like this:
Example for node path (/articles/random/ (where I'll add a special character in random):
regex!/articles/random/\d :: Article | /articles :: Ran'dom | /articles/random :: <title>
Example for view/page path (/articles/random)
/articles/random :: Article | /articles :: Ran'domFor your French example, it would probably look something like this, you'd need to have 3 entries and this is why it's annoying:
I'm demonstrating here if the content is represented with ID in the URL (if you use a string you can replace\dwith.+):
/l-association :: L'association// Home > L'association
/l-association/presentation :: L'association | /l-association :: Présentation// Home > L'association > Présentation
regex!/l-association/presentation/\d :: L'association | /l-association :: Présentation | /l-association/presentation :: <title>// Home > L'association > Présentation > Content titleThe last entry needs to use regex because it captures every possible combination. The
<title>tag will use the content title, so it should correctly use special characters.To understand better, the first part (up to the first
::separator) is pattern matching, this can either be string matching or regex matching.
From this point on you are building a custom breadcrumb,::separator is used to separate text and URL to use on that text,|separates different crumbs. You can leave out the URL as I do with the last element. So:<first text> :: <first url> | <second text> :: <second url> | <n-th text>