- Issue created by @jsacksick
- 🇮🇱Israel jsacksick
hm... Actually I managed to reproduce this with D11... The wishlist item add page returns a 404.
- 🇮🇱Israel jsacksick
Not sure what was the initial reasoning but I don't think we could support more than one purchasable entity type properly without passing the type from the url...
Also, since there is no wishlist item type setting for example at the wishlist type level, not sure how we could properly determine the type to use?
Or maybe we'd need a deriver defining local actions for each purchasable entity type defined, but that would result in a weird experience...
"Add product variation item"?
- @jsacksick opened merge request.
-
jsacksick →
committed c00cdb95 on 8.x-3.x
Issue #3536634 by jsacksick: Specify a default bundle for the add form...
-
jsacksick →
committed c00cdb95 on 8.x-3.x
- 🇮🇱Israel jsacksick
hm... Just realized a much simpler alternative was possible... By overridding the "_entity_create_access" route requirement as done for Commerce pricelist as done in 🐛 The add price action is missing on D11 Active .
But it turns out the Wishlist usecase is quite different as we're checking a custom permission (similar to product variations: "manage {$bundle_name} {$entity_type_id}").
Automatically closed - issue fixed for 2 weeks with no activity.