eatransform

<p>This plugin automatically shares your WordPress posts to Twitter/X when you publish them.</p>
<p><strong>Features:</strong></p>
<ul>
<li>Automatic posting when you publish a post</li>
<li>Twitter Card format support (rich preview with image and description)</li>
<li>Traditional text + image format</li>
<li>Customizable tweet text with {title} and {url} placeholders</li>
<li>Featured image support</li>
<li>Connection test tool</li>
<li>Developer-friendly with filter hooks</li>
</ul>
<p><strong>Requirements:</strong></p>
<p>You need Twitter API v2 credentials from <a href="https://developer.twitter.com/" rel="nofollow ugc">Twitter Developer Portal</a>.</p>


Eatransform SNS Auto Publisher for Twitter

Automatically post your WordPress articles to Twitter/X when published.

itthinx

<p>The <a href="https://ogp.me/" rel="nofollow ugc">Open Graph protocol</a> enables any web page to become a rich object in a social graph. For instance, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook.</p>
<p>This WordPress plugin is aimed at automating the process of adding basic and optional metadata to a site’s pages. It is also designed to act as a framework for other plugins or themes and allows to modify and adapt the information provided as needed.</p>
<p>If you find this plugin useful and would like to support our work, you can do so by purchasing in our <a href="https://www.itthinx.com/shop/" rel="nofollow ugc">Shop</a>, thank you!</p>
<p>Supports <a href="https://wordpress.org/plugins/woocommerce/" rel="ugc">WooCommerce</a> to include essential product metadata on product pages.</p>
<h3>Usage</h3>
<p>Install and activate the plugin. It will automatically render the following metadata for posts, pages, etc. :</p>
<ul>
<li><code>og:title</code> : The page’s title is used, this provides the title for posts, pages, archives etc.</li>
<li><code>og:type</code> : The type will be <code>article</code> in general, <code>website</code> for the front page and <code>blog</code> for the blog homepage.</li>
<li><code>og:image</code> : For post types that support featured images, the URL of the featured image is used. Additional metadata <code>og:image:width</code>, <code>og:image:height</code>, <code>og:image:url</code>, <code>og:image:secure_url</code> and <code>og:image:alt</code> are added.</li>
<li><code>og:url</code> : The URL of the current page.</li>
<li><code>og:site_name</code> : The name of the site.</li>
<li><code>og:description</code> : Uses the full excerpt if available, otherwise derives it from the content. For author and archive pages, the type of page and title is used.</li>
<li><code>og:locale</code> : The current locale.</li>
<li><code>og:locale:alternate</code> : Indicates additional locales available with <a href="https://wpml.org/" rel="nofollow ugc">WPML</a> and <a href="https://wordpress.org/plugins/polylang/" rel="ugc">Polylang</a>.</li>
</ul>
<p>The content of the <code>og:image:alt</code> property is based on the Alt Text of the featured image, the image’s Caption in lack thereof, or ultimately the image’s Description in lack of the latter. If any of those are empty, the property is not rendered.</p>
<h3>Filters</h3>
<p>This section is for developers. If you’re not a developer, you can safely skip it.</p>
<p>The plugin provides the following filters:</p>
<h4><code>open_graph_protocol_meta</code></h4>
<p>This filter allows to modify the value of the <code>content</code> attribute for a given meta tag.<br />
It is invoked for every supported type of metadata.</p>
<p>Parameters:</p>
<ul>
<li><code>string</code> <code>content</code> – the current value of the <code>content</code> attribute</li>
<li><code>string</code> <code>property</code> – the metadata name, for example <code>og:title</code></li>
</ul>
<p>Filters must return:</p>
<ul>
<li><code>string</code> the desired value of the <code>content</code> attribute</li>
</ul>
<h4><code>open_graph_protocol_meta_tag</code></h4>
<p>This filter allows to modify the actual HTML <code><meta></code> tag that is rendered in the <code><head></code> section of pages.</p>
<p>Parameters:</p>
<ul>
<li><code>string</code> HTML <code><meta></code> tag</li>
<li><code>string</code> <code>property</code> – the metadata name, for example <code>og:title</code></li>
<li><code>string</code> <code>content</code> – the value of the <code>content</code> attribute</li>
</ul>
<p>Filters must return:</p>
<ul>
<li><code>string</code> the desired output for the HTML <code><meta></code> tag</li>
</ul>
<h4><code>open_graph_protocol_metas</code></h4>
<p>This filter allows to add or remove metadata before it is rendered.</p>
<p>Parameters:</p>
<ul>
<li><code>array</code> of metadata indexed by metadata name</li>
</ul>
<p>Filters must return:</p>
<ul>
<li><code>array</code> of metadata indexed by metadata name</li>
</ul>
<h4><code>open_graph_protocol_echo_metas</code></h4>
<p>This filter allows to modify the HTML that renders the plugin’s meta tags in the <code><head></code> section.</p>
<p>Parameters:</p>
<ul>
<li><code>string</code> HTML with <code><meta></code> tags to be rendered</li>
</ul>
<p>Filters must return:</p>
<ul>
<li><code>string</code> HTML with <code><meta></code> tags to be rendered</li>
</ul>
<h4><code>open_graph_protocol_framework_ext</code></h4>
<p>This filter allows to determine whether additional meta tags should be produced for supported integrations.</p>
<p>Parameters:</p>
<ul>
<li><code>boolean</code> whether to process the integration</li>
<li><code>string</code> the integration</li>
</ul>
<p>Filters must return:</p>
<ul>
<li><code>boolean</code> whether to process additional meta tags for the integration</li>
</ul>
<h3>Why this plugin?</h3>
<p>This plugin was created because we needed an extendable way to render meta tags based on the Open Graph protocol, which would allow to modify the meta tag content rendered or add meta tags when appropriate based on external data.</p>
<p>None of the existing plugins provided a sufficiently flexible way of doing that, among other reasons we needed a solution that would comply with all of these requirements and none of the existing solutions does:</p>
<ul>
<li>must be compatible with WordPress 3.5</li>
<li>must automatically add meta tags for featured images</li>
<li>must be automated and create sensible meta tag content for each page, we don’t want to manually indicate the tag content for every page</li>
<li>must provide a framework for extension through hooks and filters on every tag, and provide a design that allows other plugins to modify the meta tags in flexible ways</li>
<li>must not ask to provide your Facebook account details or application ID when there is no need for it</li>
<li>must not be bloated with features you don’t want or need when you simply want Open Graph metatags to be rendered automatically for your pages</li>
</ul>
<h3>Logo Attribution</h3>
<p>The logo used for this plugin’s icon and banner is the <a href="https://commons.wikimedia.org/wiki/File:Open_Graph_protocol_logo.png#/media/File:Open_Graph_protocol_logo.png" rel="nofollow ugc">Open Graph protocol logo</a> by Facebook – <a href="https://ogp.me" rel="nofollow ugc">ogp.me</a>. Licensed under Public Domain via <a href="https://commons.wikimedia.org/wiki/" rel="nofollow ugc">Wikimedia Commons</a>.</p>
<h3>Validators</h3>
<p>To test the generated metadata you can use several tools, among those:</p>
<ul>
<li><a href="https://cards-dev.x.com/validator" rel="nofollow ugc">X Card Validator</a></li>
<li><a href="https://developers.facebook.com/tools/debug/" rel="nofollow ugc">Meta Sharing Debugger</a></li>
</ul>


Open Graph Protocol Framework

Quick and dirty, this plugin does the job. Activate it and the tags will start showing up in the markup and sharing on facebook becomes more completed. So that is great, that it requires no skill to get where you want to go.

But then you start realizing that a bunch of other stuff no longer works on your site like Woocommerce notices, or you start seeing any add_actions that you added to templates doubling up. 

This plugin calls the full apply_filters on the_content when it renders which makes everything within that stack fire twice causing anomalies which are very hard to track down.

In closing: This plugin will probably work great for you if you have a vanilla site without too much customization. If you have a complex site with things like Woocommerce it's not a good fit.



Works but too invasive.

The Open Graph Protocol enables any web page to become a rich object in a social graph. This plugin renders meta tags within an extension framework.

Eatransform SNS Auto Publisher for Twitter vs Open Graph Protocol Framework