[Sangita Support Squad]

Hi there,

Thank you for reaching out and for providing the detailed information. Our responses to your queries are provided inline below:

1. Is the store_id = 0 linking failure a known migration issue, and is it fixed in a newer release? We are already on the latest Free and Pro, and it is reproducible on a clean single migration.
2. Is there a supported way to repair / regenerate the commission-to-store links and rebuild store_users after migration, without creating duplicates?

>> You are the second user to report this issue to us about the store_id set to 0. Our team has already investigated it, but so far we have not been able to reproduce the behavior on our end. Without a reliable way to reproduce the issue, it becomes difficult for us to identify the root cause and implement a fix.

If possible, could you please share the exact steps or any specific trigger that consistently reproduces the issue? Any additional details, logs, or observations would be greatly appreciated and will help our team investigate and resolve it more effectively.

3. For both the admin and vendor lists, can the default ordering be set to newest-first, and are the sorting / pagination / date-filter behaviors known issues?

>> We have tested this on our end, and by default the listings are already sorted from newest to oldest. You can refer to the following screenshots for reference:

https://www.awesomescreenshot.com/image/61186784?key=91af8df65d3c17ec3d23af522feeb1d0
https://www.awesomescreenshot.com/image/61186795?key=6bbfb9e9b71cf65dbe715054d9a8e1f8

We also verified the pagination functionality, and it appears to be working correctly in our testing environment.

Since these behaviors are not reproducible on our end, could you please perform a quick compatibility check by temporarily activating only the default required plugins (WooCommerce, MultiVendorX, and MultiVendorX Pro) and switching to a default WordPress theme? This will help determine whether another plugin or the active theme is influencing the behavior.

Regarding the store_id = 0 issue, we would really appreciate it if you could share any additional information or a reproducible scenario that might help us replicate the problem. This will allow our team to investigate it further and work towards a resolution.

We look forward to hearing back from you.

[Sangita Support Squad]

Hi there,

We have already released MultiVendorX 5.0.0, which includes fixes for the issues you mentioned. You can update the MultiVendorX plugin to the latest version on your site and check.

Since MultiVendorX 5.0.0 is a major upgrade, we strongly recommend performing the update on a staging site first, especially if you’re upgrading from MultiVendorX 4.0.x to 5.0.x. This will allow you to confirm that everything is functioning as expected in a safe testing environment before applying the update to your live site.

Once you’ve verified that everything is working correctly on the staging site, you can proceed with updating your live website with confidence.

For additional guidance on the upgrade process, you can also refer to our documentation here:
https://multivendorx.com/release/.

If you encounter any issues during the upgrade or have any questions, please let us know. We’ll be happy to assist you further.

[Sangita Support Squad]

Hi There,

Thank you for getting back to us with the details.

After reviewing the situation, this appears to be an isolated case, as we have not received any report of store duplication from other users who have upgraded from MultiVendorX 4.0.x to 5.0.x.

Based on our analysis, this behavior seems to be related to a possible database inconsistency or corruption on your site, which may be causing unexpected data duplication during the upgrade process.

To move forward, we would recommend first addressing and resolving the database-level issue on your end. Once the database is stable and clean, you can proceed with the upgrade again.

If you have an in-house developer, they should be able to assist you in reviewing and fixing the database integrity. Alternatively, if you prefer, you may also reach out to our service team for assistance here: https://multivendorx.com/custom-development/ and they will be happy to help you resolve the issue.

Once the underlying database concern is resolved, the upgrade should work smoothly without any store duplication issues.

Please feel free to reach out if you need any further assistance—we’ll be happy to help.

[Sangita Support Squad]

Hi There,

Thank you for confirming and for checking again.

We’re glad to know that the translations are now working fine at your end and everything is available.

If you need any further assistance from our side, please feel free to let us know. We’re always here to help.

[Sangita Support Squad]

Hi there,

Thank you for your prompt response.

Regarding the translation issue, we look forward to hearing back from you once you have more information to share.

We also appreciate you bringing the capability checkbox selection under the User Capabilities section to our attention. We will review this and include an appropriate fix in the upcoming update.

Additionally, we’d like to keep you informed that the Store Owner capabilities listed under User Capabilities are synchronized with the Store Permissions settings. This means that once the store permissions are configured, the corresponding capabilities will be automatically assigned to the Store Owner role.

In the meantime, if there is anything else we can assist you with, please don’t hesitate to let us know. We’re always happy to help.

[Sangita Support Squad]

Hi there,

Thank you for getting in touch with us.

Our replies are inline with your queries below:

1. After the last update, some translations (header, review tabs) were missing from the vendor store page. This includes the “Seller Registration” page. We also noticed that translation strings for the vendor dashboard are completely missing.

>> We have checked the translations with the latest version on our end and were unable to reproduce the issue. Kindly review the video below for reference:

https://www.awesomescreenshot.com/video/53327199?key=020365b1cd61366e8afababfecacf3ce

Could you please share a staging site running the latest version where you are experiencing this issue? This will allow us to investigate further and assist you accordingly.

2. Go to My Account → Orders → Open an order → Click the “Request a Refund” button. There’s no button to close the modal window.

>> Thank you for reporting this. We have already informed our development team about the issue, and the required modification will be added in the upcoming update.

3. Go to Plugin Settings → User Capabilities → The option to select settings for the Store Owner is missing.

>> We have checked this on our end and the settings are displaying correctly. Please refer to the screenshot below:

https://www.awesomescreenshot.com/image/60991613?key=9756017c021f1a6b4202c0658d51db47

Could you please share a screenshot or screen recording of the section from your end? This will help us better understand the issue and assist you further.

We look forward to hearing from you.

[Sangita Support Squad]

Hi there,

We are pleased to inform you that MultiVendorX 5.0.7 has been released, which includes the new exclude_ids parameter for the Store List shortcode. This allows you to exclude specific stores from appearing on the store listing page.

After updating to the latest version of MultiVendorX, you can use the following shortcode:

[marketplace_stores exclude_ids=”1,5,10″]

Simply replace the IDs with the vendor/store IDs you would like to exclude.

Please check this on your end and let us know if you need any further assistance. We’ll be happy to help.

[Sangita Support Squad]

Hi there,

We checked your site.

We are a bit confused because when we initially tested the migration on your shared site to verify the flow, we did not observe any store duplication issue. Additionally, for other users who have upgraded from earlier versions to the latest release, we have not received similar reports of duplicate store entries.

Since this behavior is only occurring on your setup, we would like to understand if there were any additional actions performed apart from updating MultiVendorX from the earlier version to the latest one. For example, was there any manual migration run, database operation, or plugin/theme change carried out during or after the update?

At the moment, we are not seeing any known trigger in the current migration flow that would result in store duplication under standard upgrade conditions. This is why we would like to carefully review any extra steps or environment-specific changes that may have contributed to this behavior.

Looking forward to your update so we can investigate this further and assist you in resolving it.

[Sangita Support Squad]

Thank you for your confirmation. We will review your site and get back to you with an update accordingly.

[Sangita Support Squad]

Hi there,

Thank you for sharing the site access with us.

As mentioned in our earlier response, could you please confirm whether the store duplication issue is occurring for all existing vendor stores on your site or only for specific stores?

If it is limited to certain stores, it would be very helpful if you could share the names of the affected stores so we can investigate more precisely.

Additionally, please confirm whether we have your permission to temporarily deactivate plugins and switch themes (if required) during our investigation. This will help us perform a more thorough troubleshooting and identify the root cause efficiently.

We look forward to your update.

[Sangita Support Squad]

Hi there,

Thank you for getting back to us and for taking the time to develop and share this solution. We truly appreciate your effort and willingness to contribute to the MultiVendorX ecosystem.

If you’d like to contribute this enhancement, please feel free to submit it as a pull request through our GitHub repository:

https://github.com/multivendorx/MultiVendorX

Once submitted, our development team will review the implementation and evaluate how it may fit within the plugin’s roadmap and architecture.

Thank you again for sharing your work with us. Contributions and feedback from community members like you are always appreciated.

In the meantime, if you need any further assistance from our side, please let us know. We will be happy to help.

[Sangita Support Squad]

Hello there,

Thank you for reaching out and providing the detailed information regarding the issue.

We are sorry to hear that you encountered this duplication after migrating from MultiVendorX v4 to v5.

To help us investigate this further, could you please confirm whether the duplicate store profile issue is occurring for all vendor stores on your marketplace or only for specific vendors?

Additionally, to properly review the migration data and identify the root cause, we would appreciate it if you could provide access to a staging environment where the issue can be reproduced. Please share temporary WordPress admin and FTP access so that our team can thoroughly examine the store records and migration process.

Once we have access to the requested details, we will investigate the issue and assist you with the safest resolution approach.

Also, while sharing the access details, please do not forget to mark your reply as private to ensure that the credentials remain secure.

We look forward to your response.

[Sangita Support Squad]

Hello there,

Thank you for reaching out and sharing the detailed analysis.

On the product page, the MultiVendorX scripts are primarily used to load and manage vendor-related data such as store information, geo-location, and other associated storefront functionalities. This is why the scripts are being enqueued on the product page.

Regarding the performance observations, I will share these details with our development team for review if further optimization is possible.

[Sangita Support Squad]

Hi There,

Thank you for reporting the breadcrumb issue.

We have investigated the issue and have logged it in our GitHub repository for further review and resolution. Our development team will work on fixing it in an upcoming update.

You can track the progress of this issue here:

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

We appreciate your patience and understanding while we work on this improvement.

In the meantime, if you need any further assistance or have any additional questions, please feel free to let us know. We are always happy to help.

[Sangita Support Squad]

Hi there,

Thank you for sharing the details. We will review and test the mentioned flow on our end and get back to you with an update accordingly.

[Author]

Posts