[alexg]

@Sirbenky Hello, thank you for opening a new thread, we’ll track the issue there, as it’s probably a different issue.

[alexg]

Hello,

This is expected behavior. The plugin’s DB is a ledger that reflects transactions that the wallet knows about. These transactions are associated with WordPress users, and they include deposits, withdrawals, and any internal (off-chain) transactions.

Since you restored the entire DB from a backup, any transactions since that time will be lost. The plugin cannot simply “restore” transactions from your wallet, because the wallet doesn’t know about association between any transactions and actual WordPress users, and the wallet does not know anything about off-chain transactions.

Plugin transactions are stored in the wp_wallets_txs table, and user deposit addresses are stored in the wp_wallets_adds table (assuming you have the default DB table prefix, wp_. You can use phpMyAdmin or mysqldump to export these into a separate backup. Mysqldump can be automated via unix cron to help you keep daily backups.

with regards

[alexg]

Hello @Sharpraba,

This error indicates that your full node coin adapter cannot connect to your wallet. You should first check where your wallet is installed.

Since 192.168.* is in a private address space (https://en.wikipedia.org/wiki/Private_network), this is probably an address on your local network. If your webserver is on a hosting provider, you will not be able to connect to a local wallet (without setting up NAT and using a static IP). It’s best to run your wallet service on a fully managed host and use its public IP address.

On the other hand, if you are running the plugin locally (such as on an integration/test server), then it’s ok to connect to a local wallet on the same network.

In general, your WordPress server should be allowed to connect to your wallet server via TCP to the port that you’ve specified.

Since you’re installing a full node wallet, see the relevant article: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/installation-instructions/

If you are NOT certain that you need to setup a full node, please see an introductory article about the different types of coin adapters available: https://www.dashed-slug.net/howto-choose-between-available-coin-adapters/

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

with regards

[alexg]

Hello,

Glad that you resolved the issue.

The error regarding port 9150 means that the plugin cannot connect to your local tor service. Are you running tor on your web server? If not, then it won’t work.

Using the three exchange rate providers that you mentioned should be more than enough. In general you should be using the least amount of providers that covers all of your coins. You only need fixer.io if you need the exchange rates against fiat currencies.

with regards

[alexg]

Hello again,

I have added debug prints into the latest version 2.1.1 of the extension.

1. First enable debugging. Then, view a custom post. Either the UI will be shown, or you will get an error message in the debug.log file, explaining why the UI was not shown.

2. Let me know if you got a chance to test again with CMB2 disabled.

3. This could also be an issue related to the theme. Let me know if you tested with a different theme.

with regards

[alexg]

I have now provided an alternative fix for empty payment ids in version 0.1.4-beta. Since the payment ID is an optional parameter, the adapter will not pass the payment id value if it’s empty or null.

with regards

[alexg]

Hello,

I have used this fix in the latest version 5.0.9 of the wallets plugin.

Just make sure to keep your MySQL DB in the same timezone as your WordPress settings. I was not able to fix the timezone issue at this time. I evaluated several solutions but with each one, too many things could break 🙂

with regards

[alexg]

Hello,

With the latest version 5.0.9 of the plugin, internal transfers now always trigger a notification email. Therefore, the tips will trigger the usual notification messages.

Thank you for spotting this issue.

with regards

[alexg]

Hmm, that’s a weird one.

The fact that even after reverting to the previous version the problem remains, means that this is probably something else.

What I can do, is add a few debug prints in the logic that controls when the UI is shown. Then you can enable WordPress logging and see what’s going on.

I will do this soon and let you know.

In the meantime, please try with some plugins disabled, particularly CMB2 if you have it installed, and tell me please if you see any difference.

Finally, the ids and classes that you found in your console should have some context. Is this part of an error you see? How come this information is in your console? If possible can you show me a screenshot of where you found this information?

with regards

[alexg]

OK, again thank you for spotting this issue.

Did you get this after entering a withdrawal without any Payment ID?

If the solution works for you, then go ahead and use it for now. I will add a similar guard clause to the next patch.

with regards

[alexg]

Yep, you were absolutely correct. There was a typo in there. I have now released version 0.1.3-beta where this is fixed. I have set the number of decimals for 2ACoin to 8 (previously was 4). I am not sure if this is correct, since block explorers seem to show the decimals set to 4. In any case, you can now modify this value using the WordPress filter.

Many thanks for spotting this bug.

[alexg]

I will investigate this using TurtleCoin and get back to you.

[alexg]

That’s great.

Keep in mind that, if your PHP and MySQL servers are in different timezones this can create problems.

Before releasing a fix I will look into whether I can do something about this.

But this solution should work for you for the time being.

with regards

[alexg]

Hello,

Unfortunately this would be extremely hard with the current design. The UI works by using the JSON API, and the frontend JavaScript does not get loaded if the user is not logged in. Altering this would involve big changes to the parent plugin and this extension.

Again, since you seem to have so many ideas on what to develop, you really should hire a developer and provide specs on what you require. My recommendation is that you draw up a requirements document, and then shop around for people who would be willing to implement your product.

I can provide assistance on how to interface with the wallets plugin.

with regards

[alexg]

Hello,

I do not know why it doesn’t work.

1. Again, since I have changed nothing else besides the new capability, this has to do with the capability. Go to your author and assign the receive_tip capability directly, (i.e. directly to the user, not to the user role). Also, go to the user you use to visit the post, and assign the tip_the_author capability directly to the user (not the user role). Does this make a difference?

2. What do you mean by “it works by times and others not”? What changes between tries? Please provide as much information as possible so I can reproduce the issue.

with regards

[Author]

Posts