[Connor Murphy]

We are using the MultiVendorX plugin on a website https://drillerdeals.com. After updating to the latest version, we encountered multiple critical issues (including fatal errors and warnings) that caused previously stable functionality to break. We are on the latest version at the moment MultivendorX (4.2.30) And MultivendorX Pro (1.3.24)

Impact:

The vendor dashboard became inaccessible due to fatal errors.
The plugin started returning NULL for $vendor->term_id, breaking multiple dependent templates.
Vendor information and store settings are not updating properly in some cases.
These issues occurred immediately after the update, on a site that was working perfectly beforehand.

Key Observations:

$vendor objects are sometimes returned without a valid term_id.
Functions like mvx_get_vendor_review_info() are being called with NULL parameters, triggering fatal errors.
The issue appears to be related to changes in the latest version affecting vendor object initialization or term assignment.
Some jQuery issues related to DataTables

Current Status:

We applied a temporary fix in our vendor dashboard template by checking for $vendor object validity before calling dependent functions.
The site is stable now, but vendor data handling needs further review to ensure new vendors and dashboard functions work as expected.

[Sangita Support Squad]

Hello there,

We’re sorry to hear that you’ve been experiencing these issues. However, we haven’t been able to replicate them on our end.

It would be greatly appreciated if you could create a staging site where the issues can be reproduced and share the following details with us:

— Staging site URL

— Temporary admin access

— FTP access

This will allow our team to investigate the issues thoroughly and provide you with an appropriate solution.

Also while sharing the access don’t forget to mark your reply as private.

We will look forward to hearing back from you.

[Sangita Support Squad]

It’s been a while since we last heard from you, so we’re assuming your query has been resolved. We’ll be closing this thread for now.

If you need any assistance or face any issues in the future, please feel free to create a new support ticket — we’ll be happy to help.

[Author]

Posts