Alexander Holsgrove

Thanks @doofinder, looks good this end – svn, track and wpackagist have updated. Thanks again for sorting this.

Using version 1.7.0 I can only seem to get the plugin to work on the classic cart using the shortcode, so doesn’t look like it’s compatible at the moment.

Any response to this please?

Thank you, much appreciated. I will report back when the update is released and I can confirm everything is working our side. Thanks again.

I’ve also had the same issue. @takayukister – are you able to add a blank option to the dropdown – “please select…” which should resolve the issue?

As well as creating the 2nd form, you can manually edit the block markup to set the form ID / title. Fill in the # with your own values:

<!-- wp:contact-form-7/contact-form-selector {"id":####,"title":"####"} -->
<div class="wp-block-contact-form-7-contact-form-selector">[contact-form-7 id="#####" title="####"]</div>
<!-- /wp:contact-form-7/contact-form-selector -->

Hi Niklas,

Thanks for your response. I’ve commented here after seeing @twyvel had similar “payment pending” orders, but will raise a support ticket with our specific issues.

To add a little more information from our side, we were told by an Integration Engineer at PayPal that the issues would be fixed in the 1.4.0 release. We have now enabled logging via the plugin and are seeing the following error for each of the “Payment Pending” orders:

WARNING Failed to capture order. PayPal API response: [UNPROCESSABLE_ENTITY] The requested action could not be performed, semantically incorrect, or failed business validation. https://developer.paypal.com/docs/api/orders/v2/#error-TRANSACTION_BLOCKED_BY_PAYEE

As I said, I’ll raise a ticket to discuss the details further.

The plugin is developed by WooCommerce not PayPal, but interesting that you’ve had several “Pending Payment” issues. We have seen the same on our side and were advised by a contact at PayPal that the 1.4.0 release would resole this. Still seems to be an issue.

From your support ticket, is WooCommerce saying the issue is on PayPal’s side? Are you able to quote some of the reply please?

Care to share any useful details?

The developer is working on the plugin, but it may take time to release new updates. You could always contribute towards the plugin, as it’s open-source after all.

Rather than closing, could you please offer any assistance in resolving the issue? We are happy to add any debug lines. The code is deployed through git so something else must be failing either at server level or with the plugin.

Thanks for the reply @gt3themes. It’s not because of this I’m afraid because the site works fine when I run it on my local development area, using the same split WordPress core and “wp-content” directory. It’s a bedrock/roots inspired setup:

ABSPATH is defined properly, and points to httpdocs/wp which is where we have the WordPress core (wp-admin, wp-includes etc). httpdocs/app/ is the WP content path.

As I said, this isn’t an issue unless there are hardcoded paths in your plugin, rather than using the proper WP constants / methods?

In your code, require_once(ABSPATH.'wp-admin/includes/file.php'); does point to the right location for us httpdocs/wp/wp-admin/includes/file.php. I am happy to provide further debugging output to help work out the problem.

Thanks,
Alex

The container block issue is probably more of a WordPress problem – just in the same way it’s hard to select a group. You can simply click into one of the container elements, and press the up arrow to get to the container. I don’t see this as an issue with the plugin itself.

As for it working sometimes or not – sounds curious. Unless your page isn’t loading properly it should either work or not work, rather than being intermittent. What versions of WordPress and plugin are you using? What is the problem specifically?

Lastly – how is it a “poorly written plugin”? Perhaps you can contribute some better code?

Care to add some more details to that – how is it hard to use specifically, and what other blocks did it “crash”?

I have just seen this same issue. Running ACF Pro 5.8.7 and 5.8.9.

I have opened an issue on GitHub here: https://github.com/woocommerce/woocommerce/issues/24540

So this support topic can be closed rather than duplicating things.

Thanks