Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
[Note: Recipe is now in its own issue at https://www.drupal.org/project/schema_metatag/issues/2933278]
Hello,
Can you integrate products, services and recipes?
Thank you
Comment | File | Size | Author |
---|---|---|---|
#15 | schema_metatag-2903107-15.patch | 15.1 KB | ChristophWeber |
#14 | schema_metatag-2903107-14.patch | 13.63 KB | ChristophWeber |
#12 | schema_metatag-2903107-11.patch | 8.51 KB | ChristophWeber |
#10 | schema_metatag-2903107-9.patch | 5.4 KB | agarzola |
#8 | schema_metatag-2903107-8.patch | 8.85 KB | Eric Heydrich |
Comments
Comment #2
cllamas CreditAttribution: cllamas as a volunteer commentedHi, if you tell me more or less how to create a new type of tag I could add Product and Service by myself.
Comment #3
Eric HeydrichHi, I will add the Product Type.
Comment #4
zenimagine CreditAttribution: zenimagine commentedVery well thank you
Comment #5
Eric HeydrichPlease test Product Schema.org type. If it works fine, I will go to the next element.
Comment #6
Eric HeydrichComment #7
cllamas CreditAttribution: cllamas as a volunteer commentedAmazingly fast work! but I'm not sure the patch is correct. I get errors when applying it
Comment #8
Eric HeydrichEdited and tested the patch.
Comment #9
philsward CreditAttribution: philsward commentedIs "Product" not available for 7.x or am I simply missing it? Any chance to get a backport?
Comment #10
agarzola CreditAttribution: agarzola at Chromatic commentedHello! I’ve added a small patch (#9) that creates a Recipe type. It only has a type, name, and description (as that is what we need at the moment), but someone else can run with this and flesh out the rest of the Recipe properties.
Cheers!
Comment #11
ChristophWeber CreditAttribution: ChristophWeber as a volunteer commentedPatch #10 works great for me. Thanks agarzola!
I plan to extend it when I have time, at minimum to the level that I need, and maybe for the full recipe schema if I'm totally in the groove.
Patch #8 applied fine, but left duplicate files in the main schema_metatag directory. A bit of manual cleanup and things are clean.
Comment #12
ChristophWeber CreditAttribution: ChristophWeber as a volunteer commentedI rerolled the patch from #8 so it applies schema_product cleanly from the base module directory.
@philsward Correct, no patches for 7.x-1.x yet. I plan turn my attention to the D7 release once D8 has its stuff ready to go.
Comment #13
ChristophWeber CreditAttribution: ChristophWeber as a volunteer and at BIZX LLC commentedComment #14
ChristophWeber CreditAttribution: ChristophWeber as a volunteer and at BIZX LLC commentedHere's a patch that updates Product schema to include AggregateRating. It incorporates and supersedes schema_metatag-2903107-5.patch, schema_metatag-2916438-2.patch and new code to make Product schema complete enough to validate at Google without errors and warnings. As such Product could be considered a minimally viable schema now. Please test.
Comment #15
ChristophWeber CreditAttribution: ChristophWeber as a volunteer and at BIZX LLC commentedHere's a patch providing Service schema. I am unsure what exactly people are looking for in the Service schema type. Generally, I prioritize what Google lists at https://developers.google.com/search/docs/guides/search-gallery, but Service or Service subcategories don't appear there. So I am providing a straight up clone of Product to get this started.
Comment #16
DamienMcKennaComment #18
KarenS CreditAttribution: KarenS at Lullabot commentedI think this is a reasonable pass at some basic properties for product and service. If someone needs others they can provide a patch. Plus this also gets a basic AggregateRating base in.
Thanks!
Comment #19
KarenS CreditAttribution: KarenS at Lullabot commentedLet's backport this to D7.
Comment #20
KarenS CreditAttribution: KarenS at Lullabot commentedComment #21
KarenS CreditAttribution: KarenS at Lullabot commentedI'm going to create a separate issue for this.