Adrian Roselli

colinleroy

Milen Petrinski - Gonzo

<p>Add simple share buttons under your posts, add share block in the new editor, or use the widget to add sharing to any widget area your theme provides. This plugin uses simple SVG icons for social network logos and small vanilla JavaScript to allow the user to share the current post or page. Share icons inherit their colours from the theme link colours to match the website design.</p>
<p>Why choose Minimal Share Buttons before other similar plugins?</p>
<ul>
<li>Minimal and elegant look that blends with your theme (tested with all latest default WordPress themes as well as with some other popular themes).</li>
<li>Minimal impact on your site’s performance – the plugin loads only a small SVG file with the icons, less than 1k CSS and 3.5к unminified and uncompressed JavaScript – most of it to make SVG icons work in old browsers.</li>
<li>Doesn’t spy on your users – the plugin doesn’t load any thitd-party scripts that record your user’s activity on your site, doesn’t set or read any cookies.</li>
<li>Sharing through the native share dialog on devices that support it.</li>
<li>GDPR-hasle-free – since the plugin doesn’t leak personal information to third parties, this makes it easier for website owners to comply with the European privacy regulations.</li>
<li>Accessibility – the share links have labels, read by screen readers, and visible for keyboard users.</li>
<li>Gutenberg and WordPress 5.0 ready – the plugin provides block that displays the share buttons so that authors can place them wherever they want in the post content.</li>
</ul>
<h3>Usage</h3>
<p>There are five ways of displaying the share buttons on a post or page:</p>
<ol>
<li>Force them to display under the content of the post by checking the relevant checkboxes in the Display settings sections on the plugin settings screen.</li>
<li>Add Share widget to the sidebar or another widget area.</li>
<li>Use the Gutenberg block to add the share buttons whereever you want in the post content.</li>
<li>Use the shortcode <code>[msb_share title="Share this"]</code> in the classic editor.</li>
<li>Use the function <code>msb_display_buttons()</code> to render the widget in your theme templates.</li>
</ol>
<h3>Theme developers</h3>
<p>From version 1.4 you can more easily display the sharing widget in your templates using the function <code>msb_display_buttons()</code>. The function accepts two arguments – an array of options, passed to the widget, and a second boolean argument that tells the function to echo the resulting markup. Here’s an example:</p>
<pre><code>$args = [
  'before_widget' => '&lt;div class="msb-container">',
  'after_widget'  => '&lt;/div>',
  'before_title'  => '&lt;h2>',
  'after_title'   => '&lt;/h2>',
  'title'         => __( 'Share this article', 'mytextdomain' ),
];
msb_display_buttons( $args, true );
</code></pre>
<p>If your theme uses SVG icons, combined into a SVG sprite, and your sprite has icons for Facebook, Twitter, Google+ and LinkedIn, there are two filters you can use to replace the icons, provided by the plugin, with yours. The results of the two filters are concatenated with a hash between them and passed through <code>esc_url</code> before output.</p>
<p>Another filter allows manipulation of the array of social networks.</p>
<h3>msb_sprite_url</h3>
<p>The filter is applied to the URL of the sprite image and the filter function should return the URL (without the hash sign) of an SVG sprite image, consisting of icons in <code>symbol</code> elements.</p>
<h3>msb_icon_name</h3>
<p>The filter is applied to the icon name before concatenating it to the sprite URL. It should return the ID of the icon symbol in the sprite.</p>
<h3>msb_icon</h3>
<p>The filter allows to change the whole icons markup, It receives the icon markup and the icon name as parameters.</p>
<h3>msb_socials</h3>
<p>The filter is applied to the default list of social networks and allows adding or removing socials networks. The array of social networks is associative array, the key is used for the option name on settings page and for the icon ID, and the value is associative array with three elements – <code>field_label</code> (the label of the field in settings), <code>button_label</code> (the label of the button for screenreader users), and <code>share_url</code> (the URL for sharing links). The <code>share_url</code> is passed through <code>sprintf</code> with two params – the URL of the current page and the title of the page. Example:</p>
<pre><code>function my_add_xing( $socials ){

  $socials['xing'] = array(
    'field_label' => __( 'Xing', 'mytheme' ),
    'button_label' => __( 'Share on Xing', 'mytheme' ),
    'share_url' => 'https://www.xing.com/spi/shares/new?url=%1$s&title=%2$s'
  );

  return $socials;

}
add_filter( 'msb_socials', 'my_add_xing' );<h3>msb_button_classes</h3>
</code></pre>
<p>This filter allows changing the classes of the individual buttons. Two parameters are apssed to the filter functions: the array with classes and the social network / button slug.</p>
<h3>Credits</h3>
<ul>
<li>SVG Icons from <a href="https://fontawesome.com/" rel="nofollow ugc">FontAwesome</a>, <a href="https://creativecommons.org/licenses/by/4.0/" rel="nofollow ugc">Creative Commons CC BY 4.0</a>, MIT licence</li>
<li>Banner image by <a href="https://pixabay.com/en/share-play-words-2482016/" rel="nofollow ugc">heinzremyschindler on pixbay</a>, <a href="https://creativecommons.org/publicdomain/zero/1.0/deed.en" rel="nofollow ugc">Creative Commons CC0</a></li>
<li>Plugin icon based on <a href="https://thenounproject.com/term/share/107273/" rel="nofollow ugc">work by Nathan Diesel from the Noun Project</a>, <a href="http://creativecommons.org/licenses/by/3.0/us/" rel="nofollow ugc">Creative Commons CC-BY</a></li>
</ul>


Minimal Share Buttons

Very fast, very easy to use and modify, no users tracking, no GDPR compliance needed

Light and easy to use

Supported social networks currently are:

Native share dialog (don't know what this does, no apparent effect in Firefox on Windows)
Facebook
Twitter
Google Plus (why?)
LinkedIn
Pinterest
Reddit
Email

There's no control over appearance -- icons are black squares with transparent cutouts. You can elect to display share buttons on all posts or none, all pages or none, all "templates" or none. There's not an option to disable on specific pages, but you can disable for pages generally and use the "Share" block or their shortcode to insert the buttons on pages where you do want it.

Does just what it says

A social share plugin that doesn't spy on users and doesn't slow down your site.

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.

Minimal Share Buttons vs Open Graph Protocol Framework