Hi,
we're having the same problem and looked through the implementation while evaluating a custom workaround for our case.
We were confused by the fact, that the code in the Resources/views/storefront/layout/footer/footer.html.twig (Line 100 - 105) (v6.6.10.19) acutally looks like the replacement of the URL is already implemented.
It was only when we raised the issue via a Shopware ticket that we learned that this was not a current requirement and that replacing the "unfriendly URL" with the SEO-URL is not a working implementation.
That was a long way trying to figure out how we could get this SEO-URL replacement to work via Configuration, because we assumed an issue there.
The Service-Menu entry is found in the template but does not have a valid SEO-URL, which causes the logic to skip the replacement.
A working implementation for this issue would be very appreciated.
Hi,
we're having the same problem and looked through the implementation while evaluating a custom workaround for our case.
We were confused by the fact, that the code in the Resources/views/storefront/layout/footer/footer.html.twig (Line 100 - 105) (v6.6.10.19) acutally looks like the replacement of the URL is already implemented.
It was only when we raised the issue via a Shopware ticket that we learned that this was not a current requirement and that replacing the "unfriendly URL" with the SEO-URL is not a working implementation.
That was a long way trying to figure out how we could get this SEO-URL replacement to work via Configuration, because we assumed an issue there.
The Service-Menu entry is found in the template but does not have a valid SEO-URL, which causes the logic to skip the replacement.
A working implementation for this issue would be very appreciated.