[Anushka Sinha]

Hi there,

Thank you for reaching out to us!

We’ve informed our development team regarding this enhancement , and they’ll begin working on it shortly. Kindly allow us some time—we’ll keep you updated as progress is made.

In the meantime, you can track the status of this request here: https://github.com/multivendorx/mvx/issues/980

Thank you again for your understanding and continued support.

[Anushka Sinha]

Hi there,

So happy to hear your issue has been resolved, it’s always a pleasure helping you out!

Your continued trust and engagement mean a great deal to us.

If you have a moment, we would greatly appreciate it if you could leave us a 5-star review here: https://wordpress.org/support/plugin/dc-woocommerce-multi-vendor/reviews/#new-post

Your support motivates our team to keep doing even better!

Thanks again for being such an amazing part of our community!

[Anushka Sinha]

Hi there,
Thankyou for your patience.

The issue with the suborder display can be resolved by adjusting a simple setting in your WordPress dashboard. Please follow the steps below:

1. Go to your WordPress admin dashboard
2. Navigate to Settings > Reading
3. Locate the ‘Blog pages show at most’ option (https://snipboard.io/loApeY.jpg )
4. Increase the number to your desired limit (e.g., 50 or 100)

After updating this setting, all suborders should be displayed as expected.

If you need any further assistance , let us know- we will be glad to help ..

[Anushka Sinha]

Hi @vassiring,

Thank you for sharing the details with us. We’ve forwarded the information to our development team, and they are currently looking into it. Kindly allow us some time , we’ll keep you updated on the progress.

[Anushka Sinha]

Hi there,

Thank you for sharing the logs. Unfortunately, we’re unable to view the attached file.

Can you please use an online tool to paste the log content?
You can try using Hastebin:(https://hastebin.com). Just paste the error details there, save it, and send us the generated link.

Alternatively, you’re welcome to paste the error message directly into this thread (without attaching a file).

Looking forward to your response!

[Anushka Sinha]

Hi there,

Thank you for sharing the details.

As you mentioned the issue is not occurring on the staging site and only on the live site, and also everything appears to be functioning correctly on our end, we recommend double-checking the reCAPTCHA configuration on your live site. Please ensure that both the site key and secret key are correctly set up.

If the issue still persists, we kindly request you to create a new staging site that is an exact replica of your live site and share the following details with us:
Staging site URL , Temporary admin access and FTP credentials.

Please remember to mark your reply as private when sharing this information to keep your data secure.

Looking forward to your response so we can assist you further.

[Anushka Sinha]

Hi there,

You can check the error logs by any of these these steps:

– You can enable the debug mode on your site. Once enabled, try to recreate the issue. The error message should appear on the screen or in the debug log file. Kindly share that message with us for better assistance.

You can follow this guide to enable debug mode: https://wpforms.com/developers/how-to-enable-debugging-in-wordpress/

– Or , navigate to WooCommerce > Status > Logs. There, you’ll find logged errors. Please select the relevant error log from the dropdown and share the error details with us.

Looking forward to your response.

[Anushka Sinha]

Hi there,

You can check the error logs by any of these these steps:

– You can enable the debug mode on your site. Once enabled, try to recreate the issue. The error message should appear on the screen or in the debug log file. Kindly share that message with us for better assistance.

You can follow this guide to enable debug mode: https://wpforms.com/developers/how-to-enable-debugging-in-wordpress/

– Or , navigate to WooCommerce > Status > Logs. There, you’ll find logged errors. Please select the relevant error log from the dropdown and share the error details with us.

Looking forward to your response.

[Anushka Sinha]

Hi there,
Thank you for the update.

Please let us know once the access is ready, and we’ll proceed accordingly.
Please make sure to mark your reply as private when sharing these details to keep your information secure.

[Anushka Sinha]

Hi @vassiring, Thanks for the update.
Not to worry. If you need any further assistance, we will be glad to help.

[Anushka Sinha]

This reply has been marked as private.

[Anushka Sinha]

Hi there,
Thank you for your continued cooperation.
As discussed earlier, you wanted to restrict vendors from receiving the “Processing” order status email, please find the relevant code snippet below:

add_action( 'woocommerce_order_status_changed', 'disable_mvx_vendor_order_email_for_processing', 98, 4 );
function disable_mvx_vendor_order_email_for_processing( $order_id, $from_status, $to_status, $order ) {
if ( ! $order_id || ! is_a( $order, 'WC_Order' ) ) return;
// Check if this is a parent order with MVX suborders
if ( ! $order->get_parent_id() && $order->get_meta( 'has_mvx_sub_order', true ) ) {
// Only run if to_status is 'processing'
if ( $to_status === 'processing' ) {
$vendor_orders = get_mvx_suborders( $order_id );
foreach ( $vendor_orders as $vendor_order ) {
// Mark the email as already triggered to prevent the original MVX function from sending it
$already_triggered = $vendor_order->get_meta( '_mvx_vendor_new_order_mail_triggered', true );
if ( ! $already_triggered ) {
$vendor_order->update_meta_data( '_mvx_vendor_new_order_mail_triggered', true );
$vendor_order->save();
}
}
}
}
}


Please Note: The code previously shared for triggering the “On-hold” email will send vendors a new order notification when an order is placed and this new snippet will restrict the mail for order status on ‘Processing’.Both snippets work independently.
If your goal is to:
– Allow the vendor to receive the “On-hold” email
– Restrict the “Processing” email
You can safely use both snippets together.
Let us know if you need any further assistance we will be happy to help.

[Anushka Sinha]

This reply has been marked as private.

[Anushka Sinha]

Hi there,

Thank you for your patience.

We’ve informed our development team about the issue, and they’ll begin investigating on this issue shortly. We’ll keep you updated as soon as we hear from them.

Kindly allow us some time, and we truly appreciate your cooperation.

[Anushka Sinha]

Hi @Cyan,
Regarding the issue where All Bookings redirects to a 404 page, we’d like to let you know that this issue have occurred in the latest version of the Bookings module.
Our development team has identified the issue and will be working on a fix. Kindly allow us some time- this will be addressed in an upcoming update.
We appreciate your patience and understanding.

Also , we are waiting for the admin access of the staging site to proceed with further troubleshooting regarding the Avada Theme issue. Kindly share it at your convenience so we can continue investigating the issue.
Please make sure to mark your reply as private when sharing any sensitive information.

[Author]

Posts