Archives: Documentation
-
Transactions are not saved to the database
What to do when transactions are not saved: a missing table, processing that does not run, or a token without synchronization.
-
REST API endpoints
REST endpoints in the affinite-fio/v1 namespace: process-transactions (secret/force) and license activate/verify/deactivate.
-
XML export of customers without orders
A button exports customers without orders to XML (incl. metadata except sensitive keys). The export is streamed and protected.
-
Items per page
The only setting — customers per page — is changed via Screen Options. Default 20, range 1–999, stored per user.
-
Creating Watermark Rules
Learn how to create and manage watermark rules in Affinite WP Watermark plugin.
-
Feature overview
A brief overview of the main features: transaction download, automatic matching, multiple accounts, manual review, ignored accounts and notifications.
-
AJAX actions and security
The plugin’s admin AJAX actions (attach, mark/unmark reviewed, amount ok, ignored), secured by a nonce and the manage_options capability.
-
How often are transactions checked?
It depends on the server CRON interval; each run downloads transactions for the configured number of days back (2 by default).
-
CRON returns a 403 error
A 403 error means a missing security token. Use the URL with ?secret=… from the Fio settings page and update the server CRON.
-
Deleting a single customer
Click Delete on a customer row and confirm. The server verifies the user has no extra roles, orders or content before deleting.