Updating
without losing data.

01Update to a new version

1. Download the new version from your CodeCanyon downloads page.
2. Recommended: Settings → Tools & status → Download JSON, and back up your database.
3. Plugins → Add New Plugin → Upload Plugin → choose the new cryptometer.zip → Install Now → Replace current with uploaded. (Or overwrite wp-content/plugins/cryptometer by FTP.)
4. Database and settings changes are applied automatically on the next page load.

02Coming from an earlier CryptoMeter build (pay-per-read layout)

If your site ran a pre-release build with the older screens (Dashboard, Payments, AI Bots, Simulator, Setup wizard), settings are migrated once: if a wallet was set, Monetize is switched on and AI agents and training crawlers stay on Charge; otherwise the default "Get cited, block training" applies. Existing per-bot choices are kept as exceptions. Old admin bookmarks (page=cryptometer-payments, -bots, -settings, -simulator, -setup) redirect to the matching new screen.

03Self-test

CryptoMeter ships with a self-test that checks pricing, bot classification, intents and presets, IP-list verification, Web Bot Auth signatures (with a locally generated key), the robots.txt parser, signals output, referral vendors, rule snippets, header decoding, access passes, settings sanitisation, CDP JWT signing and the 402 decision engine. It makes no network calls; settings, IP lists and keys are overridden in memory only and never saved; the temporary posts and categories it creates are deleted at the end (or on shutdown if interrupted).

It needs WP-CLI (many hosts provide it over SSH). From your WordPress folder, with the plugin active (a staging copy is ideal):

wp eval-file wp-content/plugins/cryptometer/tests/run-tests.php

Expected output:

CryptoMeter self-test: 176/176 passed

Failures are listed as FAIL <name>. Verified result: 176/176 on PHP 7.4.33 and PHP 8.4.25 with WordPress 7.1.2 (WordPress Playground, SQLite, 2026-09-25; the file was included through a local test harness rather than WP-CLI). If you added your own cryptometer_price or cryptometer_bots filters, they still apply during the test, so some checks may report different values.

04Deactivate and uninstall

Deactivate

Stops everything immediately: no blocking, no logging, no signals. Scheduled tasks are removed; settings and data stay, so you can reactivate at any time.

Delete (uninstall)

Deleting the plugin from the Plugins screen removes (on every site of a multisite network):

• Options cryptometer_settings, cryptometer_secret, cryptometer_errors, cryptometer_db_version, cryptometer_spike_sent, cryptometer_rewrite_version
• Tables {prefix}cryptometer_log, {prefix}cryptometer_referrals, {prefix}cryptometer_hits
• Cached IP lists and key directories, scheduled tasks and cryptometer_* transients

It keeps the payment ledger ({prefix}cryptometer_payments) and per-post/category prices, because the ledger is your accounting record. To delete them too, add this before deleting the plugin (export a CSV first if you need the records):

define( 'CRYPTOMETER_DELETE_LEDGER', true );

After uninstalling, remove any server or CDN rules you copied from Server & cache rules; they live in your server configuration, not in WordPress.