[Sangita Support Squad]

Hi there,

Thank you for getting back to us and for sharing the details.

We have reviewed the information you provided. Regarding the store page loading issue, I have already shared it with our development team for their review.

As for the console errors, we have logged the issue in our GitHub repository, and our team will work on implementing a fix. Once the fix is available, we will keep you updated. In the meantime, you can also track the progress of the issue here: https://github.com/multivendorx/multivendorx/issues/2072.

Regarding the issue mentioned in point #2, it appears that the video link is currently inaccessible on our end. Could you please share an updated or accessible video link so that we can review the issue and assist you further?

We look forward to your update.

[Sangita Support Squad]

Hello,

Thank you very much for your valuable suggestion.

I have already forwarded your feedback to our development team for review. They are currently working on the integration for the Persons & Resources tab and will also evaluate the custom field addition workflow to determine the most suitable approach that aligns with the overall product experience and enhances the global functionality.

We truly appreciate you taking the time to share your ideas and feedback with us.

In the meantime, if you have any further questions or need any assistance from our end, please don’t hesitate to let us know. We’re always happy to help.

[Sangita Support Squad]

Hi there,

Thank you for getting back to us.

Regarding the Product Category widget, we have already addressed this in our previous reply.

As for the issues with the menu and breadcrumbs, we have already reported them to our development team. They are currently working on a fix, which will be included in an upcoming update. We will keep you informed of any progress and share updates as soon as they become available.

Additionally, we were unable to reproduce the console error on our end. Could you please let us know on which page(s) and under what circumstances you are encountering this error? Any additional details or screenshots would be greatly appreciated and will help us investigate the issue further.

We look forward to hearing from you

[Sangita Support Squad]

Hello there,

Thank you for sharing the information.

To help us better understand your requirement, would it be possible for you to share a screenshot indicating exactly where you would like this functionality to be implemented? Having a visual reference will give us a clearer understanding of the workflow you’re aiming to achieve.

Once we have that information, we’ll be able to discuss it with our development team in greater detail and work towards identifying the most suitable approach for the implementation.

We appreciate your cooperation and look forward to your update. If you have any additional details that might be helpful, please feel free to share them as well.

[Sangita Support Squad]

Hi Juane,

Thank you for getting back to us and for sharing your thoughts. We truly appreciate your patience and continued support.

With **MultiVendorX 5.0 & MultiVendorX 2.0**, our goal has been to make the plugin more versatile by incorporating many commonly requested features directly into the core functionality. We aim to provide a smoother and more flexible experience while reducing the need for customizations wherever possible.

At the same time, we also strive to ensure that custom code does not interfere with the plugin’s default workflow or create compatibility challenges during future updates. That’s why we encourage users to discuss their requirements with us first. Our development team carefully evaluates every request and, whenever it addresses a broader use case or benefits a wider range of users, we make every effort to implement it as part of the core plugin rather than relying on custom hooks or filters.

With that in mind, we’d be grateful if you could share a bit more about the customization flow you had previously implemented. Understanding your specific use case will help us better evaluate your requirements and guide you toward the most suitable solution.

We sincerely appreciate your cooperation and look forward to learning more. Please feel free to share any additional details, and we’ll be happy to assist you further.

[Sangita Support Squad]

Hello,

Thank you for reaching out.

We’re pleased to let you know that support for the Persons and Resources tabs for accommodation products is already on our roadmap. We hope to include them in one of our upcoming updates.

As soon as these features are implemented and available, we’ll be sure to keep you informed.

Thank you for your patience, support, and cooperation. If you have any further questions or suggestions, please feel free to let us know.

[Sangita Support Squad]

Hi there,

We reviewed the information you provided, and the mismatch you’re experiencing between the vendor stores and the total number of vendors after the upgrade is quite unusual. Since we have not been able to reproduce the issue on our end, we would like to investigate it further to identify the root cause.

Could you please share the following with us?

* Your staging site URL
* Temporary WordPress admin access
* Temporary FTP access

With this information, our team will be able to examine the issue directly on your site and assist you more effectively.

Also, when sharing the access details, please make sure to mark your reply as **private** so that your credentials remain secure.

We look forward to hearing back from you.

[Sangita Support Squad]

Hi there,

First of all, we sincerely apologize for the inconvenience and confusion caused.

We investigated the license activation issue and identified the cause. It turns out that this is not actually a problem with the plugin itself.

For staging sites, license activation is not required. Licenses are only intended to be activated on live/production sites. Because of this, the behavior you experienced on your staging environment is expected.

You can continue testing the plugin on your staging site without activating the license. Once you’re ready to deploy to your live site, you can activate the license there as usual.

To help prevent similar confusion in the future, we will also discuss adding a clearer indication within the plugin when it is running on a staging environment.

Once again, we sincerely apologize for the inconvenience this caused. If you have any further questions or encounter any other issues, please don’t hesitate to reach out. We’re always happy to help.

[Sangita Support Squad]

Hi there,

Thank you for getting back to us and for sharing the details.

Kindly allow us some time to review the information thoroughly. We will get back to you with an update accordingly.

Thank you for your patience and understanding.

[Sangita Support Squad]

Hi there,

We’re sorry to hear that you encountered this issue after updating to the latest version.

Our team has already been able to reproduce the problem and has logged it on our GitHub repository. The development team will work on implementing a fix as soon as possible. You can also track the progress of the issue here:

https://github.com/multivendorx/MultiVendorX/issues/1981

We’ll keep you updated as soon as the fix has been implemented.

Thank you for your patience and understanding.

[Sangita Support Squad]

Hi there,

Sorry for any confusion.

When we refer to the Product Category Widget, we mean the widget available under the MultiVendorX Store Sidebar section. You can refer to this screenshot for reference:
https://www.awesomescreenshot.com/image/61295648?key=9549272d8cf7637f2d5d202fa604723f

Once you add this widget on your end, the product categories will be displayed in the store sidebar as shown here:
https://www.awesomescreenshot.com/image/61295664?key=56bcc5d0adb350624a5c1d585df758f7

If anything is still unclear or if you have any further questions, please let us know. We’d be happy to assist you further.

[Sangita Support Squad]

This does seem unusual.

Could you please try deactivating MultiVendorX Pro and then activating it again? After that, check whether you’re able to activate the license successfully.

If the issue still persists, please share temporary admin access with us so we can investigate it further and assist you more effectively. When sharing the credentials, kindly mark your reply as private to keep the information secure.

We look forward to your update and are happy to assist further.

[Sangita Support Squad]

Just following up on the vendor migration issue—could you please let us know if there are any specific checks we can perform to identify why these particular vendor accounts were not migrated successfully?

[Sangita Support Squad]

Hi there,

Thank you for sharing the detailed information.

Regarding the Product Categories widget, this is the expected behavior. When a user clicks on a product category widget, they are redirected to the page displaying the products belonging to that category.

As for the other issues you’ve mentioned, such as the loading time, menu behavior, and breadcrumb display, could you please test your site using a default WordPress theme like Twenty Twenty-Five or Storefront and check whether the same issues persist?

We will look forward to your update.

[Sangita Support Squad]

Hi Kevajo,

Thank you for sharing the details about your migration run and your findings.

Based on the information you’ve provided, the issue appears to be related to these specific user accounts rather than a functional problem with the MultiVendorX migration process itself.

In MultiVendorX versions prior to 5.0.0, vendors were assigned the dc_vendor role. During the upgrade to MultiVendorX 5.0.0, vendors created through the standard MultiVendorX vendor registration flow are automatically migrated to the new Store Owner role.

Since the migration has worked successfully for the majority of vendors on your site and only a specific set of users continues to be affected, this generally indicates that those particular accounts may not have been created through the default MultiVendorX workflow.

In such cases, the users may have been added through custom code, a third-party integration, manual database modifications, or another custom process. Because the migration utility is designed to recognize vendors created through the standard plugin flow, it may not automatically migrate accounts that do not match the expected structure.

We therefore recommend reviewing how these specific vendor accounts were originally created and checking whether any customizations or manual processes were involved.

As this appears to be a user-specific data issue rather than an issue with the migration functionality itself, our support team is unfortunately unable to perform detailed debugging or database-level investigations for these custom-created records. If you require assistance with this, you may reach out to our Custom Development team (https://multivendorx.com/custom-development/). They can review your custom implementation, investigate the underlying database structure, and provide guidance or a tailored solution based on your site’s specific setup.

[Author]

Posts