[alexg]

@scorza420 Thank you. That’s true, the UIs are most easily customizable with CSS.

Additionally, some basic styling can be done via the Customizer menu.

@ncury1 It depends on what you’re trying to do. The easiest thing to do is use Customizer or apply some simple CSS. It is also possible, but harder, to modify the markup. For a complete list of things you can do, please consult the FAQ under “I don’t like the built-in forms. Can I change them or provide my own?”

Please let me know if you have any questions about this.

with regards

[alexg]

OK thank you for the additional information.

If this warning is all you see in the JavaScript console, then there is no error, the shortcode is working as intended. Additionally, I could not reproduce the issue on my end.

The dynamic shortcodes require a selected market, therefore at least one of the [wallets_exchange_market] templates must exist on the same page. If you’re using the static templates, it’s best to only stick to those.

I am in the middle of optimizing the frontend, so that only the code and data that’s actually needed in each page is loaded. This is a coordinated effort that has to affect all components, so I’m trying to release the changes in a sequence that will not affect users. This will be rolled out over the coming months.

Glad you found a solution to your issue.

with regards

[alexg]

Hello,

Thank you for the information!

When an admin registers a deposit, it is already possible to enter the transaction ID, amount, and a message. What is missing is the date of transaction (which can be different from the date on which the admin enters the transaction, via the tools menu).

Unfortunately it is not easy to add fields to the DB record with the current design. The schema is built for cryptocurrencies and I’ve already been trying to fit a square peg into a round hole with this fiat adapter. I will change the admin text to indicate that the admin should also enter the transaction date in the comment text.

The same is true for the admin withdrawal tool, the admin can enter a transaction ID and edit the message, while the user has already entered an amount. The actual bank transaction date is missing but can be added in the comment text as well.

I hope this will be sufficient.

with regards

[alexg]

Hello,

Thank you for letting me know.

I assume you upgraded the Exchange directly from 1.1.0 to 1.1.2, because there is nothing in 1.1.1 that could cause this issue.

Could you please tell me the following:

1. Are you running the latest version of wallets, 4.4.8?

2. What errors do you see in the JavaScript console while logged out?

thank you

[alexg]

Hello,

That’s a good question! Chances are good! This new type of coins are possibly the future of crypto, and would be a nice addition to the plugin.

I have already played with the grin wallet, and it should be possible to develop a coin adapter for this and similar coins.

Right now I’m very busy with the upcoming 5.0.0 release of wallets. Once this is done, I have to decide between working either on grin, or a game of chance, which many users request.

Eventually I hope to do both.

I will post here and on the blog if I have any news about this.

with regards

[alexg]

Hello,

Oops I think I know why this happens, and it’s a mistake on my part.

The code that does the export is this: https://github.com/dashed-slug/wallets/blob/4.4.8/includes/adapters-list.php#L29-L78

A file handle is opened here: https://github.com/dashed-slug/wallets/blob/4.4.8/includes/adapters-list.php#L38

And the data is written out to the file handle here: https://github.com/dashed-slug/wallets/blob/4.4.8/includes/adapters-list.php#L76

But I never called fclose().

My apologies for this, I feel like this is such a rookie mistake! I will of course fix it on the next release.

In the meantime, you can go to wp-content/plugins/wallets/adapters-list.php and add it between lines 77 and 78:

		fputcsv( $fh, $row, ',' );
	}
	fclose( $fh ); // this line was missing!
}

This must be it. The fix will go into the upcoming wallets release. Please let me know if you can’t edit the file or if you continue to face this issue for any reason.

with regards

[alexg]

Hello,

The transactions that you see in the “Wallets” -> “Transactions” screen are stored in the wp_wallets_txs table. The export functionality dumps the data into CSV files, but replaces user ids with user emails. This helps when you migrate your data to another installation with different database IDs. As long as users use the same email in your new system, they should be fine even if they have different user ids. If you don’t care about migrating the data to another server, then you might as well use mysqldump or phpmyadmin to export this table. The wp_wallets_txs.account and wp_wallets_txs.other_account columns are WordPress user ids (you can join them with the wp_users.ID key).

From your description, I am not sure what the problem is. To be clear, you used the “Export” link from the coin adapter pages and you got a CSV file, which was working fine before, but now the new CSV export does not contain any new transactions? Also what do you mean by “registration is not displayed in the usual way”? What exactly is missing from the exported data?

Please describe the problem in more detail so I can help.

with regards

[alexg]

please repost the images

[alexg]

Hello,

I have performed analysis on this, and I will be implementing QR code scanning, hopefully in the next release of the plugin.

Regarding sharing a deposit address, you can either share the string (there is a copy button next to the address, in the [wallets_deposit] shortcode, and the QR code is displayed by default. If you believe there is an issue with this, please open a new thread. This thread is for scanning QR codes for withdrawals.

with regards

[alexg]

Only the name, port, and symbol are actually necessary.

If you don’t have explorer URIs then set these to false or empty.

The other options you set, should appear as defaults when you enter coin adapter settings via the admin. (These defaults currently don’t work very well, but I have prepared a fix for this, and I will be uploading it within this week.)

with regards

[alexg]

Hello,

First of all congratulations for setting up a Monero node. It’s somewhat complex, but if you’re seeing addresses, then I don’t think you’re doing anything wrong.

That the one address you see per site is a main deposit address for the site (cold storage deposit), while the deposit addresses that your users are assigned are subaddresses. This helps the adapter organize addresses. If you check the cli for subaddresses you should be able to see them.

In a multisite install, each blog is mapped to one account index. On a single-site install, you will find your addresses, under the first Monero account. The label of each Monero account is the home url of the site. So you will find the user deposit addresses as subaddresses to this account.

Most wallets should be able to send to subaddresses if they are fully compatible with Monero.

with regards

[alexg]

Also check this guide: https://www.dashed-slug.net/howto-debug-an-incoming-deposit-full-node-wallet/

[alexg]

Hello,

My apologies, I should have provided a longer explanation for why I am not doing this.

The WCMp code is very complex (and somewhat buggy), and it is not built with an API that will let you extend it towards other payment gateways, as WooCommerce is. The documentation is aimed at end-users, not developers. I had to do a significant amount of reverse-engineering to get it to work as it is.

As you correctly pointed out, withdrawals were not being recorded when they were being applied automatically. When commissions are approved manually by an admin, the withdrawals are being recorded. This is not something that I want to debug any further.

I am not comfortable selling and providing support for code that I cannot trust. This is not how professional software engineers work. The products I sell cannot be based on knowledge acquired through reverse-engineering, because then they are not reliable. I was wrong to attempt this.

My initial reaction to all of this was to consider decommissioning the WCMp gateway altogether. However, the gateway currently does work when the admin is manually confirming commissions, so I have decided against removing WCMp support at this time. I have instead added a warning that users should disable automatic disbursal.

You are asking me for guidelines on how to do this yourself. If I had done the analysis required to know this, then I would also be able to implement it myself. 90% of the time goes to analysis and testing, not to implementation. Coding is the easy part.

If it turns out that I have to do any more ugly hacks to support the plugin, this will be an endless mess that will never end, and I will not be able to focus on any of my other work, for a plugin that is essentially not interesting to many users. In that case, I will have to remove WCMp support altogether.

with regards

[alexg]

Hello,

Unfortunately the plugin only works with coin symbols being unique.

In your situation, I would recommend that you create different coin symbols, so that if your symbol is ABC, then create something like ABC and ABC2, ABC and ABCOLD, or ABC and ABC2, or something like that.

If you absolutely need to use the same symbol for both coins, then how are your users going to differentiate between the two? Only by the coin’s icon? You need to explain to your users why they have two different balances on what appears to be the same coin but is actually two coins.

In any case, here’s an ugly hack that I thought of just now: You could maybe use a non-printable Unicode character, such as the zero-width space, in the old coin’s symbol string: https://en.wikipedia.org/wiki/Zero-width_space

I am not saying that this is a nice solution; it will probably create confusion, so it’s up to you to decide if you want to do this. If you do, at least make sure that the two coins have different icons, because this will be very confusing for your users otherwise.

The two coins will be different for the system, but users will be seeing the same symbol on their screens.

I hope that this helps you, and that it doesn’t create a big mess! Please test it before deploying on production.

with regards

[alexg]

Hello,

The following is generic bitcoind info (not specific to this plugin):

8332 is the default Bitcoin port for the RPC API, and 8333 is the default P2P post. For the purposes of communicating with WordPress, we are interested in the RPC port, i.e. 8332. Port 8333 should be open to let the wallet communicate with other wallets. Incoming connections to your wallet should be allowed on these ports, and that means that any firewalls that are in place should be open to the internet. You can use this tool to check: https://www.canyouseeme.org/

You mentioned a router. If you are on a home network, you will need to enable NAT on your router. i.e.: You need to add a rule that says that incoming TCP connections to 8332 or 8333 will be redirected to the 8332 or 8333 ports of your machine on your local network. Your machine on your local network will have a local IP that will most likely begin with 192. Your ISP cannot do this, only the person who is managing the router can. How you do this will depend on the exact router model and will be explained in the router’s manual.

Please understand that what you are doing is non-standard. I did not include any of the above information in the guide, because most people who install a full node will either already know networking, or would not be installing the wallet behind a local network; the usual setup is with an internet-facing server. I might create another guide on how to setup a full node on a local private network.

In any case, what you are trying to do is doable. Check your port first, to see that it is open from the machine that runs WordPress. Once this is done, then you can configure the coin adapter.

with regards

[Author]

Posts