sarmatopia

Managed to get the scan working by disabling proxying on Cloudflare.

I don’t know the long-term fix.

Main oddity with my setup (Nexcess hosting) is the SSL cert on the server is issued to a temporary domain name (subdomain of a Nexcess domain) and then our domain is an “additional domain” on the Let’s Encrypt cert. But that wasn’t a problem when Cloudflare proxying was off.

I wasted a day working on this problem because you mislead me.

I don’t have more time to waste explaining things to you. Your response shows it’s not worth trying.

We can talk next time there’s problem or “contribution” to make.

AWS SES code also needs:

require_once ABSPATH . WPINC . '/class-phpmailer.php';

Also interested on if this can be implemented: List-Unsubscribe: <mailto: emailAddress>, <unsubscribe URL>

https://www.ads-software.com/support/topic/list-unsubscribe-in-header/

I came to ask about List-Unsubscribe too. When I go to Gmail’s “Show Original” I do NOT see the header, and same behavior in another webmail tool. I’m using AWS SES add-on to send

You are correct, we were not on the latest version. But wp-admin/plugins.php did not have any notice of an update. How do we automatically check for updates?

I suggest maybe using wp_parse_args() on $wpsc_ticket_data/get_ticket and the other arrays used, probably within the functions before they’re returned.

That replace_macro.php file should just be part of the class-wpsc-functions.php rather than included. It makes it difficult to read the code to fix it.

I’m not sure what $ticket_data = json_decode(json_encode($ticket), true); is helping to do, i.e. if it were removed, would the array have default empty values? (I’m not sure).

Consider putting @ in front of the function call for warnings that can be ignored.

Thanks. We have no custom fields. Maybe it’s because we added SupportCandy Woocommerce Add-On recently.

All resolved, thank you very much!

Highly recommended.

I have discovered possibly part of the problem. I was testing on a staging site created with wp-staging plugin: https://www.ads-software.com/plugins/wp-staging/

This added an additional login across the entire staging site, including the REST API, so would return a HTML page with “You need to login to access that page” when you were POSTing to the return_url.

Unfortunately, I’m still getting the admin message “Bitcoin Payment Gateway requires wallet updates. Please update your Settings to benefit from recent security improvements.” I’ve updated to the latest version of your plugin.

I also tested in Chrome on MacOS but there was no difference.

I’ve updated my email address to the correct one.

I added some error_log() to triplea_handle_api_tx_update() but don’t see it being called by your server (although testing with Postman confirms the logging is working).

Thanks for the quick reply!

This error seems not related to the key, as Firefox says “Cross-Origin Request Blocked” (a HTTP security measure). When I add the key, the attempt by the browser (presumably the Tripe-A JavaScript) to use your API at https://moneyoverip.io/api/add_pub is blocked. The solution for that is either to add the correct CORS HTTP header or to perform the request server-to-server via wp_ajax_.

For reproducibility, I’m using Firefox 69.0.3 on MacOS.

And Jaxx does allow viewing the public keys through its own interface:

You can see all of the address/key pairs associated with your wallet at Menu > Tools > Display Private Keys.

https://support.decentral.ca/hc/en-us/articles/224342787-What-is-the-difference-between-a-public-address-and-a-private-key-

View post on imgur.com

The instructions you linked gave me the “Account Extended Public Key” which matched the Jaxx “Account” xpub key.

Now that I am re-testing I am not getting the CORS error but I am still getting the error message:

Bitcoin Payment Gateway requires wallet updates. Please update your Settings to benefit from recent security improvements.

I’m a reasonably skilled WordPress developer so let me know what you need and we can troubleshoot this together. I like your plugin (otherwise!).

It’s also unclear what key I should use. I created a wallet with Jaxx and it gives me three public keys, “Account”, “External” and “Internal”.