Setting up OwnerTrail Pro
Pro is an add-on. It sits beside the free OwnerTrail plugin and acts on what it finds. Three steps, a couple of minutes.
You are in. Your licence key is in your email, and the zip is in your customer portal, which that email links to. If you started the free trial, nothing has been charged. The steps below take a couple of minutes.
1. Install the free OwnerTrail first
Pro needs it, and WordPress will not activate Pro without it. From your admin: Plugins > Add New Plugin, search for OwnerTrail, then Install Now and Activate. If it is already installed, make sure it is up to date.
2. Upload Pro
Download ownertrail-pro.zip from your customer portal: the payment email’s “Access in your customer portal” link opens it, or sign in there with the email you bought with. Leave it zipped.
Then Plugins > Add New Plugin > Upload Plugin, choose the zip, Install Now, and Activate.
If you have set OwnerTrail’s Code lock to allow code changes only over FTP, WordPress will not let anyone upload a plugin, Pro included. As the site owner, open OwnerTrail > Code and press Unlock for 1 hour first; it relocks by itself. Or unzip Pro and copy the ownertrail-pro folder into wp-content/plugins over FTP.
3. Activate your licence
OwnerTrail > Licence, paste the key from your receipt, and press Activate. The Pro screens switch on at once, and the muted Pro entries in OwnerTrail give way to the real ones.
Each site you activate uses one of your licence’s places: one for Personal, five for Pro. To move a licence, choose Deactivate on this site on the old site first, and the place is free again.
Where everything is
| Screen | What it does |
|---|---|
| OwnerTrail > Quarantine | Holds a risky update until you approve that exact version, with an email showing what the update changes |
| OwnerTrail > Code | For a file that no longer matches: the changed lines, and the genuine file put back in one click, with undo. For a file nothing vouches for: quarantine, which moves it into a sealed vault where it cannot run, and back again in one click |
| OwnerTrail > Developer access | Access for a developer that ends by itself and stays in the areas you choose; a change anywhere else suspends it |
| OwnerTrail > Policies | Rules that refuse a plugin before it is activated: a minimum trust score, a recent change of owner, a closed plugin |
| OwnerTrail > Check a plugin | A plugin’s record before you install it, and whether your policies would refuse it |
If the licence lapses
Protection keeps running. An update held yesterday stays held, a policy keeps refusing what it refused, and developer access can still be suspended or ended. A security product that switched itself off when a payment failed would be worse than none.
What stops is what costs us to provide: updates to Pro itself, and new intelligence.
What the licence check sends
Your licence key and your site’s address, to the licence service of Dodo Payments, which sells Pro, when you activate and then about once a week. Nothing about your plugins, your users or your content. If Dodo Payments cannot be reached, the last good answer stands for 14 days, so an outage on their side changes nothing on yours.
Updates
While your licence is active, new versions of Pro arrive as ordinary WordPress updates, from Decodeinfy rather than WordPress.org. Each package is signed, and Pro checks that signature before WordPress installs anything; a package that does not verify is deleted and refused.
Billing and help
Pro renews yearly. Invoices, your licence key, your card, and cancelling are all in the customer portal. Anything else: decodeinfy@gmail.com.