A feedback after testing the microdatas.
- No microdata available for textareas
- All microdatas should be optional in core fields for flexibility purposes. Hard coded microdatas in fields can create conflict between microdatas set in an item Type or a FieldGroup, and the core fields set in the template. When set in a template, "creaDate" and "modifDate" core fields break the validation of a "Product" microdata type for instance
- Like the selection of a microdata in a select list at the item Type or FieldGroup level, another selection list should be available to optionally set a microdata Type as the property of another microdata Type (Product(Offer(...)))
- There is a conflict between the "id" CSS selector and the microdata model wich creates a strange data in microdatas : ...id="flexicontent"... gives "@id
www.arbracam.org/boutique-terrot/item/flexicontent
" as microdata.
(Conflicts are impossible with a JSON-LD.)
Due to the previous issues, I try to create a JSON-LD format in the template.
- Unfortunaltely, one can't esealy display the "aggregateVoting" datas in the template : the "voting" core field is useless and it seems there are no simple way to display "ratingValue", "bestRating" and "ratingCount" in the template, because "ratingValue", "bestRating" and "ratingCount" fields aren't available for display.
So I go back to the microdatas, where "aggregateVoting" datas are ok, and hack the FieldGroup PHP file. I hard coded what I needed (microdata "Offers" as a property of "Product"), but the other issues still remain.
Hope this will help fixing all the issues and improve the next version.
You can get code sample and screenshot here :
www.flexicontent.org/forum/30-feature-re...nombre-de-votes.html
www.flexicontent.org/forum/30-feature-re...de-deux-niveaux.html