setup the ezpublish.yml with a matcher such as:
with this configuration, the result is these broken behaviors:
- content that begins with the same string as the siteaccess will result in a kernel error.
- the siteaccess name is repeatable. for example, given an object named "test", these are accepted urls:
they all point to the same object
- usage of twig operator path( location ) or other other path() variants with a location where the url has this structure:
site.host.name/<SA_name>/<string that includes SA_name>, will result in urls lacking the <SA_name> part.
example: calling a path(...) for an object with url:
will result in a url: