What is generating my meta og:description?

I then configured the AddThis Wordpress plugin to remove Add This from the post excerpt, but the same code is still spat out by the excerpt functions.

asked Jul 14, 2011 at 5:02 1,737 19 19 gold badges 66 66 silver badges 112 112 bronze badges

The latter part of your question seems unrelated to what it was in first place. Please consider asking new question for newer separate issue.

Commented Jul 14, 2011 at 15:50

2 Answers 2

The Facebook Page Publish plugin is adding the og:description. Looking through the code in fpp_index.php at lines 843 - 851:

 $description = array(); if ($options['show_post_author']) < $description[] = esc_attr(fpp_get_post_author($post));/*, ENT_COMPAT, 'UTF-8')*/ >if ($options['show_post_categories']) < $categories = esc_attr(fpp_get_post_categories($post));/*, ENT_COMPAT, 'UTF-8')*/ if (!empty($categories)) $description[] = $categories; >echo ''; 

It appears that you have only checked the "post categories" option and have unchecked "post author" on the plugin admin page. See this screenshot.

That's the option the plugin is using the generate the og:description.

answered Jul 14, 2011 at 5:52 chrishajer chrishajer 161 6 6 bronze badges

Thanks. The problem is that I was expecting the og:description to be more than the lowest-level category of the page. I thought it would essentially have an equivalent value to the meta description.

Commented Jul 14, 2011 at 13:31

These OG Meta tags are reported as errors by validator.w3.org:

Line 34, Column 16: there is no attribute "property"

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.