Plugin profile · observed daily since 02 Aug 2026
WP-Copyright-Protection
Active installs5,000+ rounded
Current authorDave Ligthart
Owner changesNone while we have been watching
Last release18 months ago 23 Feb 2025
Support— no recent threads
Releases on record9
Rating4.4 /5 · 21
Added to directory22 Feb 2011
Requires WP2.3
Requires PHPfalse
Version lag0.4 behind
Tested up toWP 6.7.7 WordPress is now on 7.1
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Dave Ligthart throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| dave.ligthart | 9 | 12 Apr 2019 | 23 Feb 2025 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Moderately adopted: 5,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
17 downloads a day over the last 7 days, rising 21% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 33/day04 Sep 2026
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 22 | 22 | 0 | 11 | 24 | 11 | 22 | 22 | 11 | 12 | 22 | 11 | 22 |
Unchanged throughout: ratings total (21) · active installs (5,000+) · version (1.9) · support threads (0) · threads resolved (0)
34 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory15 years ago 22 Feb 2011
Requires WP2.3
Requires PHPfalse
Version lag0.4 behind
Is anyone still maintaining this?
- No release in 559 days (1.5 years). The last was 23 Feb 2025.
- Declares compatibility only up to WordPress 6.7.7, while 7.1 is current. The author has not confirmed it runs on the last 4 releases.
- The same account maintains 7 other plugins, and none has been updated in over a year, the most recent on 18 Dec 2012.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 17 Aug 202619 days agoDormancy threshold crossed540 days since the last release (2025-02-23). Dormancy is a maintenance observation, not a judgement about the owner.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 23 Feb 202518 months agoVersion 1.9 released
- 23 Feb 202518 months agoVersion 1.9.1 releasedfrom the release logCommitted by dave.ligthart.
- 22 Feb 202518 months agoVersion 1.8 releasedfrom the release logCommitted by dave.ligthart.
- 22 Feb 202518 months agoVersion 1.8.1 releasedfrom the release logCommitted by dave.ligthart.
- 22 Feb 202518 months agoVersion 1.8.2 releasedfrom the release logCommitted by dave.ligthart.
- 22 Feb 202518 months agoVersion 1.8.3 releasedfrom the release logCommitted by dave.ligthart.
- 22 Feb 202518 months agoVersion 1.8.4 releasedfrom the release logCommitted by dave.ligthart.
- 19 Jun 20197 years agoVersion 1.6 releasedfrom the release logCommitted by dave.ligthart.
- 12 Apr 20197 years agoVersion 1.5 releasedfrom the release logCommitted by dave.ligthart.
- 22 Feb 201115 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Dave Ligthart for all 34 days we have observed it.
- It was last released 18 months ago (23 Feb 2025).
- Its author declares it tested up to WordPress 6.7.7; WordPress is now on 7.1.
- WordPress.org reports 5,000+ active installs.
- It carries 21 ratings, averaging 4.4 out of 5.
What we don’t know yet
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.
Secure Copy Content Protection and Content Locking
Copy Protection plugin is activated it disables the right click, copy paste, content selection and copy shortcut keys
20,000+ installs4.3★ (62)updated 03 Sep 2026
Compare side by side Right Click Ban – Disable Right Click & Content Copy Protection
Disable right click to protect your content. Blocks text copying, image dragging, keyboard shortcuts, F12 and developer tools access.
200+ installs4.3★ (7)updated 20 Aug 2026
far fewer installs
Compare side by side WP Content Copy Protection & No Right Click
This WP plugin protects posts from being copied (content copy protection). Keep your content safe from unauthorized distribution!
100,000+ installs4.8★ (1,131)updated 02 Sep 2026
20× the installs
Compare side by side Disabled Source, Disabled Right Click and Content Protection
Disable Source(Ctrl+U), Disable Right click, Disable F12 functional key, and Disable save the page(Ctrl+S) and Content Protection of your WordPress We …
10,000+ installs4.9★ (102)updated 21 Aug 2026
Compare side by side Disable Right Click & Content Copy Protection
Content protection plugin that disables right-click, prevents copying, and blocks image dragging with customizable settings and notifications.
50+ installsupdated 27 May 2026
far fewer installs
Compare side by side ContentShield Lite
Complete content protection suite. Disable right-click, copy, print, shortcuts, image saving; add watermarks, block RSS, hotlinking.
20+ installsupdated 27 Apr 2026
far fewer installs
Compare side by side Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about WP-Copyright-Protection: a person reads every submission, and corrections get a reply within 5 business days.