IoClaudio

Yes, thank you, I’ve seen it but it seems a project not longer maintained

After looking the code of other plugins I’ve solved in this way:

(function () {
  "use strict";

....
  const title = settings.title || "";
.....


  const Block_Gateway = {
    name: settings.id,
    label: wpElement.createElement(() =>
      wpElement.createElement(
        "span",
        null,
        wpElement.createElement("img", {
          src: icon,
          alt: title,
        }),
        "  " + title
      )
    ),

...
  wcBlockRegistry.registerPaymentMethod(Block_Gateway);
})();

• This reply was modified 2 years, 5 months ago by IoClaudio.

I’ve seen that the problem is that “starting with WooCommerce version 8.3, the Cart and Checkout Blocks are the default for new installations“.
So there are two way to solve the problem.

1. The first is to add the checkout block.
2. The second is to edit the page: Page->Checkout and disable the blocks in the checkout page.

Here some references to this issue:

• https://woo.com/document/cart-checkout-blocks-status
• https://wordpress.org/support/topic/custom-payment-gateway-is-no-longer-listed-in-checkout/

I’m sorry, but this issue can be ignored.

I was expecting a wrong behaviour from the payment_complete method.

It works well as before the update.

Please, ignore it.

Thank you very muc.

Claudio

Thank you for your answer.

Looking in the forum I found a solution that consists in the use of the filters: single_template and archive_template. In this way I can force the use of a certain template for a certain post type. I’ve tried it and it seems to work well. However I will look to template_redirect to see if it can help me. Thank you very much.

• This reply was modified 3 years, 3 months ago by IoClaudio.

Thank you for your advice.

I think to have seen some plugins use this way of creating post types, however I will follow the advice of using a hook.

cld

thank you