[alexg]

@Charles Hello, the Exchange extension is self-contained. You do not need to purchase access to any other extensions for a fully functional exchange. The other components you need are the parent plugin which is freely available from wordpress.org, and any coin adapters you need, all available for free from this site when you sign up.

To show the buy/sell boxes, use the shortcodes [wallets_exchange_limit_buy] and [wallets_exchange_limit_sell]. For a full list of shortcodes that you can use and their attributes, please refer to the documentation for the exchange. The documentation is the PDF file included in the bundle download of the exchange.

You also have the option of using the same UIs as widgets, it’s up to you which method you prefer.

@dynamitemedia Thanks, I believe the OP is showing screenshots from other exchanges to explain the buy/sell boxes.

with regards

[alexg]

Hello,

1. You say that you found the procedure above confusing. Out of the four steps, which ones are you having trouble with? I can help clarify. This is the correct procedure.

2. If you did not perform the above procedure, then what did you do? You say that you cleared the transactions table after migrating the database. This alone would create the problem you describe. You would need to reimport the exported csv files, then enable the new site once you are 100% sure that everything is correct.

3. I am not sure what user meta you are referring to. There are no user meta involved in this. The data is in the transactions table.

The plugin periodically rediscovers old deposits. If you have deleted a deposit row, eventually it will get re-discovered, and you might face the same problem again, until you perform the migration as described.

Please ask me any questions you need in order to understand the migration process. Then you can repeat the steps and I’m sure it will work.

with regards

[alexg]

Hello and thanks for paying for membership.

At first you had signed up for an EU tax exempt plan but the VATIN you provided does not check out on VIES, this is why you could not download. You have subsequently re-subscribed with a non-tax exempt plan and you should have access now. I will refund your earlier payment. If you have a valid VATIN for your business, please contact me again either here or via email and we can sort this out.

with regards

[alexg]

Hello,

To be clear, the user IDs (not the user names or user logins) can be different if you import them into your new MySQL because the id is an AUTO_INCREMENT column. If you have 100% certain that you have preserved all the IDs then there should be no issue.

The procedure I described above, with the intermediate CSV files is available so that you do not have to worry about IDs. The plugin normally associates transaction rows in the db with user ids. When the transactions are exported to CSV, the user ids (account column) are replaced with the user emails. Upon import, these are again replaced with the user ids, which can now be different, due to the behavior of AUTO_INCREMENT columns on MySQL.

I did not understand from your post. Did you perform this exact procedure?

1. Transfer the full WordPress backup to a new server.

2. Export the transactions to csv from the old installation, one csv file for each coin.

3. Clear the transactions table on the new installation (with DELETE or TRUNCATE commands)

4. Import the CSV file or files to the new installation.

If you have performed these exact steps and the problem remains, select a user whose balance is not correct and look at their transactions. How do they compare to their transactions on the old installation? Are there more transactions? Less? What’s going on?

[alexg]

Hello,

User balances are derived from summing all of a user’s transactions.

The transactions are attached to WordPress user ids. If you have migrated your site, the ids of the users are probably different now. Clear the new wp_wallets_txs table, then use the export/import feature to migrate the transaction data. The export feature is found in Wallets -> Adapters -> Export, under each adapter. This will create csv files where the users are uniquely identified by their email. The import feature is found in Wallets -> Transactions at the bottom of the page.

with regards

[alexg]

Hello,

1. Some users have posted their exchange sites here: https://www.dashed-slug.net/forums/topic/live-sites-powered-by-the-bitcoin-and-altcoin-wallets-wordpress-plugin/

2. A referral system is one of the things that are often requested but it has not been implemented yet. See:

referral program in Rheine Exchange?

If it is implemented I will post a notification in all the relevant threads.

with regards

P.S. I have moved your question to a new thread as it was not relevant to the other thread where this was posted.

[alexg]

This issue is now fixed in version 0.3.1-beta of the adapter. Thanks again for reporting it!

[alexg]

This issue is now fixed in version 0.3.1-beta of the adapter.

[alexg]

OK, I see the error too. This is a bug. I will fix this as soon as possible. Thank you for reporting. I will contact you again here shortly.

with regards

[alexg]

Hmm. Good point. This isn’t easy to do with the current architecture. The coin information is loaded from the parent plugin only when the user is logged in. I will have to think about this. Thanks for pointing this out.

[alexg]

Hello,

Thanks for the detailed description of the problem. It does sound somewhat surprising, since you say that the IPN message was successful.

Balances are not affected because the deposit transactions are not recorded. I assume this is a new installation since there are no transactions in the list. The question is, why would transactions not be recorded if the IPN message was sent successfully?

1. Please double check that the deposit address that you are sending funds to is the same as that shown in the plugin. You can check deposit addresses via Wallets -> Deposit addresses, or in the user profile screen for each user.

2. Enable the WordPress debug log, and resend one of the IPNs from CoinPayments. Do you see any error in wp-contents/debug.log? What about the PHP error log, or MySQL error log?

3. Is the status of the IPN message 100? If not, this is an early IPN message where the transaction is not yet confirmed, and there will be a subsequent IPN message with status 100. Only these IPN messages (with status>=100) are used by the plugin.

I really cannot think of anything else at this time. If the deposit address is correct and the IPN is successful, the deposit should be recorded, or if something unexpected happens, there should be some trace of the error in one of the logs. There is no other outcome that I can think of.

So please check all of the above and let me know.

[alexg]

Hello,
Error 502 means that the PHP service did not respond to your nginx, possibly because it was too busy. It’s way too general of an error to draw any meaningful conclusions. I would look around in the server logs for anything strange. Think access logs, nginx error logs, mysql error logs, etc.

Also, I would like to ask you the following:

1. Do you get the 502 error every time you follow the cron job link, or only some times?

2. Since you have enabled the WordPress debug log, do you see any other errors in the wp-contents/debug.log file?

3. Which coin adapter or adapters are you using? If you are using any RPC-API wallets, could it be that a connection is timing out due to some firewall?

4. Did you change anything around the time when this problem first occurred?

5. Go to the dashboard, and inspect all the debug info about cron jobs: Cron jobs last ran on, Cron jobs last runtime (sec), Cron jobs peak memory, Cron jobs memory delta. What do these read?

[alexg]

i can see that the site is generating adresses for mue and btc – but when transfering into those adresses – it dosent show up in user transactions as deposited. See screenshot..

Attachments:

You must be logged in to view attached files.

[alexg]

Hello,

This is expected behavior if you are not logged in.

The UIs are available to logged in users with the correct capabilities.

If you want to change the error message displayed, please consult the manual under Frontend -> Frontend UI WordPress filters -> Shortcode rendering error messages. This will give you instructions on how to use the wallets_ui_text_shortcode_error filter.

The manual is the PDF file in the bundle download of the plugin available here: https://www.dashed-slug.net/downloads/

If you are logged in and you still see this error, it is due to your server side cache settings. Simply exclude the page with the wallet shortcodes from your caching plugin.

with regards

[alexg]

Hello,

It wouldn’t be smart to open all ports. Firewalls are there for a reason.

As you found out, bitcoin wallets by default require *incoming* TCP connections to 8332 for the RPC API and 8333 for P2P communication. The plugin connects to the RPC API. You can always change these default numbers with the settings port and rpcport (see https://en.bitcoin.it/wiki/Running_Bitcoin ). This also means that *outgoing* TCP 8332 must be allowed from your WordPress site.

Best of luck with setting up the tunnel, let me know if you have any questions.

with regards

[Author]

Posts