Version: 4.3.3 Reporter: timoteus —
The bug as described in https://expressionengine.com/support/bugs/21633/template-routes-with-static-segments-and-require-all-set-to-no-error and https://expressionengine.com/support/bugs/23046/template-route-issue still still exists.
The EE-documentation in https://docs.expressionengine.com/latest/urls/template_routes.html#require-all-variables states:
Require all Variables If set to “yes” all segments defined in your Template Route must be contained in a URL in order for it to match. For example in this Template Route:If “Require all Variables” is set to “No” (the default) then only static segments are required. Any or all of the non-static segments may be omitted. Thus all of the following URLs will match:/name/{first_name}/{last_name}/{suffix}/{page:pagination}If all segments are required only the first URL will match. Neither setting would allow this route to match:/name/Enrico/Fermi/III /name/Enrico/Fermi /name/Enrico /name/III /name/P5 /name/not_name
Kevin is talking about design flaws within the EE-code. But why does the documentation say that it is working?
Either fix it or update the documentation, please?
ExpressionEngine implements Markdown Extra and BBCode. Please see the Markdown Extra docs and the BBCode Wikipedia article for a full reference.
**bold**, __bold__, *italics*, _italics_, ~strike/del~, `code()`
bold, italics, strike/del, code()
Link: [link title](https://example.com)
Image: 
[blockquote]...[/blockquote], [quote]...[/quote], and Markdown style:
> Some quoted text. > > This is all one quote.
[code]...[/code], and you can also specify the language for syntax highlighting, [code=php]...[/code]
GitHub flavored Markdown code fences are also supported:
```
public function decoderRing($str)
{
return str_rot13($str);
}
```