"Related Products" Taxonomy Support (PRO)

[gkv-ckultzow]

Our core use case for the plugin is to put recipes on small CPG brand sites that are showing recipes explicitly made using their products. The existing taxonomies really can't be repurposed for this very well as they're still needed for general organization, but this wouldn't need to work any differently than Cuisine currently does.

If this was added, it would also be great if [cooked-browse] supported a related_product="slug" parameter to use on various product pages, that limited the recipes specifically to that taxonomy.

[XjSv]

@gkv-ckultzow Hey there, I finally had some time to think this over. This sounds like a nice feature I would just like to flush it out a little more.

Would these products be ingredients?

[gkv-ckultzow]

I've actually completed this work as described on a copy of the plugin, which you can see on our staging site. Most of the work was done in Pro, just duplicating what's there for cuisine, then a little addition in base to accommodate the Browse dropdown. I think just this is very helpful. https://candyshopcostg.wpenginepowered.com/recipes/ https://candyshopcostg.wpenginepowered.com/recipes/related-product/reeses-peanut-butter-cup/ Yes, the products are always ingredients, but in practice there's complications when it comes to "making that more automated / useful". You can't assume how many or what format of the product are needed - 3 packets? 1 pouch? 12 oz of [product] as prepared using directions on box? I have explicitly not been able to have consistency approved, this client has required us to have the formatting be different from recipe to recipe. There's also a ton of different ways to store "products" on a site. In the consumer packaged goods world, you're not typically selling through woocommerce, but plenty of people might be. On this site, they're currently pages. Usually, they're custom post types. So no way to automate that list because there's no way to know what the post type would be. I thought about what it would take to have the "product ingredient" be represented as more of an object so that it could become a link, but there's so many issues. What would the action of linking it do - go to a product detail page? Launch a store locator? That's typically by SKU. Is it tied to a SKU instead of a slug? How is the SKU stored? Is the product called out on the page? I think it's so open a question with no "typical" answer that I would just tell a developer "Best practice is to match cooked-related-product slugs with your product's information and use the taxonomy query [example] to satisfy other code needs" Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: Armand Tresova ***@***.***> Sent: Monday, September 9, 2024 5:55:24 PM To: XjSv/Cooked ***@***.***> Cc: Chris Kultzow ***@***.***>; Mention ***@***.***> Subject: Re: [XjSv/Cooked] "Related Products" Taxonomy Support (PRO) (Issue #51) Caution! This message was sent from outside your organization. Allow sender<https://mail-cloudstation-us-west-2.prod.hydra.sophos.com/mail/api/xgemail/smart-banner/34cbe36c7e9fd2d13aa01bf60abd48ce> | Block sender<https://mail-cloudstation-us-west-2.prod.hydra.sophos.com/mail/api/xgemail/smart-banner/cf0fedeb94f56049fe78a62985a569a4> @gkv-ckultzow<https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2drdi1ja3VsdHpvdw==&p=m&i=NjVmODk0MmNkZTRiMDU2NWZkOTFiZWUz&t=NmJBckttQnliamFPVjMrZndINnlmWlliM3FPU0x1VXRTTW1raWMzQkxuOD0=&h=10b89666eba241798f05f5b830891e30&s=AVNPUEhUT0NFTkNSWVBUSVZ-CzEl059Ym1RlqwKl3ZhNfC-dR2N5IDL9CUAdMA_6tA> Hey there, I finally had some time to think this over. This sounds like a nice feature I would just like to flush it out a little more. Would these products be ingredients? — Reply to this email directly, view it on GitHub<https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL1hqU3YvQ29va2VkL2lzc3Vlcy81MSNpc3N1ZWNvbW1lbnQtMjMzOTIyMzE3MA==&p=m&i=NjVmODk0MmNkZTRiMDU2NWZkOTFiZWUz&t=VHJFWlFGdnBqZGliZUpYOFRsM3NLeWdONGRwODg4ZEpzNG5MTjRJTlFYWT0=&h=10b89666eba241798f05f5b830891e30&s=AVNPUEhUT0NFTkNSWVBUSVZ-CzEl059Ym1RlqwKl3ZhNfC-dR2N5IDL9CUAdMA_6tA>, or unsubscribe<https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BSVgyRlVZRkI0NVhWWE1NWlVURlBUM1pWWUtNWkFWQ05GU002QUFBQUFCTTZRTlRYT1ZISTJEU01WUVdJWDNMTVY0M09TTFRPTjJXS1EzUE5WV1dLM1RVSE1aREdNWlpHSVpER01KWEdB&p=m&i=NjVmODk0MmNkZTRiMDU2NWZkOTFiZWUz&t=QjZiQ0l4dzZqOHVpS2ltM1p4TG1HLzBHYVJFdHBkdURZNDRiNHR5UGpiTT0=&h=10b89666eba241798f05f5b830891e30&s=AVNPUEhUT0NFTkNSWVBUSVZ-CzEl059Ym1RlqwKl3ZhNfC-dR2N5IDL9CUAdMA_6tA>. You are receiving this because you were mentioned.

[XjSv]

That was exactly what I was concerned with, the "making that more automated / useful" part. More specifically how to implement it in a way that is not obtrusive to the users that might not need it and useful enough to the users that do need it, in the various ways that they might have products configured.

Maybe a better solution for the plugin itself would be to implement a hook that would allow developers to add any taxonomy they need. This way it makes it flexible enough so it does not need to be hacked and updates can be applied regularly. And at the same time you get the functionality that's needed.

[gkv-ckultzow]

Being able to just create custom taxonomies and have them float down to the browse button would solve more generally, agreed. Definitely shifts it from an hour of copy paste to a real change, but I'm glad to see you guys being forward thinking with the plugin. Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: Armand Tresova ***@***.***> Sent: Wednesday, September 11, 2024 5:06:31 PM To: XjSv/Cooked ***@***.***> Cc: Chris Kultzow ***@***.***>; Mention ***@***.***> Subject: Re: [XjSv/Cooked] "Related Products" Taxonomy Support (PRO) (Issue #51) That was exactly what I was concerned with, the "making that more automated / useful" part. More specifically how to implement it in a way that is not obtrusive to the users that might not need it and useful enough to the users that do need it, in the various ways that they might have products configured. Maybe a better solution for the plugin itself would be to implement a hook that would allow developers to add any taxonomy they need. This way it makes it flexible enough so it does not need to be hacked and updates can be applied regularly. And at the same time you get the functionality that's needed. — Reply to this email directly, view it on GitHub<https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL1hqU3YvQ29va2VkL2lzc3Vlcy81MSNpc3N1ZWNvbW1lbnQtMjM0NDcwMTc0Mg==&p=m&i=NjVmODk0MmNkZTRiMDU2NWZkOTFiZWUz&t=M0I0d25GclFtWDlMYmZIQ1NYaWFUbSsyVVJFZEN5NFIvYVhHRTI1SE1obz0=&h=aa1e8cb35ead4098a9143783c464042a&s=AVNPUEhUT0NFTkNSWVBUSVZ-CzEl059Ym1RlqwKl3ZhNfC-dR2N5IDL9CUAdMA_6tA>, or unsubscribe<https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BSVgyRlU3TUpFM05INEQ3RFkzR1E2M1pXQ1dGUEFWQ05GU002QUFBQUFCTTZRTlRYT1ZISTJEU01WUVdJWDNMTVY0M09TTFRPTjJXS1EzUE5WV1dLM1RVSE1aREdOQlVHNFlEQ05aVUdJ&p=m&i=NjVmODk0MmNkZTRiMDU2NWZkOTFiZWUz&t=TmVrdklvTU5VOVJoT2FCWXlGYkZwdU4wYkNHOFVhb0RCV04xeHl2UDBlMD0=&h=aa1e8cb35ead4098a9143783c464042a&s=AVNPUEhUT0NFTkNSWVBUSVZ-CzEl059Ym1RlqwKl3ZhNfC-dR2N5IDL9CUAdMA_6tA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[XjSv]

I will attempt to implement that in one of the next upcoming releases. I have a backlog already going, and being that you already have a solution in place I will add this to the queue.