Databases
StackOverflow2013
Postsdbo
POPlus One Button not traversing the dom to grab snippet data
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPlus One Button not traversing the dom to grab snippet data
    primarykey
    data
    text
    <p>It has been stated that the google plus-one button works it's way up the dom hierarchy when it is looking for microdata to set the +snippets information for sharing (Jenny Murphy said this at <a href="https://stackoverflow.com/questions/7190163/google-1-button-snippet-problem/7261460#7261460">Google+ +1 Button Snippet+ Problem</a> ). Also, the documentation on the +Snippets site from google at <a href="https://developers.google.com/+/plugins/+1button/#plus-snippet" rel="nofollow noreferrer">https://developers.google.com/+/plugins/+1button/#plus-snippet</a> states "If the page is annotated with schema.org microdata, the +Snippet will use the name, image, and description properties found on any schema.org type". However, it doesn't appear that this is truly the case in some conditions. </p> <p>We have a test page at <a href="http://www.magnetstreet.com/stores/html/weddings/testPage.html" rel="nofollow noreferrer">http://www.magnetstreet.com/stores/html/weddings/testPage.html</a> where it is demonstrating a very simple product page which has been marked up with schema.org microdata. This page passes w3c validation and its microdata is parsed properly in Googles rich snippets testing tool. However, when the +1 button is clicked and you proceed to share it, the api is clearly ignoring the itemprops set inside the product tag. This can be seen by how "page title" is displayed instead of "product title" which is the itemprop name.</p> <p>Does anyone see any obvious issues with this code? </p> <p>I would like to note, if we only have microdata properties set on the Product div and within (no itemscope or itemtypes on any outer elements), then the button works as expected. However, We have data on much more complex pages that need the other microdata, so removing all other microdata besides the product is not a solution.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USJohnathon Sanders
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPlus One Button not traversing the dom to grab snippet data
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPlus One Button not traversing the dom to grab snippet data
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPlus One Button not traversing the dom to grab snippet data
      1. USkarry
      1. VTFavorite
    1. COWhat code? There is no code here.
      singulars
      1. POPlus One Button not traversing the dom to grab snippet data
      1. USLightness Races in Orbit
    2. COI'm referring to the source code of the testPage
      singulars
      1. POPlus One Button not traversing the dom to grab snippet data
      1. USJohnathon Sanders
    3. COThe question contains no code.
      singulars
      1. POPlus One Button not traversing the dom to grab snippet data
      1. USLightness Races in Orbit
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload