[l.gan]

Hello, thank you for your support.
The site has become very, very slow.
1. Previously, the frontend loaded in 0.9 seconds (which we calculated was slow), but now it’s about 10-11 seconds. Even Google Page Speed ​​can’t measure the speed.
We also see a repeating error in the logs, which seems to happen every time any page is closed.

PHP Fatal error:  Uncaught Error: Call to a member function get_total() on false in 
/public_html/wp-content/plugins/dc-woocommerce-multi-vendor/classes/Migration/MVX.php:898\nStack trace:\n#0 /public_html/wp-content/plugins/dc-woocommerce-multi-vendor/classes/Migration/MVX.php(123): MultiVendorX\\Migration\\MVX->migrate_commissions()\n#1 
/public_html/wp-content/plugins/dc-woocommerce-multi-vendor/classes/Migration/Cron.php(62): MultiVendorX\\Migration\\MVX->run_migration_cron()\n#2 [internal function]: MultiVendorX\\Migration\\Cron->run_table_migration_cron()\n#3 
/public_html/wp-includes/class-wp-hook.php(341): call_user_func_array(Array, Array)\n#4 
/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters('', Array)\n#5 
/public_html/wp-includes/plugin.php(570): WP_Hook->do_action(Array)\n#6 
/public_html/wp-cron.php(191): do_action_ref_array('mvx_full_migrat...', Array)\n#7 {main}\n  thrown in 
/public_html/wp-content/plugins/dc-woocommerce-multi-vendor/classes/Migration/MVX.php on line 898

What we tried:

Disabled all plugins except Woo and Multivendorx.
Switched to the “Storesront” theme.

The site speed is still slow.

2. Question about the Loco Translate plugin: We also noticed that our custom translation isn’t loading. It’s there – it’s synced with the new version of the plugin, but our language isn’t being applied.

[Sangita Support Squad]

Hi there,

I’m sorry to hear that you encountered an issue with the upgrade. To help us investigate and resolve this as quickly as possible, could you please share access to a staging site (a replica of your live site), along with the FTP details?

For security purposes, kindly ensure that you mark your reply as private when sharing these credentials.

We look forward to receiving the details and assisting you further.

[l.gan]

It looks like we’re having trouble migrating from the old plugin to the new one. Order status:

All orders (there are 236 in the system) have been canceled.
Example:
cancelled #16546 – ​​for a deleted store
cancelled #16545 – for a deleted store
However, the number of commissions is 6592. We checked the system, and multiple commissions are being generated for a single order.
Lifetime Earning is significantly inflated.

All products have had their assigned vendors automatically removed.

Something clearly went wrong, and we’ve performed a full rollback.
Unfortunately, we are currently unable to provide access to the website.

Attachments:

1. 

   2026-04-18-164810.png
   

2. 

   2026-04-18-164937.png
   

[NerdySupportExpert Moumita]

Hi @l.gan,

We’re sorry to hear that you’re facing this issue.

We tested the migration on our end but were unable to reproduce the error. Since the issue seems specific to your setup, we’ll need to replicate your environment to properly identify the root cause.

It would be very helpful if you could share a database dump of your site, preferably from before the upgrade. Alternatively, access to a staging site along with its database backup would allow us to run the migration and investigate the issue more closely.

We understand that you may want to use a rollback version for now. However, we strongly recommend moving to MultiVendorX 5.0, as it introduces a major structural upgrade built on a modern React-based framework. All future updates and improvements will be based on this version.

To ensure your site transitions smoothly to 5.0, it’s important for us to understand why this issue is occurring specifically in your case.

For context, 1000+ sites are already using this version successfully, with only a few isolated issues reported. Your support in sharing the required data will help us resolve this faster and ensure a stable experience.

Looking forward to your response.

[l.gan]

This reply has been marked as private.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Our team already worked on this and loaded the minimum no of resources possible and that too page wise as and where required, Will release that update tomorrow.

[Sangita Support Squad]

Hi there, We have released an update (MultiVendorX 5.0.1). Kindly update the plugin to the latest version on your end and verify if everything is working as expected.

If you have any further questions or need any assistance, please feel free to let us know—we’ll be happy to help.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Hello there,

Thank you for getting back to us and sharing your queries in detail. Please find our responses inline below:

1. Issue: Error with WooCommerce emails
(Go to WooCommerce → Settings → Emails to view the error)

>> We have shared this issue with our development team, and they are currently investigating it. As soon as a fix will be added we will share the fx with you accordingly.

2. Issue: Translations (especially Russian) not working with Loco Translate

>> As MultiVendorX 5.0.0 is a major revamp, we’ve made significant improvements to the plugin’s structure, which also involved updating existing text strings and introducing new ones.

Because of these changes, some of the translations created in older versions may not automatically apply in the new version—this happens when the original strings have been modified or replaced.

To retain as much of your existing work as possible, you can export your previous translation files and import them into the updated version. Any unchanged (matching) strings will continue to display your translations. However, for newly added or modified strings, translations will need to be added again.

We understand that you’ve already invested time in translating the plugin, and these changes were necessary to improve functionality and ensure a more robust and future-ready system.

If you have any further questions, please feel free to let us know—we’re always here to assist you.

[l.gan]

Thank you very much for your quick response and prompt review.

Translation: the file isn’t old; it’s a new installation of WordPress, WooCommerce, and MultivendorX (with the new version) on a new database and a clean WordPress installation.

I mean that MultivendorX was already installed with version 5.0.

[Sangita Support Squad]

Thank you for your response.

We will review the translation flow on our end and get back to you as soon as possible.

Thank you again for your understanding and continued support.

[Sangita Support Squad]

This reply has been marked as private.

[l.gan]

This reply has been marked as private.

[NerdySupportExpert Moumita]

Hi @l.gan, We’ve thoroughly checked this issue, and we can confirm that it is not coming from our plugin.

From our investigation, the error appears to be caused by Cyr to Lat plugin.

Similar issues have also been reported here: https://wordpress.org/support/topic/the-rest-api-encountered-an-unexpected-result-15/

We recommend reaching out to the Cyr to Lat plugin author for further assistance, as they would be better equipped to investigate and resolve this conflict.

Please feel free to reach out if you need any help from our side.

[l.gan]

Thank you for the information, I’ll contact the plugin developers or the hosting provider for assistance.

4. Question:
If the plugin is installed on an older version (prior to 5.0), it triggers a wave of CRON tasks to initiate the migration.

If the plugin is installed on a clean version of WordPress without previously installed WordPress MultivendorX, the migration process shouldn’t occur.

In one of my cases, there is an installation on a clean WordPress (another site – not the one you have access to) and I encountered a situation where there are over 13,000 “errors” in the logs.

For example:

1. WordPress database error Table '*.wp_mvx_products_map' doesn't exist for query SELECT product_map_id, product_id, created FROM wp_mvx_products_map ORDER BY product_map_id, ID LIMIT 100 OFFSET 0 made by do_action_ref_array('mvx_full_migration'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MultiVendorX\Migration\Cron->run_table_migration_cron, MultiVendorX\Migration\MVX->run_migration_cron, MultiVendorX\Migration\MVX->migrate_other_tables

2. WordPress database error Table '*.wp_mvx_vendor_ledger' doesn't exist for query SELECT * FROM wp_mvx_vendor_ledger LIMIT 100 OFFSET 0 made by do_action_ref_array('mvx_full_migration'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MultiVendorX\Migration\Cron->run_table_migration_cron, MultiVendorX\Migration\MVX->run_migration_cron, MultiVendorX\Migration\MVX->migrate_ledger

3. WordPress database error Table '*.wp_mvx_shipping_zone_methods' doesn't exist for query SELECT * FROM wp_mvx_shipping_zone_methods LIMIT 100 OFFSET 0 made by do_action_ref_array('mvx_full_migration'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MultiVendorX\Migration\Cron->run_table_migration_cron, MultiVendorX\Migration\MVX->run_migration_cron, MultiVendorX\Migration\MVX->migrate_other_tables

4. WordPress database error Table '*.wp_mvx_visitors_stats' doesn't exist for query SELECT * FROM wp_mvx_visitors_stats LIMIT 100 OFFSET 0 made by do_action_ref_array('mvx_full_migration'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MultiVendorX\Migration\Cron->run_table_migration_cron, MultiVendorX\Migration\MVX->run_migration_cron, MultiVendorX\Migration\MVX->migrate_other_tables

5. WordPress database error Table '*.wp_mvx_cust_questions' doesn't exist for query SELECT * FROM wp_mvx_cust_questions LIMIT 100 OFFSET 0 made by do_action_ref_array('mvx_full_migration'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, MultiVendorX\Migration\Cron->run_table_migration_cron, MultiVendorX\Migration\MVX->run_migration_cron, MultiVendorX\Migration\MVX->migrate_other_tables

As far as I understand, I can simply manually delete them from the CRON tasks, but could you please provide an exact list of CRON tasks for migration that I can safely delete?

As I currently see it, this task is exactly:

mvx_full_migration
mvx_migrate_other_tables
mvx_migrate_ledger

Thank you.

[Sangita Support Squad]

Hi there,

Thank you for bringing this to our attention and for sharing the detailed information.

We have shared these details with our development team for further review. They will investigate the root cause and work on implementing the necessary fixes. Once the improvements are included in an upcoming update, we will make sure to keep you informed.

You can also keep track of the same from here https://github.com/multivendorx/multivendorx/issues/1719.

In the meantime if you have any additional details or observations, please feel free to share them with us.

[l.gan]

This reply has been marked as private.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

I’ve shared this with the development team. I’ll update you as soon as I hear back from them.
Thank you for your understanding and continued support.

[Sangita Support Squad]

This reply has been marked as private.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Hi @l.gan,

Thank you for sharing the details from your hosting provider.

To clarify, MultiVendorX does not require Composer in a production environment at all. The plugin is designed to work out of the box after installation and activation in WordPress.

Composer is only used during development—for tasks like coding standards, testing, and build processes—and all of those dependencies are listed under require-dev. These are not needed for running the plugin on a live site.

So for your setup:

You do not need Composer installed on your server
You do not need to configure any Composer path
You do not need to run composer install
No command-line access is required

The only runtime requirement for MultiVendorX is:

PHP version 8.0 or higher

Because of this, there is no Composer path to provide or configure for the plugin to function.

If you are encountering an issue related to Composer or PHP versions, it may be coming from the server environment or another plugin, rather than MultiVendorX itself.

Please let us know if you need help identifying the exact cause—we’d be happy to assist further.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Hello there,

Thank you for your response.

As mentioned earlier, MultiVendorX does not require Composer in a production environment, and the only runtime requirement is PHP version 8.0 or higher.

Now as you have mentioned PHP issue, could you please share more details about the specific error or behavior you’re experiencing? This will help us understand the issue better and assist you more effectively.

We look forward to your reply.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

This reply has been marked as private.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Hello There,

Thank you for getting back to us. We are sorry to hear that you are still experiencing issues with the translation.

To help us investigate this more accurately, could you please share the specific strings or texts that are not getting translated on your end? This will allow us to review the issue accordingly and assist you further in the best possible way.

We look forward to your response.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Hi There,

Thank you for getting back to us, and we are sorry to hear that you are still experiencing issues with the translations.

Regarding the notices, we have already shared the details with our development team, and they will review them accordingly.

As for the translation issue, we checked from our end and found that the changes are getting reflected properly. Kindly refer to the screenshots below for reference:
https://www.awesomescreenshot.com/image/60347677?key=0d13863e98b1262025e345beddfb7ed6
https://www.awesomescreenshot.com/image/60347683?key=7e2ba44c79812173916b28678b0e60ad

Therefore, we would kindly request you to make sure that the site language has been changed accordingly so that the translations can reflect properly on your site.

If there is anything else we can assist you with, please do let us know. We are always happy to help.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Hi there,

Thank you for the update. This does seem a bit unusual.

We attempted to log in to the shared site to investigate the issue further, but unfortunately we were unable to access it. We are currently seeing a white page during login, as shown in the screenshot below:
https://www.awesomescreenshot.com/image/60358143?key=672b6288a72bd5e1b22c159b0d222d6a

Could you please check this on your end and let us know once the issue has been resolved and the site is accessible again? We’ll then proceed with the investigation accordingly.

Thank you!

[l.gan]

Thanks for the info, yes, this is related to debug mode being enabled.

Debug mode is now disabled, the define( ‘WP_DEBUG’, false ) condition is set, and there shouldn’t be any white screens.

Please check again.

[Sangita Support Squad]

Thank you for the update. Kindly provide us some time to check and we will get back to you accordingly.

[Sangita Support Squad]

Hello there,

Just to keep you posted, we have checked the translation issue on your shared site and found that the translations added in other languages are getting reflected accordingly. However, the issue seems to be occurring specifically for the Russian language.

Please do not worry, as we are currently looking into this matter with our development team, and we will keep you updated accordingly with further findings.

Thank you for your patience and cooperation.

[Sangita Support Squad]

Hello There,

Our team has further investigated the issue, and we found that the translations added for other languages on your site are getting reflected correctly. To debug the issue further, we also tested the Russian translations on our own test environment, and in our case, the translations were displayed properly as well.

Kindly refer to the following video for reference:
https://www.awesomescreenshot.com/video/52418525?key=450c2173bc7cff8d00fa719780902b5a

At the moment, this situation appears quite unusual because the issue seems to be occurring only for the Russian language on your site, while the other language translations are working as expected. If the issue had been reproducible for all languages or on our test environment as well, it would have been easier for us to identify the exact root cause.

With that being said, could you please let us know if we may reset your site for testing purposes to check whether there might be any database-level corruption or inconsistencies causing the issue on your end?

We truly appreciate your cooperation and look forward to your response.

[l.gan]

Hello,

“Could you let us know if we can reload your site for testing purposes to check for any corruption or inconsistencies at the database level causing the issue on your end?” – Of course, you can take any necessary steps to fix the problem.

Just please let us know what needs to be done/or not done, as the issue affects multiple sites. (Two with a new WordPress installation, one a store, but we rolled back.)

[Sangita Support Squad]

Hello There,

Thank you for getting back to us.

We would like to clarify that, by “reset,” we mean performing a complete reset of the shared site. This process will remove and reset all existing site data, including the database tables and related configurations.

As this action is irreversible, we would kindly request your final confirmation before we proceed with resetting the site on your end.

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

[l.gan]

Yes, go ahead and reset it.

[Sangita Support Squad]

This reply has been marked as private.

[Sangita Support Squad]

Hi There,

We went ahead and reset your site. After that, we added the translation for the string “Questions about this product,” and it is now displaying correctly on the site.

Kindly check the screenshots below for reference:
https://prnt.sc/k-DXGIwop_E0
https://prnt.sc/Riu8siJzC-On

Based on our findings, it appears there may previously have been an issue related to database corruption, which was likely preventing the translations from being reflected properly.

We would kindly request you to check the translations on your end again and let us know if everything is working correctly now.

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

[donald_punk]

Hi, I’m experiencing the same translation issues described here. I’m also using Loco Translate and trying to translate everything into German. I deleted my old translation files and started fresh with new ones, but the dashboard still isn’t being translated.

[Sangita Support Squad]

Hi There,

We are extremely sorry to hear that you are experiencing a similar issue with the translations on your end.

To help us better understand and investigate the matter, could you please share more details about the specific strings or text that are not getting translated correctly? If possible, screenshots or examples of the affected areas would also be very helpful for our investigation.

Once we have these details, our team will look into the issue carefully and assist you further with the appropriate solution.

We look forward to hearing back from you.

[donald_punk]

Hi, sadly I couldn’t translate anything from the dashboard. I started with “Good morning”, I tried “Admin Announcements” and “Latest Reviews”.

Because of many issues, I had to roll back with a backup with the MVX version 4.

I will try to set up a staging during the day and send you the login.

[Sangita Support Squad]

Hi There,

Thank you for sharing the details with us.

Our team is currently investigating the translation issue and we will keep you posted with updates as soon as we have more information from our development team.

Regarding the other issues you mentioned, could you please specify the exact problems you encountered apart from the translations? This will help us investigate them properly and assist you with the appropriate fixes and guidance.

We look forward to hearing back from you so that we can assist you further accordingly.

[Sangita Support Squad]

Hi There,

We are glad to inform you that we have added a fix for the translation issues you were experiencing in the latest MultiVendorX update.

Kindly update the MultiVendorX plugin on your end to the latest version, MultiVendorX 5.0.5, and then check the functionality accordingly.

If you need any further assistance from our end or face any issues after updating, please do let us know. We are always here to assist you.

[l.gan]

Everything works great now, Sangita, thank you so much, great support!
In version 5.0.5, everything was translated 🙂
Thanks again for your work!

[Sangita Support Squad]

Hello,

Thank you so much for your kind words and feedback. We are really glad to hear that everything is working properly now and that the translations are reflecting correctly in version 5.0.5.

It was our pleasure to assist you, and we truly appreciate your patience and cooperation throughout the process.

If you have any further queries or need any assistance in the future, please do not hesitate to reach out. We will always be happy to help.

[l.gan]

Hello, could you please check this for yourself: Website appearance:
Strings are not translated or strings are missing for translation.

/store/shop-name/reviews/ – “No policy found” – missing from the translation file.
_____
/store/shop-name/reviews/
5 Star
Reviews
4 Star
3 Star
2 Star
1 Star
Ratings
– Rating information (please see photo). Translation strings are in the file, they are translated, but the translation is not applied.
____
Seller registration page:
Account
Store info
Tell us about your store.
This information will be reviewed by our team before your store goes live. Please fill it out accurately.
Continue to Store Details
– Translation strings are in the file, they are translated, but the translation is not applied.
**
Step 2 of 2
Click to upload or drag and drop
Please enter a valid email address.
is required

– missing from the translation file

Attachments:

1. 

   2026-05-13-185951.png
   

2. 

   2026-05-13-185831.png
   

[Sangita Support Squad]

Thank you for sharing the information. Kindly allow us some time to review this on our end. We will get back to you with an update accordingly.

[l.gan]

Sorry, could you please check the flow again?

“Other” – in the abuse report – is in the translation file, but it’s not translated.

—-
1. Redirect from the vendor login page to the Dashboard.
Multivendor before 5.0 – there was an automatic redirect.

Please help:
As far as I understand, the page with the shortcode [marketplace_store] is the Dashboard login page for already registered vendors?

After logging in via [marketplace_store], should there be a redirect to the Vendor Dashboard page with the shortcode [marketplace_dashboard]?

Behavior after 5.0: Currently, there is no redirect. After logging in via [marketplace_store], the vendor remains on this page – it simply becomes empty (but with the site header, footer, etc.).

To access the Dashboard, the vendor needs to find the [marketplace_dashboard] page themselves, and only then will they be able to access their dashboard.

Can you please verify and confirm that this is the expected behavior?

___

2. Should an already authorized vendor via [marketplace_store], when going to the page with the [marketplace_registration] shortcode, see the option to re-submit the registration form?

Expected behavior: maybe a message like “You’re already registered!”

The user is currently viewing (photos 2 and 3).
___

3. Should there be a button to access the dashboard from site.com/my-account/? (as was the case before)

[Sangita Support Squad]

Hi There,

Thank you for sharing your queries in detail. Our replies are inline with your questions below:

1. Translation issue

>> We have already logged this issue on our GitHub repository, and our development team will work on a fix accordingly. As soon as the fix is implemented, we will keep you posted with further updates.

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

2. Redirect from the vendor login page to the Dashboard

>> Currently, the shortcode for the store dashboard is: [marketplace_dashboard]

So, you need to use this shortcode for the store dashboard page.

We checked the flow on our end, and upon logging in, the vendor is redirected to their store dashboard accordingly. Kindly check the video here:
https://www.awesomescreenshot.com/video/52534180?key=99a78e352f97cabd6bdea3d6cb6d6082.

Also, it seems there is a typo mistake in the admin dashboard settings description related to the Store Dashboard page shortcode. Not to worry – we will update this accordingly so users are not confused in the future.

3. Should an already authorized vendor via [marketplace_store], when going to the page with the [marketplace_registration] shortcode, see the option to re-submit the registration form?

>> With MultiVendorX 5.0.0, we introduced the concept of multi-stores. This means a single store owner can now register and manage multiple stores under the same account. From the dashboard, they can switch between different stores accordingly.

If you do not want your store owners to have multiple stores, then customisation would be required on your end to restrict this behaviour.

4. Should there be a button to access the dashboard from site.com/my-account/?

>> We checked this on our end, and the button for accessing the dashboard page is appearing correctly on the WooCommerce My Account page. Kindly check the screenshot here:https://www.awesomescreenshot.com/image/60462014?key=c53f207a6951759f65328db71cf3a15a.

Could you please check carefully once again on your end?

If you have any further queries or need any additional assistance, please do let us know. We will be happy to assist you further.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

Hello There,

Thank you for getting back to us. We are glad to hear that the other queries have been resolved on your end.

Regarding the button issue, as per the default flow, we have already added the “Go to Dashboard” button on the My Account page for redirecting users to the Store Dashboard, and this functionality is working correctly from our end.

It appears that, within the theme settings, the redirect URL for the profile widget has been configured to point to the admin dashboard instead. Because of this configuration, you are experiencing the current redirection behaviour.

We would kindly recommend reaching out to the theme support team and sharing these details with them so they can assist you with modifying the redirect flow accordingly. Alternatively, if needed, you may also add your own custom modification to refine the redirection behaviour of the theme’s widget.

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

[l.gan]

Thanks for your message.

Regarding the button issue, as per the default flow, we have already added the “Go to Dashboard” button on the My Account page for redirecting users to the Store Dashboard, and this functionality is working correctly from our end.
It appears that, within the theme settings, the redirect URL for the profile widget has been configured to point to the admin dashboard instead. Because of this configuration, you are experiencing the current redirection behaviour.

The redirect to the Account page from the Bloxy theme widget doesn’t work only for the “Store Owner” role, which is created by the MultivendorX plugin. This role is what redirects to the admin control panel page.

For other roles not created by the MultivendorX plugin, there are no issues with the theme widget or redirecting to the WP-Admin control panel page.

This is a conflict between the theme and MultivendorX.

[l.gan]

Sangita, sorry, we retested based on your recommendations – indeed, there is no problem.

In the Blocksy theme header settings, you need to select redirection to the WooCommerce user account, not the user’s account.

Sorry, it was our oversight.
We confirm that everything is fine.

[Sangita Support Squad]

Thank you for the update. We’re glad to hear that everything is working well on your end.

Please let us know if you need any further assistance from our side. We are always happy to help.

[l.gan]

This reply has been marked as private.

[Sangita Support Squad]

This reply has been marked as private.

[l.gan]

Hello

Yes, please give me a little time and I’ll share the access with you.

But I have a new question:
Is it possible to add attributes to a “Simple Product Type” from the vendor dashboard?
I don’t have an attributes tab – is this a new feature or limitation?

[l.gan]

To add to the question, the “Attributes” tab is also missing from your test site. The ability to add attributes is only available for variable product types—I checked this on your site: multivendordemo.com/multivendorx/store-dashboard

Is this how it should be?
If so, is this a critical change? Why didn’t you warn me about it in the release?

[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.

[l.gan]

Hello, thank you for your reply. This is a complete disaster.

How will filters work then when a user searches for their clothing color? This solution means that when using filter plugins, the user won’t see some products because they won’t be displayed at all—they simply won’t have the attributes required for filtering.

The product also won’t appear in product selections (attribute archives). Could you please raise the issue of returning the attribute tab for Simple Products, or share the code (ready-made) for opening the attribute tab for Simple Products? I mean provide a setting for those who need it.

[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.

[l.gan]

Hello, please tell me if there is any information on enabling the attributes tab for a simple product type?

[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.

[l.gan]

This reply has been marked as private.

[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.

[l.gan]

Thank you very much Sangita! Of course you can turn on/off whatever you need.

[l.gan]

Also, could you please hide or delete the message with my details (message #253185) above? For some reason, it was published without being hidden 🙂

[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.

[Author]

Posts