Download websites that use OnePress Social Locker

About OnePress Social Locker

Paying for an article with a tweet was a real growth tactic once. A visitor hit a blurred paragraph or a gated download, shared the page to unlock it, and the publisher converted attention into reach without spending anything. OnePress Social Locker is the WordPress plugin that implemented the mechanic, published under GPL v2 in 2013 and written in PHP, and it belongs to a moment in blogging that has now closed.

The tactic aged badly for reasons entirely outside the plugin's control. Social networks tightened and then closed the interfaces that made a share callback reliable, so the unlock step became easy to fake and awkward to verify. Search engines took an increasingly dim view of content presented to a crawler and hidden from the reader who arrived from the results page. Publishers moved to email capture, which produces an asset they own rather than a share that disappears into a feed.

Which makes the count archaeological rather than commercial. As of October 2026 we detect the plugin on 12 sites, and the honest reading is that presence is not usage. A WordPress installation accumulates plugins and very rarely sheds them, so an active fingerprint mostly indicates that nobody has audited the plugin list, not that anyone is still locking content behind a share button. The rows are best understood as a cohort: sites built during a particular era of publishing that have not been rebuilt since.

Licensing shapes the row as well. The plugin was distributed through the public repository under GPL v2, and the listing there has since been closed, with the download removed. Reviewers on the repository listing describe having paid for a commercial edition, so a detection on its own settles nothing about whether money changed hands. Free distribution of a repository plugin also inflates counts relative to tools sold only under contract, because trying one costs a click and removing it costs a conscious decision that most site owners never get around to making.

Detection has its own limits worth naming. A lock only renders on the posts and pages configured to use it, so a crawl that sees a homepage and a handful of recent articles will miss installations where the locked content sits in an archive. The real installed base is larger than the detected one, and skewed toward sites that put a locked item somewhere visible.

The cohort is genuinely useful to several audiences. Security researchers care because unmaintained PHP code on a live site is attack surface, and an abandoned plugin is a better predictor of an unpatched core than almost anything else on a page. Agencies pitching rebuilds and maintenance contracts care because a stale plugin list is a qualified lead. Anyone studying how growth tactics decay wants the whole population, since the interesting result is the decay curve. Checking one blog tells you one blog still has it, which answers nothing about the pattern.