[Anushka Sinha]

Hi there,
Thank you for your understanding. We’ll keep you posted with any updates.
Let us know if you need any further assistance .

[Anushka Sinha]

Hey there!
Just a reminder – we’re still waiting for the FTP access details. Kindly share them at your earliest convenience so we can proceed with the investigation.

Kindly make sure to mark your reply as private when sharing sensitive information.

[Anushka Sinha]

Hi there,
Just a quick reminder – we’re waiting for you to replicate the reCAPTCHA issue and deactivate Jetpack, as it’s affecting access to the vendor dashboard on the staging site. Once that’s done, we’ll be able to investigate further.

Looking forward to your update.

[Anushka Sinha]

Hi there, Thank you for reaching out to us.

You’re absolutely right. There is currently an issue with the store name field when vendor approval is set to manual. However, when the approval is set to automatic, the store name entered by the user is saved correctly without any issues.

We’d like to share that we’re in the process of a major revamp of our plugin’s core structure, and this particular flow will be properly addressed in the upcoming release.

In the meantime, for users who are using the manual approval setting, we’ve created a temporary workaround. This patch ensures the store name is saved correctly by forcefully overriding the metadata. That said, we do not recommend using this workaround unless absolutely necessary, as it is not an ideal long-term solution.

If you still wish to proceed, you can download the temporary plugin from the following link: https://github.com/user-promi/MultiVendorX/archive/refs/heads/store-name.zip and follow the below steps –
– Delete the installed MultiVendorX via wp-admin >> plugin
– Unzip the GitHub plugin
– Rename the folder as “dc-woocommerce-multi-vendor” and Now, zip this folder again.
– Install this plugin on your site.

Please note that this workaround is only applicable for manual approvals and will not work if you’re using automatic approval.

We truly appreciate your patience and understanding as we work towards improving this flow in the upcoming version. If you have any further questions, feel free to let us know.

[Anushka Sinha]

Hi there,

Just a quick update – we’ve included a fix for the translation issue with Loco Translate in our latest version of MultiVendorX.

Kindly update the plugin to the latest version and check if everything is working as expected on your end.

If you run into any further issues, feel free to reach out – we’re happy to help!

[Anushka Sinha]

Hi there,
Thank you for your patience.

To modify the image cropping behavior for the vendor store cover, please add the following updated code to your theme’s functions.php file:


add_filter('mvx_frontend_dash_upload_script_params', 'custom_mvx_crop_options');
function custom_mvx_crop_options($image_script_params) {
$image_script_params['cover_ratio'] = array(1600, 900);
return $image_script_params;
}


If you need any further assistance, feel free to let us know.

[Anushka Sinha]

Hi there,
We’ve added a fix for the issue regarding “vendors REST API endpoint “. This fix is available in our GitHub version.
You can download the file from the following link and test it on your end: https://github.com/user-promi/MultiVendorX/archive/refs/heads/new-vul.zip

We’ll also include this fix in our next official update and we will keep you posted accordingly.

If you need any further assistance, please don’t hesitate to let us know. We’re happy to help.

[Anushka Sinha]

Hi there,
I hope you’ve been able to implement the appropriate filters and that your custom product types are now functioning as expected.

We’ll go ahead and close this thread for now. If you encounter any further issues or have questions, please don’t hesitate to create a new thread – we’ll be happy to assist you!

[Anushka Sinha]

Hi there,

We’re waiting for the FTP access to proceed with resolving the issue. Kindly share it at your convenience so that we can assist you further.
Kindly make sure to mark your reply as private when sharing sensitive information.

[Anushka Sinha]

Hi there,
We’re waiting for the FTP access to proceed with resolving the issue. Kindly share it at your convenience so that we can assist you further.
Kindly make sure to mark your reply as private when sharing sensitive information.

[Anushka Sinha]

Hi there,
Thank you so much for your patience.

I wanted to inform you that MultiVendorX is currently going through a major backend and frontend revamp. The feature you mentioned has been added to our 5.0 milestone (you can track it here: https://github.com/multivendorx/mvx/issues/980 ).

Since this is part of a bigger update, we’re unable to commit to an exact timeline right now. That said, I’ll definitely keep an eye on it and do my best to get back to you as soon as there’s any progress or workaround available.

Really appreciate your understanding. Please feel free to reach out if you have any other questions in the meantime!

[Anushka Sinha]

Hi there,
Sorry to hear that the code didn’t work as expected on your end.

We’ve reviewed the flow again by testing the code on our end, and it worked as intended.
Now ,to investigate this further on your end and replicate the issue, we kindly request you to create a staging site (a clone of your live site). Once it’s ready, please share the following details with us:

– Staging site URL

– Temporary admin access

– FTP credentials

This will allow us to replicate the issue in your environment and troubleshoot it more effectively.

Please make sure to mark your reply as private while sharing sensitive information.

Looking forward to your response.

[Anushka Sinha]

Hi there,

We’re currently waiting for you to replicate the reCAPTCHA issue on the site you shared so we can investigate further.

Additionally, please deactivate Jetpack on the staging site, as it’s preventing us from accessing the vendor dashboard.

Looking forward to your update.

[Anushka Sinha]

Hi @garaj,

I wanted to inform you that we’ve successfully recreated and fixed the issue related to the “Bookings 404 error”.

Kindly update both MultiVendorX and MultiVendorX Pro to the latest versions to apply the fix.

If you need any further assistance, feel free to reach out to us.

[Anushka Sinha]

Hi there,

Thank you for the update. We’ll make sure to update the blog and fix the broken link , really appreciate you pointing it out.

If you need any further assistance, feel free to reach out. We’re happy to help!

[Author]

Posts