Rob Landry

<p>I was working on a plugin that had a pro (paid) version. This plugin had 2 code bases and was hosted on an external site. This site charged upwards of 50% of what I was charging.</p>
<p>So I became interested in finding a way to provide updates and use only one code base. I also wanted to minimize the cost to sell the plugin so that the money was not going into someone elses pocket. With Sell My Plugin, you host your own plugins. You use PayPal to charge for the purchases. There is a transactions list so that you can keep track of your sales. If you sell 10 copies of your plugin in a month at <strong>$10/ea</strong>, this plugin will save you <strong>$360</strong> per year vs PlugPress and <strong>$600</strong> vs CodeCanyon.</p>
<p>This plugin also uses the familiar domain.com/extend/plugins/ layout just like wordpress.</p>
<h4>Free Features</h4>
<ul>
<li>Your.Domain.com/extend/plugins/ to list all of your plugins just like wordpress.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug to display the plugin info.</li>
<li>A custom search on the plugins page to search for available plugins.</li>
<li>Number of downloads tracked to see which plugins are HOT!!</li>
<li>News updates to provide you with up-to-date info on Sell My Plugin.</li>
<li>Shortcodes are provided to display the plugin where ever you want.</li>
<li>A <a href="http://redmine.landry.me/projects/sell-my-plugin/boards" rel="nofollow ugc">Forum</a> and <a href="http://redmine.landry.me/projects/sell-my-plugin/issues" rel="nofollow ugc">Bug Tracker</a> to get help.</li>
</ul>
<h4>Pro Features</h4>
<ul>
<li>If the plugin is a paid plugin, ?transaction= is added to:</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/version/ to allow downloads.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/update/ to display the update json to allow for plugin updates.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/update/ to display the update json to allow for plugin updates.</li>
<li>[sell-my-plugin] Displays the plugins list.</li>
<li>[sell-my-plugin slug=the-slug] Displays a small info box about the plugin.</li>
<li>[sell-my-plugin slug=the-slug format=full] Displays the full plugin info.</li>
<li>[sell-my-plugin slug=the-slug version=1.0 format=full] Displays the full plugin info for a particular version.</li>
<li>Transactions list for book keeping and tracking.</li>
<li>PayPal express checkout for purchase!</li>
<li>Downloads instantly activated upon completion of purchase.</li>
<li>UPDATES!! provided to plugins once a new version zip is uploaded!</li>
<li>PayPal Sandbox to test plugin purchases without mixing with REAL purchases.</li>
<li>Custom pricing of plugins in backend.</li>
<li>Ability to give paid plugins for free providing a FREE KEY!</li>
<li>
<p>Custom email following purchase including shortcodes to allow for injection of PayPal data!</p>
</li>
<li>
<p>And many more!…</p>
</li>
</ul>
<h3>Requirements</h3>
<p>There are a few things that you need to do to make sure that you can use this plugin.</p>
<h4>PHP 5 >= 5.2.0, PECL zip >= 1.5.0</h4>
<p>This plugin makes use of the ZipArchive class, introduced in PHP 5.2.0.  You must be running at least this version to use the plugin.</p>
<h4>Valid readme.txt and plugin headers</h4>
<p>Like plugins hosted on wordpress.org, you must include a valid readme.txt file and the proper plugin headers in your main plugin file.  Check out a <a href="https://wordpress.org/extend/plugins/about/readme.txt" rel="ugc">sample readme.txt file</a> and use the <a href="https://wordpress.org/extend/plugins/about/validator/" rel="ugc">readme validator</a>.  The Sell My Plugin plugin uses the readme.txt file and the plugin headers to render information about the plugin.</p>


Sell My Plugin

It has zero downloads because it doesn't even work.



Doesn't Even Download

This plugin allows you to host your own plugins on your wordpress installation.

Pascale

<p><a href="https://hitkeep.com/" rel="nofollow ugc">HitKeep Analytics</a> connects WordPress to a self-hosted or cloud HitKeep instance. It injects the normal <code>hk.js</code> tracker from your HitKeep instance and keeps data flowing through the core HitKeep ingest pipeline.</p>
<p>The plugin does not add a separate analytics backend, database, queue, or third-party service. It only loads the tracker from the HitKeep instance you configure.</p>
<h3>Privacy-first web analytics for WordPress</h3>
<p>HitKeep is built for teams that want useful web analytics without adopting a heavy analytics stack. The WordPress plugin keeps setup simple: choose your HitKeep instance, save the settings, and the plugin loads the first-party tracker on public pages.</p>
<p>Logged-in WordPress users are skipped by default, so administrators and editors do not pollute public traffic reports. Browser Do Not Track is respected by default.</p>
<h3>Features</h3>
<ul>
<li>EU Cloud, US Cloud, and self-hosted HitKeep options.</li>
<li>Logged-in WordPress users are skipped by default.</li>
<li>Do Not Track is respected by default.</li>
<li>Pageview tracking through HitKeep’s normal <code>hk.js</code> tracker.</li>
<li>Built-in HitKeep automatic events for outbound links, file downloads, and form submissions.</li>
<li>Optional Web Vitals reporting for LCP, INP, CLS, FCP, and TTFB.</li>
<li>Self-hosted URLs may include a path prefix, such as <code>https://www.example.net/hitkeep</code>.</li>
<li>Clear opt-outs for sendBeacon delivery, route changes, outbound links, downloads, and forms.</li>
<li>Shortcut to open the configured HitKeep instance from the settings page.</li>
<li>Snippet preview so site owners can see which tracker attributes will be emitted.</li>
</ul>
<h3>What the plugin does not do</h3>
<ul>
<li>It does not set analytics cookies.</li>
<li>It does not create WordPress analytics tables.</li>
<li>It does not require a tag manager.</li>
<li>It does not load the tracker from a third-party CDN.</li>
<li>It does not collect form field values, request bodies, link text, or URL query strings through automatic events.</li>
</ul>
<h3>Third-party service connection</h3>
<p>This plugin connects to HitKeep. Depending on your settings, it loads JavaScript from and sends analytics data to one of these HitKeep hosts:</p>
<ul>
<li><code>https://cloud.hitkeep.eu</code></li>
<li><code>https://cloud.hitkeep.com</code></li>
<li>Your own self-hosted HitKeep URL</li>
</ul>
<p><a href="https://hitkeep.com/legal/terms-of-service/" rel="nofollow ugc">HitKeep Cloud terms</a></p>
<p><a href="https://hitkeep.com/legal/privacy-policy/" rel="nofollow ugc">HitKeep Cloud privacy policy</a></p>
<p>Self-hosted installations are controlled by your own HitKeep instance and infrastructure.</p>
<h3>Source code</h3>
<p>The <a href="https://github.com/PascaleBeier/hitkeep" rel="nofollow ugc">main HitKeep project</a> is available on GitHub.</p>


HitKeep Analytics

Adds the first-party HitKeep tracker to WordPress without analytics cookies, third-party CDNs, or a tag manager.

Sell My Plugin vs HitKeep Analytics