Pending transactions, retries, confirmations over email plus more features introduced in release 2.3.0 of Bitcoin and Altcoin Wallets for WordPress.
UPDATE: Some people experienced an issue with version 2.3.0 where user balances were shown as zero. Please upgrade to version 2.3.1 instead. Your transaction data is safe.
2.3.0 is a major milestone for the Bitcoin and Altcoin Wallets WordPress plugin.
The main improvement is that transactions now have a lifecycle and are displayed in the admin panels. Transaction requests are entered as before via the admin interface, but now their execution is decoupled from submission.
Transactions can now require confirmation either by the user that submitted them via email, or by an administrator, or both. Failed transactions can be retried for a configurable amount of times.
To learn more, see the changelog, or study the new Transactions section in the accompanying PDF manual. You can get the PDF manual when you download the bundle from the downloads section. Here’s a copy of the latest changelog entry:
- Add: Administrator panel to show all transactions in the system.
- Change: The
.csvimport functionality is now moved to the transactions admin panel.
- Change: Transaction requests are now decoupled from transaction executions. They are executed by cron jobs in batches of configurable size and frequency.
- Add: Transactions can require confirmation by an administrator with
- Add: Transactions can require the user to click on a link sent by email.
- Add: Failed transactions are retried a configurable number of times.
- Add: Transaction retries can be reset by an administrator with
- Add: Users can now be notified by email if their transaction fails.
- Add: Frontend transactions lists (wallets_transactions UI) now show the TXID.
- Add: Frontend transaction lists (wallets_transactions UI) are now color coded based on transaction state.
- Fix: The minimum number of confirmations reported by get_minconf() was always
1instead of the user-supplied value.
- Change: Performance improvement in the code that calculates balances for users (function
- Change: Internal transfers that cause two row inserts are now surrounded by a DB lock and atomic transaction to ensure consistency even in case of an unexpected error.