dashed-slug.net

Thanks for sending me the complete stack trace.

This error is expected in normal operation. For robustness the plugin rediscovers some transactions that have already been discovered. It then attempts to insert them into the database, but if they already exist it fails and moves on.

Are you observing any issues such as transactions failing? If not, then this error should not be a problem.

These error messages can quickly fill up your logs. There are two possible solutions to this:

1. Disable logging with define( 'WP_DEBUG_LOG', true ); in your wp-config.php.

2. Install logrotate on your wp-content/debug.log to minimize the amount of disk space that logs take.

Do let me know if you observe any problems in plugin operation. Thanks.

Hello,

Unfortunately the plugin architecture does not easily lend itself to this.

The reason is that the data displayed is live data, made available through an API, that only exposes information relevant to the current user. The frontend UIs have no access to other people’s balances.

There is nothing stopping you from calling the PHP API to get other user’s balances. Documentation is here: https://wallets-phpdoc.dashed-slug.net/classes/Dashed_Slug_Wallets_PHP_API.html#method_api_balance_filter

You could then write some PHP code to loop over your users and write out any markup you like. Hope this helps!

kind regards
Alex

Hello again,

Never mind, you don’t have to run the query above.

I was able to reproduce the problem on my end. It’s not a critical issue, but it is now fixed in patch 3.3.6.

Again thank you for your help!

kind regards
Alex

OK it turns out that there was a bug in the code after all. This is fixed in 3.3.4.

My fault, apologies for the trouble and thanks very much for assisting me to resolve this.

Do let me know if you continue to face problems after upgrading, although it is very unlikely.

kind regards

The reason I’m asking the above question is because the wp_wallets_txs table should have a unique constraint on txid, address, and symbol.

Previously the constraint only involved txid and symbol. It is possible that the recent schema upgrade failed for you because your tables are large.

IF that is the case, then you could do the following:

1. Deactivate the plugin.
2. Backup your database.
3. Recreate the unique constraint with:
ALTER TABLE wp_wallets_txs DROP INDEX uq_tx_idx, ADD UNIQUE KEY uq_tx_idx(txid,address,symbol);
4. Activate the plugin.

If you are not sure whether you need to do this, please share with me the output of the SHOW INDEX query and I’ll let you know.

kind regards

OK thank you.

Can you also please show me the output of this SQL query?

SHOW INDEX FROM wp_wallets_txs;

Thanks for the additional info.

CPU and memory capacity are irrelevant. It’s good to know that you have ample disk space. But just because you have a 3TB disk does not mean that it is necessarily available for use by the DB. Could you check that no quotas are in effect?

I will release a patch where the plugin will write out relevant error messages in the case, where DB inserts fail. This should shed some light to your situation.

In the meantime, could you please check the disk space that your DB takes up and let me know what you find?

kind regards

Thank you so much for the great review!

I will continue to support and improve this plugin and its extensions.

kind regards
Alex