[purchase]

Hi,

I added an attachment field for Store Logo in the Vendor registration page and set to only accept JPEG and PNG.(See attached Vendor Registration Form Settings Page.png)
When I tried uploading an unaccepted file, the error message displayed only shows letter ‘P’.
(See attached Vendor Registration Form.png and Vendor Registration Form with Error.png)

When I tried to turn on debugging,

Warning: Illegal string offset 'notice' in /XXXX/wp-content/plugins/woocommerce/templates/notices/error.php on line 30

Copy

is displayed. (See attached Vendor Registration Warning.png)

It seems the cause of the error is the incorrect way of setting the ‘wc_notices’ in line 185 of class-wcmp-user.php
Can you check on your end and see if you are able to replicate the issue?

Thank you and best regards,

[purchase]

Hi,

Here’s the remaining attachments.

[purchase]

Hi,

Here’s the remaining attachments.

[MVX Support Ninja]

Hello,

We have tested it at our end and when we tried uploading an unaccepted file it gives me this error as you can see here (https://prnt.sc/xlpdp6). It seems to be some plugin / theme conflict.

May I know if you have checked marketplace plugin with WooCommerce and standard theme (storefront/twenty). Please deactivate all your plugin, except WooCommerce and WCMp + addon. You can then check the flow. If everything is working fine, in order to detect which plugin is causing conflict- please activate each plugin consecutively and check the flow.
Similarly, for theme conflict- please deactivate the current theme and check with standard WooCommerce theme (storefront/twenty) It is suggested to please perform these tests on your staging website and keep us posted with the outcome.

[purchase]

Hi,

Thank you for checking on your end.
I have confirmed that the error message is displaying properly when an unregistered user registers as a vendor via Vendor Registration screen.
However, the problem occurs when an existing non-vendor user registers as a vendor via Vendor Registration screen.

I have tested this in a freshly installed WordPress environment with only WooCommerce and WC Marketplace plugin installed.
Can you check on your end again and see if you can replicate the issue?

Thank you and best regards,

[MVX Support Ninja]

We see a different error message when we try to register a vendor with an existing non vendor account as you can see here (https://prnt.sc/xpmjzz).

Kindly check the same at your end with only Woocommerece and WCMp plugin + WCMp addons activated and share a video with us of the issue that you are facing.

[purchase]

Hi,

I’m sorry for the incomplete details.
Please login to WordPress first, then go to Vendor Registration and upload an unaccepted file.

Can you check on your end again and see if you can replicate the issue?

Thank you and best regards,

[MVX Support Ninja]

We will be testing it at our end and keep you posted by tomorrow.

[MVX Support Ninja]

We see a different error message when we try to register a vendor with an existing non vendor account and with an unaccepted file upload as you can see here (https://www.loom.com/share/0afb0ef6fcd849049b394106fcde1bf8)

Kindly check the same at your end with only Woocommerece and WCMp plugin + WCMp addons activated and share a video with us of the issue that you are facing.

[purchase]

Hi,

I’m sorry if the replication steps are not clear.
In your video, you are trying to register as a vendor without logging in.
Can you try below steps and confirm if you can replicate the issue?

1. Login to WordPress as an existing user. Make sure user is not yet a vendor.
2. Go to Vendor Registration screen. (You will know that you are accessing the page as a logged in user since the required Email Address field will not be displayed anymore)
3. Upload an unaccepted file.

Thank you and best regards,

[MVX Support Ninja]

Thank you for the detailed steps.
We have found the issue at our end and you can track it from here https://github.com/wcmarketplace/dc-woocommerce-multi-vendor/issues/646

[MVX Support Ninja]

As I can see the issue is fixed. So we are closing the ticket now. In case any issue arises kindly raise a new ticket.

[Author]

Posts