Bitcoin and Altcoin Wallets error

Hello,

Judging by your DB prefix, it looks like you may be on a shared hosting platform. It’s possible, although unlikely, that they don’t allow new tables to be created; you can check with them to see if you have CREATE TABLE rights.

If you have access to your MySQL logs, the error will be apparent there.

Alternatively you can go to your MySQL console or phpMyAdmin SQL console, and paste the following code: https://pastebin.com/GKyKVwdD

This will either create the transactions table with your prefix, or it will give you an error. Let me know what happens when you try this, and we’ll proceed from there.

with regards,
Alex

hello,

thanks for support.

Yes, i have an error:
A comma or a closed parenthesis was expected. (near “signed” at position 972)
Unexpected statement start. (near “20” at position 1056)
Unexpected statement start. (near “10” at position 1059)
Unrecognized statement type. (near “signed” at position 1063)

error in the page of plugins:

Bitcoin and Altcoin Wallets error

Bitcoin and Altcoin Wallets could NOT create a transactions table “H1S_wallets_txs” in the database. The plugin may not function properly.
Bitcoin and Altcoin Wallets error

The plugin may not function properly because at least one DB index was not found on the H1S_wallets_txs table. If this error message persists, please contact support and report this: Array ( [0] => stdClass Object ( [Table] => h1s_wallets_txs [Non_unique] => 0 [Key_name] => PRIMARY [Seq_in_index] => 1 [Column_name] => id [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [1] => stdClass Object ( [Table] => h1s_wallets_txs [Non_unique] => 0 [Key_name] => uq_tx_idx [Seq_in_index] => 1 [Column_name] => txid [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => YES [Index_type] => BTREE [Comment] => [Index_comment] => ) [2] => stdClass Object ( [Table] => h1s_wallets_txs [Non_unique] => 0 [Key_name] => uq_tx_idx [Seq_in_index] => 2 [Column_name] => address [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [3] => stdClass Object ( [Table] => h1s_wallets_txs [Non_unique] => 0 [Key_name] => uq_tx_idx [Seq_in_index] => 3 [Column_name] => symbol [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [4] => stdClass Object ( [Table] => h1s_wallets_txs [Non_unique] => 1 [Key_name] => account_idx [Seq_in_index] => 1 [Column_name] => account [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [5] => stdClass Object ( [Table] => h1s_wallets_txs [Non_unique] => 1 [Key_name] => blogid_idx [Seq_in_index] => 1 [Column_name] => blog_id [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) ) .
Bitcoin and Altcoin Wallets error

The plugin may not function properly because at least one DB index was not found on the H1S_wallets_adds table. If this error message persists, please contact support and report this: Array ( [0] => stdClass Object ( [Table] => h1s_wallets_adds [Non_unique] => 0 [Key_name] => PRIMARY [Seq_in_index] => 1 [Column_name] => id [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [1] => stdClass Object ( [Table] => h1s_wallets_adds [Non_unique] => 0 [Key_name] => uq_ad_idx [Seq_in_index] => 1 [Column_name] => address [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [2] => stdClass Object ( [Table] => h1s_wallets_adds [Non_unique] => 0 [Key_name] => uq_ad_idx [Seq_in_index] => 2 [Column_name] => symbol [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [3] => stdClass Object ( [Table] => h1s_wallets_adds [Non_unique] => 0 [Key_name] => uq_ad_idx [Seq_in_index] => 3 [Column_name] => extra [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [4] => stdClass Object ( [Table] => h1s_wallets_adds [Non_unique] => 1 [Key_name] => retrieve_idx [Seq_in_index] => 1 [Column_name] => account [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [5] => stdClass Object ( [Table] => h1s_wallets_adds [Non_unique] => 1 [Key_name] => retrieve_idx [Seq_in_index] => 2 [Column_name] => symbol [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) [6] => stdClass Object ( [Table] => h1s_wallets_adds [Non_unique] => 1 [Key_name] => lookup_idx [Seq_in_index] => 1 [Column_name] => address [Collation] => A [Cardinality] => 0 [Sub_part] => [Packed] => [Null] => [Index_type] => BTREE [Comment] => [Index_comment] => ) ) .

Hello,

If I understand correctly, once you entered the CREATE TABLE command you got an error. This could be because you copied the code in such a way that the quotes were mangled.

If you saw this issue after somehow migrating your site using some migration tool, then deactivate the plugin and activate it again. (The plugin normally creates all the tables and indices required on the DB, when it is activated. It’s possible that the import/export tool you used only copied the standard WP tables and not any custom ones. Or if you performed a full SQL dump it’s possible that the table was not migrated due to incompatible collations or character sets.)

In any case, I asked you to run the CREATE TABLE query manually to see if it was somehow incompatible with your version of MySQL. You entered the CREATE TABLE command in your SQL console, and you got a syntax error. It is possible that the quotes were mangled during copy-paste. Can you try again with the raw version of this pastebin? https://pastebin.com/raw/GKyKVwdD I have double checked that the syntax is correct, so if you get any errors here, please let me know again.

Any subsequent errors that you see are normal. The plugin requires two tables plus some indices to work correctly. The query I gave you will not fix the error, it’s only so we can understand what went wrong.

Ultimately one of two things must be true: Either
a. the plugin will create the tables successfully, or
b. there will be an error in your mysql.log file, corresponding to the time when you activated the plugin.

In conclusion:
1. Try deactivating/activating the plugin again.
2. Please check again to see if the CREATE query actually created the table in your DB.
3. Let me know if you see any error in your SQL console, immediately after entering the CREATE query correctly from the raw pastebin (i.e. NOT errors in WordPress).
4. If you find any errors in your mysql.log file around the time you activated the plugin, please share them with me.

Thank you.

with regards,
Alex

Hi,

no, any errors in Mysql query or console, but in wordpress same error! This is frustrating…No other plugins show this…

Hello,

Either the plugin will create all the tables successfully on activation, or there will be errors in mysql.log. Did you drop the table and then attempt to deactivate/reactivate?

If you like I can also log to your site and attempt to diagnose the problem. If you want me to do this please contact me by email.

with regards

sorry for late reply…
but where is mysql.log?
i dont know mysql…
I have domain in Register.it with wordpress installation and control pannel with mysql

Hello,

Most likely there is some restriction placed by your hosting provider on what you can do on the database.

Did you attempt steps 1-3 from my post above?

If your host is using cPanel, go to Databases -> phpMyAdmin. Instructions from your host are here. Then, go to the SQL tab to find the SQL console. What happens when you enter the create command?

Any errors will also be in your mysql.log. Your host will be able to tell you how to access the log. Usually it is in /var/lib/mysql/{SERVER_NAME}.err where {SERVER_NAME} is the name of your server. Your host may be able to tell you how to view this from cPanel.

with regards