Hi,
make sure there are no other plugins that are altering the checkout form/workflow. Try disabling the one by one until you find the interfering one. Try also to temporarily switch theme, it might be the cause as well.

In order to exclude any plugin malfunctioning, please use the following site: https://codecanyondemo.work/wcoa/wp-admin/ (user: demo, pass: demo) to recreate your scenario. Report me if you are experiencing the issue and if so, please report me a step-by-step guide on how to. Thank you.

Thanks, it seems that the theme is the problem. What can I do to fix this? Can you maybe assist?

I’m really sorry, I cannot provide assistance for 3rd party software that I haven’t designed. What I can suggest is to make sure that the theme sticks to the default checkout page. If it is implementing a custom checkout process, try to see if has any option to restore the original workflow (for example some themes allow to perform a multistep checkout but have an option to use the original checkout page template).

Are there any woocommerce checkout plugins that works with this plugin?

I haven’t directly tested any. Make eventually sure they are not altering the normal checkout workflow.

I managed to fix the payment gateway.

I want to use the Pay first and wait for approval option.

I deactivated the plugin for testing and the payment gateway opened perfectly.

Now I have activated the plugin again and it does not open the payment gateway anymore and gives me this message:

This order’s status is “Waiting for approval”—it cannot be paid for. Please contact us if you need assistance.

I am sure that I am not using the correct settings but there is not much info on the manual.

Can you please assist with these setting? Maybe a screenshot?

It seems that the plugin is not accepting the “Waiting for approval” for payment.

$statuses[] = 'approval-waiting';

and reperform a test. If it still doesn’t work, you need to contact that plugin help staff and ask how to extend it in order to accept custom order statuses for payment acceptance.

Thanks, on which plugin? Your plugin or on my payment gateway plugin?

on my plugin. the file is named Order.ph (you find it inside the classes\com folder).

Thanks, I inserted the code but still not working. here is a image of the settings that I am using. http://pintopin.co.za/wp-content/uploads/2023/06/settings-scaled.jpg

To ask for the support you need to renew your license.

meanwhile make sure you are running the latest 7.6 plugin version, that non of the 3rd party plugins you are using is not interfering with the email notification process, and that your server emailer is appropriately working.

I will ask my partner to renew.

Question: I am already using updated version.

If admin approve the order from admin panel, customer getting the notification to complete payment.

But admin not getting the email.

Yes, the plugin is designed to work in that way. If the admin approves an order only the customer get notified for that. there is no need to send a notification also to the admin that reports the action he just performed.

If the admin approves an order only the customer get notified for that

Currently Admin not getting email to approve the order/

The plugin doesn’t send any specific email to approve/reject, it injects the approve/reject into the “new order” email already sent by WooCommerce

But I am not getting the New Order email !

I paid for support. Can you help me now?

The new order email is sent by WooCommerce when an order is just placed, it is not sent or managed by the plugin.

Make eventually sure you have not disabled it via the WooCommerce > Settings > Emails settings menu.

When I remove the Order approval plugin I am getting the order email !

Can you please take a look in my website?

How I can send you website login?

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

Thanks, I am doing these step & updating you.

Which php version do you suggest? 8.0 ? OR 8.1 ?

Hi,
The Envato usage license policy allows you to use the software in only one end product (website), not one end product at a time. This means that the license cannot be migrated from one product to another.

Websites are uniquely identified by the associated domain. Once you register a domain that will become the end product for which you are licensed to use the software.

The plugin activation system, however, allows you to activate the license in two domains (the second one should be for testing purposes). In each domain, you can activate unlimited subdomains and subfolders.
If you consumed all these options, you need then to buy another license in order to be compliant with the Envato usage policy.

I guess you didn’t understand what I wrote.

We don’t want to use 1 licence on 2 different websites. We already have 2 licences for 2 websites. But as our client name changed we also changed the staging website domain. Now we can’t test your product because the 2 domains for that licence are in use (one on the public website and the other on a staging domain that is no longer in use).

Are you telling me that we would need to buy another licence to have it work on the staging website?

Which was the old staging domain and the new one? Note that the license allows you to use the license in only one production domain

Old staging URL was kettner.dev.intg.pt. New one is grouse.dev.intg.pt.

Client name change was finalised before the new website went live so we have the plugin registered to the correct public URL (grouse.pt).

Hello,
thank you for your appreciation. Actually the plugin doesn’t perform any particular action to send email, it just sends them via the WooCommerce emailer component (https://woocommerce.github.io/code-reference/classes/WC-Emails.html )

you can also check by yourself by editing the Email_Manager.php file you find inside the classes\com inside the plugin folder. The email is sent on line 83 by invoking the send() method (https://woocommerce.github.io/code-reference/classes/WC-Emails.html#method_send ).

I dont’ know how the WP Mail SMTP component inject its features to override the default email management. If you have any suggestion (try eventually contacting their support) I can improve the email sending aspect!

Thank you for your reply

I think I figured out why the approval emails are ending up as spam. the Reply-To address is different from the From address. The Reply-To address appears to be the email address for the person that placed the order. The From address is the address for the site admin. Emails with mismatched addresses are typically flagged as spam. Can this be changed somehow so these addresses match?

Thank you for sharing the result of your investigation. Seem strange because the WC_Emails component usually sets the Reply-To with the address used for the “from”.

I’ve however forced the Reply-To header to match the From address. Please try updating to the latest 7.4 version that I’ve just released!

Thanks so much for your quick reply! I upgraded to the 7.4 version and see the same results with the email formatting. The Reply-To is the customers email address and the sender email address is the site admin. Just to clarify, this is only an issue with approval emails. Notification emails sent to the customers seem to be fine.

Hi. You can already do that. Just edit the approval_area.php template you find inside the templates\frontend\ folder inside the plugin.

you can copy it into the \woocommerce-order-approval\frontend\ folder inside your theme. In this way, you can update the plugin without the need to restore your customizations.

here is a backtrace of what is executed at the early stage of the order in wait and pay mode, you should be familiar and understand what’s append… 1 /wordpress/wp-content/plugins/woocommerce/includes/class-wc-checkout.php(1076): WC_Order->payment_complete() 2 /wordpress/wp-content/plugins/woocommerce/includes/class-wc-checkout.php(1281): WC_Checkout->process_order_without_payment() 3 /wordpress/wp-content/plugins/woocommerce/includes/class-wc-ajax.php(481): WC_Checkout->process_checkout()

Hi,
I’m sorry, I do not understand. The woocommerce_cart_needs_payment reports to WooCommerce if the current order needs to be paid or not. This filter is triggered during the Checkout in order to display the payment area on the Checkout page.

The plugin hooks to that filter returning “true or false” according to the current payment workflow the user selects (pay and wait or wait and pay). In the case of “wait and pay”, no payment area is then displayed on the checkout page.

return $cart_needs_to_be_payment;

or just remove line 15.

What i understand is that in wait-and-pay mode (the mode i selected), the cart_needs_payment filter always return false, so woocommerce always execute process_order_without_payment() that execute payment_complete() before user start paying. On admin panel, the order is considered as payed. I think this is a side effect of using the woocommerce_cart_needs_payment filter to activate the wait-and-pay workflow, and that process_order_without_payment() should either no be executed as is (but don’t know how as it is wc code) or things like payment_complete() should be undo after that (eg. remove pay_date and order_note) The way i use the plugin is to set wait-and-pay as the default, but only for few products (that i define in settings) And i don’t want to patch your code as it is will be overwrite at the next update…

I’m really sorry, unfortunately there isn’t any other way to avoid the customer to pay the order on checkout (and avoid the payment area to be displayed on checkout page).

this isn’t what i said. Reading your code, i understand how you reach to add wait-and-pay workflow with wc code. What i said is that doing this way (and it is perhaps the only way to do that), there is a side effect : the order is flagged to be payed at the approved stage (because of execution of wc payment_complete() ) And so, the order has a bad paid flag at earliy step of order, and keep this paid flag, even if order is cancel later. This give a bad information in admin panel, as there is a text in the main metabox that say the order has been paid at a specific date Perhaps it could would be possible to unset date_paid and transaction_id in a post processing, or just add a filter on woocommerce_valid_order_statuses_for_payment_complete to prevent this whole wc code execution

Thank you for your suggestion. Actually, I did not notice that the paid date was set anyway in the case of the “wait and pay” strategy.

Please try updating to the latest 7.2 version. The plugin now hooks to the “woocommerce_valid_order_statuses_for_payment_complete” filter avoiding the paid date and transaction id to be set.