Save!

{eac}SoftwareRegistry + {eac}Doojigger Subscription

From Original price was: $22.50.Current price is: $18.00. every month
with 1 month free trial.

* Save 20% When Bundled  Together *

{eac}SoftwareRegistry - A feature-rich and easily customized software registration and licensing server for WordPress.
{eac}Doojigger is a powerful, extensible WordPress framework: a ready-to-use utility plugin combined with an architecture for building your own plugins, so you can ship professional-grade results in a fraction of the usual development time.

Description

{eac}SoftwareRegistry - A feature-rich and easily customized software registration and licensing server for WordPress.

{eac}SoftwareRegistry is a WordPress software licensing and registration server with an easy to use API for creating, activating, deactivating, and verifying software registration keys.

Registration keys may be created and updated through the administrator pages in WordPress, but the system is far more complete when your software package implements the {eac}SoftwareRegistry API to manage the registration.

One of two scenarios typically occur when a client receives your software:

  1. The client purchases your software, registers your software, then installs your software.

    With {eac}SoftwareRegistry, a new registration key may be created through the purchase process (or manually by the administrator) and then the client may enter the registration key and activate the registration when installing the software.

  2. The client downloads your software, installs your software, and then registers your software.

    The client is presented with a "new registration" screen when installing the software and may request a new registration key through the API which will automatically generate the key and activated the registration.

Registration keys may be verified via API on a scheduled basis so that any updates made by the administrator, via other transaction, or due to renewal or expiration, are updated in the client software.

Registration status may be:

  • Pending (awaiting approval)
  • Trial (limited time trial period)
  • Active
  • Inactive
  • Expired
  • Terminated

Registrations may include (but do not require):

  • Number of users/sites/devices.
  • License level (i.e. 'basic', 'pro').
  • Valid domain(s).
  • Valid site URL(s).
  • Software product-specific options and variations.

{eac}Doojigger is a powerful, extensible WordPress framework: a ready-to-use utility plugin combined with an architecture for building your own plugins, so you can ship professional-grade results in a fraction of the usual development time.

{eac}Doojigger is a WordPress plugin framework: a base plugin that ships with a working set of security, debugging, encryption, session, and administration features, plus an architecture for building your own plugins and extensions on top of it without rewriting WordPress boilerplate each time.

If you build or maintain multiple WordPress plugins — internal tools, client work, or products — {eac}Doojigger's abstract classes and traits handle the repetitive plumbing (activation/deactivation, multi-site awareness, options storage, updates, settings UI, logging) so your code only has to handle what's actually specific to your plugin.

Three ways to build with {eac}Doojigger

  1. Derivative plugins ("Doojiggers") — build your own plugin by extending {eac}Doojigger's abstract classes (abstract_context, abstract_frontend, abstract_backend). You write a small loader file plus a class file; the framework handles the rest.

  2. Extensions ("Doolollys") — a PHP class dropped into the Extensions folder (of the plugin or a child theme) that adds functionality to an existing Doojigger. Lowest-effort option for small, task-specific additions.

  3. Extension plugins ("Doohickeys") — an extension packaged as its own plugin, so it isn't at risk of being overwritten on the parent plugin's next update or reinstall. Can ship its own automatic updates via the included plugin_update trait.

If you're customizing a WordPress site, code that needs to survive a theme change belongs in a plugin, not a theme. Themes should hold presentation code only — anything functional should live in a plugin or plugin extension so it isn't lost the next time the theme is updated or swapped.

Additional information

You may also like…