[Criss]

I had you help me update WCMP to MVX on my staging site, but now I have the same problem on my production site. The plugin has crashed my site/backend and I don’t know how to recover.
Urgent help needed, please!

[Criss]

…via FTP I have renamed “dc-woocommerce-multi-vendor-DEACTIVATED” in order to see my site’s backend again. Then I tried to install MultiVendorX-main.zip but I get the same message I got in my staging site (“the link is expired”). Please reply urgently, I need to resolve this.

[NerdySupportExpert Moumita]

This reply has been marked as private.

[Criss]

…can I just copy/overwrite the backup “dc-woocommerce-multi-vendor” onto the new one, or has also the database made some changes?

[NerdySupportExpert Moumita]

Yes Criss the database has been changed .You should take backup for your entire site first then update WCMP to MVX.

[Criss]

hello again, I have now restored my website to be ready to update from WCMP 3.9.3 to MVX 4.0.1.
There is one problem I detected on my staging site, so I don’t know if it’s better to fix the issue in the staging site or go for the update and then try to tackle the issue in the production site. What do you suggest to do?
The issue is within MVX, maybe a conflict with the theme, but it appears only when a registered user has become a vendor and not if he stays as a non-vendor.

[NerdySupportExpert Moumita]

Hello Criss,We would suggest you to fix the issue first and then update the plugin.

[Criss]

…sure you are right, the problem is that the theme’s author is not responding and he’s also lying about being in contact with you.
What should I do? Can’t you look at the problem and detect the culprit? I’m not a developer and I wouldn’t know what to look for. 🙁

[NerdySupportExpert Moumita]

Hello criss our office is closed for saturday and sunday. So we will look into the matter once the weekend is over.

[Author]

Posts