Describe the bug
On the customer Wishlist page (/wishlist), each saved product is rendered as a link whose href is built by appending a hardcoded .html suffix to the product's url_key. This ignores the Magento product_url_suffix store
configuration (Stores → Configuration → Catalog → Catalog → Search Engine Optimization → "Product URL Suffix"), which controls the suffix used for product URLs across the rest of the storefront.
As a result, on any storefront whose product_url_suffix is not .html (for example an empty suffix, .htm, or a custom value), every product link inside the wishlist points at a URL that does not exist, and the user is taken to the 404 / NotFound route instead of the product detail page. This effectively breaks navigation from the wishlist for those stores.
To reproduce
Steps to reproduce the behavior:
- In the Magento admin, go to Stores → Configuration → Catalog → Catalog → Search Engine Optimization and set "Product URL Suffix" to anything other than
.html (for example, leave it empty, or set it to .htm). Flush the configuration / full-page cache.
- On the storefront, sign in as a customer and add one or more products to the wishlist.
- Navigate to "My Account → My Wish List" (
/wishlist).
- Click on the product name link inside any wishlist item.
Expected behavior
The wishlist product link should respect the store's configured product_url_suffix (the same value used by category, search, and product detail links elsewhere on the storefront) and navigate the user to the correct product detail page.
Actual behavior
The link target is always <url_key>.html regardless of the configured product_url_suffix. On stores that do not use .html, clicking the link leads to the 404 / NotFound route.
Screenshots
N/A
Possible solutions
The product_url_suffix field is already exposed by Magento's storeConfig GraphQL type and is consumed by other parts of the storefront when building product URLs. The Wishlist page should follow the same pattern: read product_url_suffix from storeConfig and use it (together with the existing URL-building utility used elsewhere in the project) when constructing each wishlist item's link, instead of appending a hardcoded .html string.
Debug Report
N/A
Please complete the following device information:
- Device: PC - Windows 11
- Browser: Chrome (also reproducible in Firefox / Safar)
- Browser Version: latest
- Magento Version: Magento Open Source 2.4.8-p4
Please let us know what packages this bug is in regards to:
Describe the bug
On the customer Wishlist page (
/wishlist), each saved product is rendered as a link whosehrefis built by appending a hardcoded.htmlsuffix to the product'surl_key. This ignores the Magentoproduct_url_suffixstoreconfiguration (Stores → Configuration → Catalog → Catalog → Search Engine Optimization → "Product URL Suffix"), which controls the suffix used for product URLs across the rest of the storefront.
As a result, on any storefront whose
product_url_suffixis not.html(for example an empty suffix,.htm, or a custom value), every product link inside the wishlist points at a URL that does not exist, and the user is taken to the 404 / NotFound route instead of the product detail page. This effectively breaks navigation from the wishlist for those stores.To reproduce
Steps to reproduce the behavior:
.html(for example, leave it empty, or set it to.htm). Flush the configuration / full-page cache./wishlist).Expected behavior
The wishlist product link should respect the store's configured
product_url_suffix(the same value used by category, search, and product detail links elsewhere on the storefront) and navigate the user to the correct product detail page.Actual behavior
The link target is always
<url_key>.htmlregardless of the configuredproduct_url_suffix. On stores that do not use.html, clicking the link leads to the 404 / NotFound route.Screenshots
N/A
Possible solutions
The
product_url_suffixfield is already exposed by Magento'sstoreConfigGraphQL type and is consumed by other parts of the storefront when building product URLs. The Wishlist page should follow the same pattern: readproduct_url_suffixfromstoreConfigand use it (together with the existing URL-building utility used elsewhere in the project) when constructing each wishlist item's link, instead of appending a hardcoded.htmlstring.Debug Report
N/A
Please complete the following device information:
Please let us know what packages this bug is in regards to:
venia-conceptvenia-uipwa-buildpackperegrinepwa-devdocsupward-jsupward-speccreate-pwa