Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dokan vednor edit page does not save the email field #769

Closed
rashedripon opened this issue Feb 11, 2020 · 2 comments
Closed

Dokan vednor edit page does not save the email field #769

rashedripon opened this issue Feb 11, 2020 · 2 comments

Comments

@rashedripon
Copy link

Description of the bug:
When you edit a vendor profile from Dokan > Vendors > Edit vendor. The email field is unable to be saved - https://prnt.sc/r0zabv. It happened to one of the user and the issue they are expecting is -
"This is a serious problem because the Dokan vendors who have the empty field in ‘Email Address’ are not receiving any notifications, such as ‘New Order notifications- and that is having a devastating effect on sales and the confidence of both vendors on the website and their customers."

How to reproduce:

  1. Register a vendor
  2. Navigate to Dokan > Vendors > Edit the newly registered vendor
  3. Check the email field, it is not saved.

Expected behavior:
The email should show in the email field.

@alamgircsebd
Copy link
Contributor

We solved this issue, hope next release will get this updates.

@looknear
Copy link

looknear commented May 5, 2020

It is related to very old report i gave about sync between "vendor" info and "user" info.
if the admin change something in the product of the vendor - the ownership is transferred to the admin, and then, the product owner get "author" as "shop manager" or any nickname your admin have.
when fixing it - and setting back the product to belong to the Vendor. then when the problems start...
the nickname of the vendor become the admin nickname.... "shop manager" or "admin" ...
and then you need manually find the vendor and change its info in the users management back-end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants