MashShare Add-Ons: What Each One Did, Where to Go Now

A shallow graphite paper tray divided into many compartments, a few holding small paper parts and the rest empty

The add-on catalogue, as it was

The old /downloads/ catalogue and pricing page were among the most linked addresses on the domain, because reviews and roundups linked to them when describing the plugin. This page records what those add-ons did, based on their product addresses and the documentation that referred to them. It is not a store. There is nothing to buy, download or activate here.

Add-on	What it did	Current guide
Social Networks	Added networks beyond the core few	Choosing networks
Responsive	Mobile layouts and separate mobile positions	Mobile share buttons
Sticky Sharebar and Floating Sidebar	Buttons that stay in view while scrolling	Sticky share bars
LikeAfterShare and Facebook Like Bar	Asked for a like or follow around a share	Share prompts
VideoPost Popup	Share request at the end of a video	Share prompts
Google Analytics Integration	Sent share clicks to analytics	Share analytics
PageViews	Showed view counts beside shares	Share analytics
ShortURLs Integration	Short links for shared addresses	Bitly short links
Open Graph	Wrote preview tags for shared posts	Open Graph tags
Click to Tweet	Quote boxes that open the X composer	Click to tweet
Select and Share	Share a highlighted sentence	Highlight to share
Performance Widget	Reported share button load cost	Share button speed

How the MashShare add-ons were installed and licensed

Each add-on was a separate plugin in its own folder under wp-content/plugins, activated on top of the free core, which the plugin directory listed under the slug mashsharer. The core's last public release carried the stable tag 4.0.47 and was marked as tested up to WordPress 6.5; its final changelog entries concern PHP 8.1 and 8.2 compatibility rather than features. Add-ons hooked their settings into the core's settings page, which had tabs for general, visual, networks, add-ons and licences, and appeared there as extra sections once activated.

Licence keys were entered under a heading that read "Activate your Add-Ons" and checked against a licence server on this domain. That server no longer exists, so a key entered today can only fail. The core also carried a number of features that people remember as add-ons because they arrived later: an "Open Graph Meta Tags" switch and a "Twitter Card" switch in the general settings, a "Shorturl method" selector with WP short links, Bitly and Goo.gl as options, a field for a Bitly access token, and a field for a Sharedcount.com API key. A site that ran both the core's Open Graph switch and the separate Open Graph add-on, or an SEO plugin, could easily print two sets of preview tags; Open Graph tags explains the one-source rule that avoids this.

What a site still carrying the add-ons sees

Nothing switches itself off when a plugin closes. The code keeps running with the settings it last saved, and the failures arrive one API at a time. The table lists what owners report in the order it usually appears, with the cause and the independent guide that covers the fix.

Symptom	Cause	What to do
Licence shown as invalid or expired	The licence server on this domain is gone	Ignore the notice; plan removal with the migration checklist
Share counts frozen at old numbers	Async cache refresh depends on WP-Cron and on network APIs that changed	Share counts not updating
Facebook count shows zero	The token in the settings expired or the app was disabled	How to create a Facebook access token
Short links stop being generated	Goo.gl was shut down; the Bitly API moved to version 4	Bitly short links
Notices in debug.log after a PHP upgrade	Add-ons received fewer compatibility updates than the core	Plugin troubleshooting order
Two og:image tags in the page head	Core switch, add-on and SEO plugin all writing tags	Facebook showing the wrong image or share text

Licences

Add-ons were sold individually and as bundles under personal, business and larger multi-site licences, renewed yearly, with a development licence for agencies. Reviews from the time mention yearly prices in euros and the number of premium add-ons in a bundle rising from nine to about a dozen. Licence keys activated updates and support; with the plugin closed, there is no licence server to activate against, and this site cannot issue, renew or refund licences.

If you still run these add-ons

They receive no updates. Treat them as unmaintained code on a live site.
Features that called network APIs, such as counts and short links, fail as those APIs change.
Plan a replacement using choosing a replacement share plugin and remove them with the migration checklist.

Removing the add-ons before the core

The order matters. Add-ons called functions defined by the core, so deactivating the core first can produce a fatal error from an add-on that is still active. Deactivate every add-on, then the core, then delete the folders. Before deleting, look at the general settings for a checkbox labelled "Remove Data on Uninstall?". The plugin's uninstall routine ran only when that box was ticked; the default was unticked, which is why most sites still have its data years after removing it.

When the box was ticked, the uninstall file deleted the options mashsb_settings, mashsb_networks, mashsb_version, mashsb_version_upgraded_from, mashsb_installDate and a handful of notice flags, plus widget_mashsb_mostshared_posts_widget for the most-shared-posts widget. It deleted the post meta keys mashsb_shares, mashsb_jsonshares and mashsb_timestamp on every post, the transients mashsb_rate_limit and mashsb_limit_req, and cleared the two scheduled hooks mashsharer_transients_cron and mashsb_cron_daily. Add-ons kept their own options, usually with the same mashsb_ prefix plus the add-on name, and those were never covered by the core's uninstall routine.

Check it worked

The Plugins screen lists no MashShare entries, and wp-content/plugins contains no mashsharer folder and no folder whose name starts with mashshare-.
An options search for the mashsb_ prefix returns nothing.
A post meta count for mashsb_shares returns zero.
wp cron event list shows neither mashsb_cron_daily nor mashsharer_transients_cron.
A sample post shows your replacement buttons and no literal [mashshare] text, on desktop and on a phone.
wp-content/debug.log gains no new lines mentioning mashsb over a day of normal traffic.

# options, post meta and cron hooks left by the core plugin (WP-CLI)
wp option list --search='mashsb_%' --fields=option_name
wp db query "SELECT COUNT(*) FROM wp_postmeta WHERE meta_key IN ('mashsb_shares','mashsb_jsonshares','mashsb_timestamp')"
wp cron event list --fields=hook,next_run_relative | grep -i mashs

A free core with paid layers was the common plugin business model of the era.

This guide belongs to the MashShare record. If you are working through the same setup, MashShare alternatives: choosing a replacement share plugin and removing MashShare cleanly from a WordPress site are the usual next questions.

Sources

Questions

Can I still download MashShare add-ons here?

No. This is an independent site. Nothing is sold, hosted or supported here.

Will my MashShare licence still work?

The plugin is closed and there is no licence service here. Expect no updates for the core or add-ons.

What replaced the MashShare add-ons?

Most features now come built into maintained share plugins or can be done with plain links and small scripts; each row above links to a guide.

Did the add-ons work without the core plugin?

No. Each add-on was a separate plugin that depended on the free core for its settings page, share count cache and button rendering. Deactivate add-ons before the core to avoid fatal errors.

Which add-on data should I clean up?

The core's options start with mashsb_ and its post meta keys are mashsb_shares, mashsb_jsonshares and mashsb_timestamp. Add-ons stored their own options under the same prefix; search for it after a backup.

Hannah Voss, Editor. Checks every guide against a working WordPress install and the networks' current documentation. Last reviewed September 2026.

About the editor and our methods