marashmallow

OK, thanks for your reponse!

Thanks! That’s useful to know.

Thanks for your reply. I hadn’t considered the wider underlying support necessary from WordPress itself for this feature. I note that someone tried making the case for adding es-419 as an included sub-domain here on make.www.ads-software.com, but received no positive response.

Thanks for your response. Unfortunately, there are several problems with the code you referred me to:

1. Since PHP 8, the function signature on line 148 must be changed from

public function wpmudev_is_unique( $num = '', $form_id, $form_field ) {

to

public function wpmudev_is_unique( $form_id, $form_field, $num = '' ) {

and accordingly also the function call on line 185.

2. The code stops a redirect from occurring.

3. A webhook call occurs but it doesn’t transfer the value of the hidden field. The value is still just the literal “submission_id”. This happens despite the fact that I can see a random string being entered into the database for the hidden field.

• This reply was modified 1 year, 8 months ago by marashmallow.

Excellent, thanks!

@mrclayton Following up on my earlier query, I’m now looking at the popup help message for setting “Capture Status” in WooCommerce > Stripe by Payment Plugins > Settings > Advanced Settings (see image). It explains:

For orders that are authorized, when the order is set to this status, it will trigger a capture.

This leads me to wonder if instead of capturing an authorized charge with the code you suggested above, it would be sufficient to just change the status of the order in WooCommerce, like the following, to be acted on by the “Capture Status” feature?

$order = wc_get_order( $order_id );
$new_status = 'completed';
$order->update_status( $new_status );

OK. Thanks for your help!

Thanks for the answer.

I notice that there’s an amout being passed to be captured. Does this mean that I can charge partial amounts multiple times up to the amount originally authorized?

Thanks!

@bycrik, thanks for your answer.

Is there a technical issue with External/Affiliate products for which you decided against allowing Tiered Pricing display on them? Or was this a product design choice?

I may have rejoiced too soon: the table consistently goes missing when the product type is set to “External/Affiliate product”, no matter the chosen location or tooltip/table choice in WC Settings.

Further notes: I played around with the “Table position” selector in WooCommerce, and the table started appearing in various places (when I reported the problem it was set to “Above buy button”).

Once I put it back to “Above buy button”, it DID appear.

So it appears that the issue has solved itself.

Thanks for looking into this.

remove the line that contains the token as it should not be exposed to the public

As stated earlier, this is already obfuscated, thanks.

I guess Revue have dropped the ball…

Thanks for the rapid response! And cool to see the detailed transaction log. I didn’t notice it before you pointed it out.

Here’s the result from attempting a Revue subscription registration (API key replaced):

Time	2022-02-05 18:42:09
Integration ID	2
Request Data	
{
  "url": "https://www.getrevue.co/api/v2/subscribers",
  "args": {
    "headers": {
      "Content-Type": "application/json",
      "Authorization": "Token token=\"uoUztZNsYdBJ8Qe8GB3vFCmuD9zigV8o\""
    },
    "body": {
      "email": "[email protected]",
      "first_name": "Atailawe",
      "last_name": "Marisbobo"
    }
  }
}
Response Code	401
Response Data	""
Response Message Unauthorized

I have verified that the API key in use by AFI is identical to the one provided by Revue in the account, at the bottom of https://www.getrevue.co/app/integrations.

Ivan, thanks for the rapid reply!