Extend microdata support to "Stars (rated while viewing)" and "Select list" widgets

I am using "Stars (rated while editing)" widget, but the microdata mapping field cannot be found, as if this field is not supported. Only itemtype is displayed. After saving I get:

Saved Rating configuration.
Error message
Notice: Undefined index: microdata in microdata_form_field_ui_field_edit_form_submit() (line 519 of /home/name/public_html/drupal/sites/all/modules/microdata/microdata.module).
Warning: Invalid argument supplied for foreach() in microdata_form_field_ui_field_edit_form_submit() (line 519 of /home/name/public_html/drupal/sites/all/modules/microdata/microdata.module).

Any idea how to solve this?

Nope. Using latest alpha 5.

I also encounter a bunch of errors with keyword research module enabled. whenever I click save, I see errors and node cannot be saved. This issue is solved by disabling the keyword research module.

Can anyone provide some sort of walkthrough on how to setup Fivestar + Microdata?

I have both modules installed and Fivestar is working fine, but I do not know how to get the Microdata module working with Fivestar. I've read a lot of posts about this but couldn't find a solution which doesn't require a patch (which I'm not able to do).

Thanks a lot!

@remkovdz:

...but couldn't find a solution which doesn't require a patch (which I'm not able to do).

Sure you can Remko! ...all you have to do is be able to read and follow well-written instructions:

Applying patches
Applying a patch manually

BTW: #619650: Add help text underneath files on how to apply patches that links to documentation ;)

Thanks for convincing me, I applied the patch manually..

But... I still don't where to begin with the settings in Microdata. Can anyone help me here?

Haven't played with fivestar + microdata yet, but the handbook page seems like a good start: http://drupal.org/node/1181440

#1516982: Add a "View documentation" link to the project's page (left sidebar, "Resources" section)

Is this patch still valid?

Based on linclark last comment, this seems to need work.

Also note #1379244: Update microdata hook for API change has been committed.

I've installed the latest version of the Fivestar and the patch from entry #10 doesn't seem to correspond to the correct line numbers. Is there an updated patch for the newest version of the FiveStar module? (the 7.x-2.0-alpha2 version from March 28 2012)

@msedlacek: Patches are always against latest dev where available and they also should be tested against it. You can still apply the patch manually. If you do go through the trouble to do that, then please be so kind to post a new patch ;)

I tried implementing the above rated while viewing patch in combination with the latest dev version for Microdata (2012-May-04) and I don't see any property data showing up for the review in the source. Is anybody able to help on this? I guess at a basic level I'm not really understanding why there would be support for "rated while editing" and not for viewing, as I'd expect most reviews to be given by anonymous site visitors, and not logged in users. Anyway, if anybody can help with a patch that would be great. I'd be willing to help chip in and pay for the dev work, contact me if interested...

thanks! just applied it and it works for me; (using the following versions)
Microdata 7.x-1.0-alpha5+8-dev
Fivestar 7.x-2.0-alpha2

follow up to previous post. it looks like the aggregaterating property shows up ok in the source code (for me as a property of the Recipe schema, not a child/nested schema), and per the very top I believe there is also a way to do this as a nested schema using the configuration page.

Though, one issue I see in the testing tool and also quoted on this page:
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1093493
"Google needs certain data to generate a rich snippet preview for each product type. For example, a Review without a reviewer or a Review-aggregate without a count will not generate a preview."

So since the count value for the reviews is also not provided as a property (along with the aggregateReview property) the entire snippet is basically rejected by the Rich snippet testing tool if you include the aggregate rating, and it only works if you then take this out. So is there currently a workaround or way to get the count showing as well? maybe I am missing something? thanks! If I understand this correctly, the functionality is only valid if you also have the count property and without that you will cause Google to basically reject your recipe (or whatever schema you are using) if you include the aggregateReview by itself.

Awesome.

This patches looks good to me, anything else should be in a follow up issue.

Proper commit credit attributed to dimon00 as per linclark comment.

--
http://drupalcode.org/project/fivestar.git/commit/46353d4

Hi dimon00, yes if you could reopen the issue that would be great. per the http://drupal.org/node/1445944 thread you cited the issue would need to be addressed here in this thread. I think that for anyone to get functional or practical use out of the microdata/fivestar combination it needs to have the ratingCount, so that should definitely be included in the future...

ps if anyone is interested, I am currently using a workaround where I pull the ratingCount and aggregate/average values via a computed field and then spit them out with the correct microdata info wrapped, here is an example of the code:

$rating_count = $entity->field_review[$entity->language][0]['count'];
$divisor = 20;  // this is done to give it a 1-5 value instead of 20, 100, etc
$rating_average = (int)$entity->field_review[$entity->language][0]['average'] / $divisor;

$display_output = <div itemprop=\"aggregateRating\" itemscope itemtype=\"http://schema.org/AggregateRating\">" ."<span itemprop=\"ratingValue\" style=\"display: none;\">" . $rating_average . "</span>" ."<span itemprop=\"ratingCount\" style=\"display: none;\">" . $rating_count . "</span></div>";

it may not be pretty but works fine for now, validates properly with the rich snippets tool, and is an elegant solution in that it can be neatly undone/removed once the fivestar/microdata fix is implemented)
I had to use css to prevent the info from being displayed twice, which Google says isn't necessarily what they want, but since it validates ok I am content to use it for now...

thanks

I re-opened the other issues.

Lets solved all the microdata problems :)