[Sangita Support Squad]

Hi,

This behavior with the translation is quite unusual, as we have tested the translations on our end and they are being translated and displayed correctly.

For your reference, please see the screenshots below, which demonstrate the translations working as expected:

https://www.awesomescreenshot.com/image/61748124?key=2288d8e645845121fcc947e6fee9c69d

https://www.awesomescreenshot.com/image/61748164?key=c7e9f83be2ab18b1f6f53e1b7cd39161

Since the translation works fine on our end, we would kindly request that you reset the staging site’s database and test the behavior again. It is possible that there is some database inconsistency or corruption in the staging environment that is preventing the translations from being reflected correctly.

We look forward to hearing the results after you have tested it again.

Regarding your question about the third-party integration, it is difficult for us to review custom code and fully understand your implementation. Could you please provide details about what you are trying to achieve and where you would like to add the integration? Based on your requirements, we will be happy to check whether there are any suitable hooks or filters available that can help you achieve the desired functionality.

Alternatively, if you require assistance with developing a custom workflow or implementation, you may reach out to our custom development team. They will be happy to discuss your requirements and assist you with the total custom development.

[Sangita Support Squad]

This reply has been marked as private.

[Sangita Support Squad]

Hello,

You’re very welcome.

We’re glad we could clarify your questions. Thank you for pointing out your observation regarding the Product Compliance settings appearing in the free version as well. We appreciate your feedback, and we’ll review it internally to see if any improvements can be made to avoid confusion.

If you have any questions in the future or need any assistance, please don’t hesitate to reach out. We’ll always be happy to help.

Have a great day!

[Sangita Support Squad]

Hi there,

Thank you for your cooperation.

We reviewed the console error you reported and have forwarded it to our development team for further investigation. They will review the issue and implement a fix accordingly. We will keep you updated as soon as the fix is available.

Regarding your second point about the Logo section, the logo uploaded by the admin from the MultiVendorX Admin Dashboard will be displayed. For a better understanding of how this works, please refer to this video:
https://www.awesomescreenshot.com/video/54326846?key=bf00c2e0aa4b793b270c1e39c47bb74c

As for the Product Compliance section shown here:
https://www.awesomescreenshot.com/image/61715405?key=972ec89961671e8796867cee9c1ed58c

This feature is part of MultiVendorX Pro. Once MultiVendorX Pro is installed and activated, you can configure the Product Compliance settings from the admin dashboard. As the marketplace admin, you can define compliance guidelines such as:
– All product listings must follow the platform’s content guidelines and avoid prohibited categories.
– Branded or regulated products must include authenticity certificates.
– Optional safety certifications may be uploaded for regulated items.

These compliance fields will then be available on the store owner’s Edit Product page in their store dashboard.

Please note that in the free version of MultiVendorX, only the Report Product Abuse feature is available.

If you have any further questions or need any additional assistance, please don’t hesitate to let us know. We’ll be happy to help.

[Sangita Support Squad]

Thank you for getting back to us, and we’re sorry to hear that you’re experiencing these issues on your end.

Kindly allow us some time to thoroughly review the reported concerns. We will investigate them and get back to you with an update as soon as possible.

Thank you for your patience and understanding.

[Sangita Support Squad]

Hi there,

Thank you for your patience while we investigated the issue.

After further testing, we were unable to reproduce the issue on our end. However, while reviewing your site, we noticed an error that appears to be related to the problem you’re experiencing.

We have logged this issue on our GitHub repository so that our development team can investigate it further and implement a fix if required. You can track the progress of the issue here:

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

We’ll keep you updated as soon as we have any progress or once a fix has been implemented.

Thank you again for your continued support, patience, and cooperation. Please feel free to reach out if you have any questions or need any further assistance in the meantime.

[Sangita Support Squad]

Hello,

Thank you for sharing the updated details. We are now able to log in to your site and proceed with our investigation.

Kindly allow us some time to thoroughly review the issue. We will get back to you with an update as soon as we have more information.

Thank you for your patience and understanding.

[Sangita Support Squad]

Hello,

We completely understand that this is a significant change for existing users, and we appreciate your concern regarding the migration process.

With the latest Membership module, we have adopted the newer subscription architecture supported by Stripe and PayPal. Due to the way these payment gateways handle subscription data, subscriptions created under the previous system cannot be automatically migrated to the new one. Unfortunately, neither Stripe nor PayPal provides a mechanism to seamlessly transfer existing subscriptions from the old architecture to the latest supported model.

We have carefully evaluated the possible approaches, and at this time, a direct migration of existing subscriptions is not technically feasible through the payment gateways themselves.

To help ease the transition, we can provide an option that allows you to manually assign an equivalent membership level to your existing stores so they can continue accessing the platform without interruption. and manage future upgrades or plan changes through the new subscription system without any issues.

However, please note that manually assigned plans are not recurring subscription plans. Due to the limitations of the payment gateways, recurring subscriptions cannot be assigned by the admin. If a store needs to be enrolled in a recurring paid membership plan, the store owner must subscribe to that plan themselves through the normal checkout process. This ensures that the recurring subscription is properly created and managed by Stripe or PayPal.

Once a store has subscribed through the new subscription system, they will be able to manage future renewals, upgrades, or plan changes without any issues.

We understand that this may require additional effort, and we truly appreciate your understanding. Our team is committed to assisting you throughout the transition and ensuring the process is as smooth as possible.

[Sangita Support Squad]

Hi there,

Thank you for sharing the access details.

Unfortunately, we were unable to log in using the credentials provided. Could you please verify them and share the correct login details with us so that we can proceed with the investigation?

We look forward to your update.

[Sangita Support Squad]

Hi there,

Thank you for getting back to us.

We have reviewed the store review flow once again on our test site, and it appears to be working as expected. When a customer submits a store review (https://www.awesomescreenshot.com/image/61601557?key=8ec6bcc9868d5a1056201af89818203b), it is successfully listed under the Store Reviews section in the admin dashboard (https://www.awesomescreenshot.com/image/61601591?key=7de2bbbf144909897ed88760f978016f), where it awaits the administrator’s moderation.

Since we have not been able to reproduce the issue on our end, it is unfortunately difficult for us to determine the exact cause or provide an accurate solution at this stage.

That said, we have logged the console errors and log details you shared and forwarded them to our development team. They will review the information carefully and make any necessary improvements or modifications where applicable.

In the meantime, if you could provide us with a site where the issue can be consistently reproduced, it would greatly help our investigation. Having access to a reproducible environment will allow us to identify the root cause more effectively and assist you with a resolution as quickly as possible.

We appreciate your patience and look forward to your response.

[Sangita Support Squad]

Hi there,

Thank you for sharing the details.

Could you please provide us with temporary access to a staging site, along with FTP access, where the issue can be reproduced? This will allow us to investigate the issue directly and assist you more effectively in identifying and resolving the problem.

When sharing the access details, kindly ensure that your reply is marked as private for security purposes.

We look forward to hearing back from you.

[Sangita Support Squad]

Hi there,

Sorry for the delay in getting back to you.

Regarding the translation issue, we have already logged it on our GitHub (https://github.com/multivendorx/multivendorx/issues/2106) for the development team’s review. They will investigate the issue and include the necessary fixes in our upcoming updates.

As for the store review flow, we have tested it thoroughly on our end and observed that as soon as a customer submits a review, it appears under the Customers tab in the MultiVendorX admin dashboard (https://www.awesomescreenshot.com/image/61577738?key=2878367e4b71b09089cd4bae6fa6688d). Only the marketplace administrator has the ability to approve or reject reviews, while the store owner can reply to the reviews from their store dashboard.

Based on our testing, this workflow is functioning as expected. We would kindly request you to review the flow once again on your end and let us know if you continue to experience any issues. If possible, please share the exact steps to reproduce the issue or any screenshots/screen recordings, as they will help us investigate further.

You can also refer to our documentation for more details on the review system:
https://multivendorx.com/docs/knowledgebase/multivendorx-review/

If you have any further questions or need any additional assistance, please don’t hesitate to let us know. We’re always here to help.

[Sangita Support Squad]

I completely understand your concern, and I appreciate your patience and understanding in this matter.

As mentioned in the previous reply, the module’s architecture has undergone significant changes with the update, which is why the behavior differs from earlier versions. That said, I understand how important this is for your workflow.

I have already shared your feedback and concerns with our development team, and we are actively reviewing the best possible approach. I will keep you informed of any updates and share further information as soon as I hear back from the team.

Thank you again for your continued cooperation.

[Sangita Support Squad]

Thank you for sharing the details. Please allow us some time to review the information. We will investigate the matter and get back to you with an update as soon as possible.

[Sangita Support Squad]

Hi there,

We completely understand your concern, and we’d like to explain the reason behind these changes.

Starting with **MultiVendorX Pro 2.0.0**, we completely redesigned the architecture of the Membership module. This update was necessary to align the module with the latest API structures and requirements of both **PayPal** and **Stripe**, ensuring better compatibility, improved reliability, and smoother subscription management going forward.

With the new architecture, whenever you create a membership plan and configure either the PayPal Marketplace or Stripe Marketplace payment gateway, a corresponding subscription product is automatically created within the selected payment gateway. When a customer purchases that membership, a matching subscription is also created on the payment gateway, and all future renewals are managed directly by the payment gateway itself.

Since the entire subscription flow and data structure have changed significantly in this new implementation, the previous membership plans are not compatible with the new system. For this reason, we were unable to provide a migration process for existing membership plans, as migrating them could have resulted in inconsistencies with the subscription data maintained by the payment gateways.

We understand that recreating the membership plans may require some additional effort, and we truly appreciate your understanding. These changes have been made to provide a more stable, secure, and future-proof subscription system.

If you have any questions or need any assistance while setting up your membership plans, please let us know. We’ll be more than happy to help you through the process.

[Author]

Posts