I'm sorry, I realize that I was forgotten one setting;
In step 2, you have to select "no action (do not replace)" for "period (.)" in the "punctuation" section of /admin/config/search/path/settings too to make it break.
If you make sure "a" is in the list AND dots must not be replaced, a node with title "A.Foo" will result in url ".foo".
And yes, I'm telling the system to not replace dots but this is a special case because this one will break your site with widely used server configurations. Maybe it should be a setting in the module to prevent urls being starting with a dot, so it can be enabled if your webserver does not allow files and directories to begin with a dot.
This patch file should fix it.
Rik Wijnen → created an issue.
Patch added which could fix this.
Rik Wijnen → created an issue.
@Lendude, this also happens on custom fields. So any untranslatable field with "Link to the Content" enabled always links to the alias of the default language.
For example;
I have one node with two translations ("English" is the original, "Dutch" is the translation) where the fields "Title" and "Identifier" are not translatable, but other fields can be translated.
I add "Identifier" to the admin view "Content" with "Link to the Content" enabled.
In the overview both fields of both translations refer to the English node.
Please note that if you create a node in "Dutch" and then translate it into "English" (so, the original language of the node is not the default language of the site), it will use the alias of the Dutch node. So links on untranslatable fields are always referring to the original translation.
If you put links on translatable fields, it is working as expected; the link is referring to the correct translation.
It's not well documented in Drupal (it took me a while to find anything about this) and I saw that `#config` was changed to `#config_data_store` in the newer Drupal versions.
In this issue of Drupal core they are talking about the fact that Drupal should indicate if a config value was overridden. So, for newer Drupal in the future, it would be recommended to add `#config_data_store`. Please see https://www.drupal.org/project/drupal/issues/2408549 🐛 There is no indication on configuration forms if there are overridden values Needs work
We had the same issue. I made this patch to have pretty paths for list item facets.
After applying the patch, you should be able to select 'List item + id' as 'Pretty path coder'.
I was thinking about the same code as Kaustab_Roy wrote, but than I realized that '0' can also be something like '0px' or maybe something else which equals to '0' (I don't know the code good enough to determine what values are possible). So I think just checking for '0' is not the solution for all, but I'm not sure.
Rik Wijnen → created an issue.
Rik Wijnen → created an issue.
Rik Wijnen → created an issue.