OK I have tested the plugin version 2.8.2 on a clean setup with PHP 5.3.29 and the latest WordPress. The tables are created on my end. However I did not test with your exact database setup. Instead I used MySQL5.5.53.
There are a couple of things you could do:
1. Inspect the log files. This could tell us what went wrong. However there will also be some SQL errors in there that are to be expected.
2. Try creating the tables manually. If there is some incompatibility with your system, it might become apparent. Try the following in your SQL console:
CREATE TABLE ccmd_wallets_txs (
id int(10) UNSIGNED NOT NULL,
blog_id bigint(20) NOT NULL DEFAULT ‘1’ COMMENT ‘blog_id for multisite installs’,
category enum(‘deposit’,’move’,’withdraw’) COLLATE utf8mb4_unicode_520_ci NOT NULL COMMENT ‘type of transaction’,
tags varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT ” COMMENT ‘space separated list of tags, slugs, etc that further describe the type of transaction’,
account bigint(20) UNSIGNED NOT NULL COMMENT ‘ccmd_users.ID’,
other_account bigint(20) UNSIGNED DEFAULT NULL COMMENT ‘ccmd_users.ID when category==move’,
address varchar(255) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL DEFAULT ” COMMENT ‘blockchain address when category==deposit or category==withdraw’,
txid varchar(255) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL COMMENT ‘blockchain transaction id’,
symbol varchar(5) COLLATE utf8mb4_unicode_520_ci NOT NULL COMMENT ‘coin symbol (e.g. BTC for Bitcoin)’,
amount decimal(20,10) NOT NULL COMMENT ‘amount plus any fees deducted from account’,
fee decimal(20,10) NOT NULL DEFAULT ‘0.0000000000’ COMMENT ‘fees deducted from account’,
comment text COLLATE utf8mb4_unicode_520_ci COMMENT ‘transaction comment’,
created_time datetime NOT NULL COMMENT ‘when transaction was entered into the system in GMT’,
updated_time datetime NOT NULL COMMENT ‘when transaction was last updated in GMT (e.g. for update to confirmations count)’,
confirmations mediumint(8) UNSIGNED DEFAULT ‘0’ COMMENT ‘amount of confirmations received from blockchain, or null for category==move’,
status enum(‘unconfirmed’,’pending’,’done’,’failed’,’cancelled’) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT ‘unconfirmed’ COMMENT ‘state of transaction’,
retries tinyint(3) UNSIGNED NOT NULL DEFAULT ‘1’ COMMENT ‘retries left before a pending transaction status becomes failed’,
admin_confirm tinyint(1) NOT NULL DEFAULT ‘0’ COMMENT ‘1 if an admin has confirmed this transaction’,
user_confirm tinyint(1) NOT NULL DEFAULT ‘0’ COMMENT ‘1 if the user has confirmed this transaction over email’,
nonce char(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL COMMENT ‘nonce for user to confirm via emailed link’,
extra varchar(255) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL COMMENT ‘extra info required by some coins such as XMR’
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
ALTER TABLE ccmd_wallets_txs
ADD PRIMARY KEY (id),
ADD UNIQUE KEY uq_tx_idx (txid,symbol),
ADD KEY account_idx (account),
ADD KEY blogid_idx (blog_id);
CREATE TABLE ccmd_wallets_adds (
id int(10) UNSIGNED NOT NULL,
blog_id bigint(20) NOT NULL DEFAULT ‘1’ COMMENT ‘blog_id for multisite installs’,
account bigint(20) UNSIGNED NOT NULL COMMENT ‘ccmd_users.ID’,
symbol varchar(5) COLLATE latin1_bin NOT NULL COMMENT ‘coin symbol (e.g. BTC for Bitcoin)’,
address varchar(255) COLLATE latin1_bin NOT NULL,
created_time datetime NOT NULL COMMENT ‘when address was requested in GMT’,
extra varchar(255) COLLATE latin1_bin NOT NULL DEFAULT ” COMMENT ‘extra info required by some coins such as XMR’
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin;
ALTER TABLE ccmd_wallets_adds
ADD PRIMARY KEY (id),
ADD UNIQUE KEY uq_ad_idx (address,symbol,extra),
ADD KEY retrieve_idx (account,symbol),
ADD KEY lookup_idx (address);
Let me know what you find.
