Nomiddleman Crypto

No follow up. Closing.

Question was answered. Closing.

No response. Closing.

The best way is using an MPK to make sure each order has a unique address, then that is the extra setting that can uniquely determine a sufficiently valued transaction has been made.

Hello!

Our apologies as the website is misleading.

We support Native Segwit and Segwit P2SH addresses for Classic Mode and Autopay Mode. For Privacy Mode we only support Legacy BTC addresses.

Since you mentioned you entered a Segwit P2SH address and not a Segwit P2SH master public key (also called MPK), you should be fine.

The transaction is signed based on the input address type (person that sends the transaction). This means that you get all the benefits of Segwit only when sending (as that is when you pay the fee and it’s added to the blockchain mempool). All addresses types can send to all address types. So a legacy address can send to a Native Segwit Bech32 address, however they won’t reduce their transaction size or anything else.

However, most (all?) wallets validate the receiver’s address to make sure you are not sending a transaction to an address that can not exist (you can still send a transaction to an address that “does not” exist.)

If one of your customers uses a wallet that either:

• Was created before Segwit was proposed
• Has not been updated since the wallet introduced Segwit support
• Has devs that never implemented Segwit

Then most likely the wallet will not be able to validate that the Segwit address can exist. Therefore the user will get an error and will not be able to send funds to your Segwit address.

This is probably pretty unlikely now as all major wallets have implemented Segwit and it might even be better (if you have a nice enough product) to force your customer to use a wallet that supports Segwit so we help weed out those users.

Cheers.

Hello!

Redux Framework is a settings framework we have embedded in our plugin.

Navigating 40+ cryptos with multiple modes in regular WooCommerce settings became extremely cumbersome. Therefore we opted to use a settings framework to improve the settings experience.

We embedded it so outside updates to Redux do not affect our plugin and it skips the step of requiring to install an extra plugin.

Sounds great! Please submit a pull request to our github repo and we can push the update when you are finished.

We have been looking over this issue. Can you please send an email to [email protected] as we will probably require debug logs to proceed.

Hello!

Please navigate to any order that had an issue displaying a privacy mode bitcoin address in the WooCommerce dashboard. Is there a custom field called “wallet_address” and does it have a bitcoin address as it’s value?

Did you check if you are getting the redirects as a regular user? Redux will be isolated to admins only, it does hook into the WordPress customizer like many other themes and plugins, so it will query and make requests on the backend.

Also, does it say ‘Developer mode enabled’ on the settings page under the title?

No worries if it does not work out, hopefully you find a solution that does!

We use redux framework for our settings page. Standard WordPress settings did not provide a user experience we were happy with. See https://www.ads-software.com/plugins/redux-framework/.

We know the lead dev personally and fully vetted the framework and source code before utilizing it as our settings framework.

Is this in your browser console?

It appears the theme is utilizing the $ variable for jQuery and not handling it correctly, see here: https://premium.wpmudev.org/blog/adding-jquery-scripts-wordpress/.
Maybe forward this link so they can fix it on their end.

Here is a fix you will have to do now and every time you update your theme:

Navigate to your wordpress directory
Navigate to \wp-content\themes\videopro\admin\assets\js\admin_template.js
Do a find and replace:
find – jQuery(document).ready(function()
replace – jQuery(document).ready(function($)

Or just add the $ variable to the jQuery(document).ready handler parameters on line 1, 189, and 306.

We can’t guarantee this fix does not break anything, but everything seems to be working okay after making this change on our end.

Cheers,
Nomiddleman Crypto

We will be setting up the theme today to check for the issue.

If you sent an email with a zip it might have been filtered before it reached us (checked spam as well).

Without their code the issue is hard to nail down, the theme is causing the plugin settings not to load and there are no errors related to our code.

We have sent a request to the theme developer to get this issue resolved.