[Sangita Support Squad]

Hi there,

Thank you for sharing the detailed findings along with the information from the WooCommerce AJAX Products Filter plugin documentation.

Based on the details you shared, it appears that the filtering issue is occurring because the third-party filtering plugin is not recognizing the MultiVendorX store page as a standard WooCommerce product archive page. As mentioned in their own diagnostic tool and documentation, the plugin relies on WooCommerce hooks, native product loops, or supported shortcodes/blocks to identify products server-side for AJAX filtering.

Since the filtering functionality is entirely handled by the third-party plugin, the required compatibility implementation would need to be added from their end so that their plugin can properly recognize and process the MultiVendorX store pages.

Therefore, we would kindly request you to reach out to the plugin’s support team and ask them to add compatibility support for the MultiVendorX store/shop pages within their filtering logic.

That said, if their team requires any technical information regarding the structure of the store shopfront page, hooks used, or any assistance from our end to help with the compatibility implementation, please feel free to let us know. We will be happy to assist with the required information wherever possible.

[Sangita Support Squad]

Thank you for the details.
Let me share this with the team, and we will get back to you accordingly.

[Sangita Support Squad]

We have already logged this issue on our GitHub, and our team will work on adding the necessary fixes accordingly.

You can track the progress of the issue from here:
https://github.com/multivendorx/multivendorx/issues/1953

Also, could you please let us know where you are seeing the details mentioned in reply #253594?

[Sangita Support Squad]

Hi There,

Thank you for getting back to us.

We are glad to hear that the “hide empty” parameter support on the store list page was helpful for you.

Regarding the addition of a parameter to pass the store ID for hiding stores from the store list page,we have logged this request in our github and we will add the support in our upcoming update accordingly. In the meantime you can keep track of the progress of the same from here https://github.com/multivendorx/multivendorx/issues/1931.

For excluding cretain store products from appearing on the WooCommerce shop page, you can make use of the following filter on your end:

return apply_filters( ‘multivendorx_get_excluded_products’, false, $product_id, $store_id );

You can customize the logic accordingly to hide specific store products from the WooCommerce shop page based on your requirements.

If you need any further assistance from our end, please feel free to let us know. We are always happy to assist you.

[Sangita Support Squad]

Hi there,

Thank you for getting back to us.

As shared earlier, with the latest version, you will no longer need to add any custom code to exclude stores without products from the store list page. You can simply use the shortcode in the following format:
[marketplace_stores hide_empty=”true”]

Regarding your query about the other customizations, please allow us some time to check with our team. We will get back to you with an update accordingly.

[Sangita Support Squad]

Hello There,

Thank you for getting back to us and for sharing the detailed explanation regarding the issues.

Regarding the issue you are facing with the third-party filtering plugin, I have already forwarded the details, including the video and the behavior you described, to our development team for further review. Once I receive an update from them regarding the compatibility flow or possible cause, I will surely keep you posted.

Regarding your queries about the attribute workflow, the behavior where newly added values get saved under the global WooCommerce attribute taxonomy is currently based on the default WooCommerce attribute handling flow, and we have implemented the same behavior for vendors within MultiVendorX.

As for the updated attribute selection flow in MultiVendorX 5.0.0, since the entire UI and architecture of the plugin have been redesigned, some workflows have also been modified accordingly. At present, when an attribute is selected, all available terms are loaded by default, and vendors can remove the unwanted ones using the delete option provided.

If your vendors need assistance understanding the updated workflow, you can simply share proper guidance or tutorials with them accordingly. Additionally, if needed, we can also help by providing proper documentation or a knowledgebase guide explaining the new flows in MultiVendorX 5.0.0. Please feel free to let us know, and we will surely assist you accordingly.

Hope this helps clarify the current behavior.

In the meantime, if you need any further assistance from our end please do let us know.

[Sangita Support Squad]

Hi There,

We have further investigated the flow mentioned by you and were able to replicate the issue on our end. Accordingly, we have logged the issue in our GitHub repository, and our development team will work on the required fixes.

Once the issue is resolved, we will surely keep you updated.

In the meantime, you can track the progress of the issue here: https://github.com/multivendorx/multivendorx/issues/1918.

If you need any further assistance from our end in the meantime, please do let us know. We are always here to assist you.

[Sangita Support Squad]

Hi there,

Thank you for your confirmation. We will now proceed with checking the issue on your end.

Also, regarding your earlier reply, it has already been marked as private, so there is no need to worry.

We will get back to you with an update shortly.

[Sangita Support Squad]

Thank you for sharing the issue details along with the site credentials.

Could you please confirm if we may temporarily deactivate the theme and plugins for troubleshooting purposes while checking the issues?

Also, we are glad to inform you that we have already released an updated version of with the addition of the Attribute tab for all product types, along with fixes for the translation issues mentioned by you. Kindly update the plugin to the latest version on your end and check the functionality once again.

We look forward to hearing back from you with your confirmation.

[Sangita Support Squad]

Hi there,

We are glad to inform you that our team has already added support for the Attribute tab for Simple Product types, and this enhancement will be included in our upcoming MultiVendorX update.

Once the update goes live, we will surely keep you posted.

In the meantime, if you need any further assistance from our end, please do let us know.

[Sangita Support Squad]

Hello,

Thank you for getting back to us, and we are glad to hear that the new MultiVendorX version is helping you cover many of your previous custom requirements through the default flow. We truly appreciate your feedback.

Regarding your query about manual commission payments in MultiVendorX 5.0.0, the flow has been updated compared to the previous versions. While the earlier “Mark as Paid” option is no longer available in the same way, you can still manage vendor payouts manually from the Transaction History section.

To proceed with manual commission disbursement, kindly navigate to:

Admin Dashboard → MultiVendorX → Transaction History

From there, you can review the commission transactions and disburse the commission amounts accordingly based on your manual payment process to vendors (https://www.awesomescreenshot.com/image/60569613?key=95bd272fded393d30f9e86c14df162eb). This allows you to continue managing payouts manually on your end while maintaining proper transaction records within MultiVendorX.

For more details about the payout and disbursement flow in MultiVendorX 5.0.0, you can also refer to our documentation here:
https://multivendorx.com/docs/knowledgebase/disbursement-of-payments/

If you have any further questions or if you need assistance with any customization related to your payout workflow, please feel free to let us know. We will be happy to assist you further.

[Sangita Support Squad]

Hi there,

We totally understand your concern, and we have already forwarded it to our development team regarding this matter.

Also, regarding the custom code, we are afraid that currently we do not have any ready-made code available for this specific requirement. However, for assistance with the customization, you can refer to our documentation here:https://multivendorx.com/docs/code-snippet/add-custom-menu-to-store-dashboard/.

If you need any further assistance from our end, please do let us know. We will be happy to assist you accordingly.

[Sangita Support Squad]

Hi There, Thanks for getting back to us.

As per the updated flow, the Product Attributes tab is now displayed only for “Variable Products.” This is because attributes are primarily used to create and manage product variations such as size, color, material, etc.

For other product types, variations are not must needed, so the Attributes section remains hidden by default. This helps keep the product management interface cleaner, simpler, and easier to manage for vendors.

If you would like to make the Attributes option available for other product types as well, then customisation will be required, as this is not included in the default functionality. For customisation guidance, you can refer to our documentation here – https://multivendorx.com/docs/code-snippet/add-custom-menu-to-vendor-dashboard/.

If you have any further queries, please do let us know.

[Sangita Support Squad]

This reply has been marked as private.

[Sangita Support Squad]

We are happy to assist you. If you need any further assistance from our end, please do let us know. We are always here to help and support you accordingly.

[Author]

Posts