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 SELLER ADDRESS FIELDS - CITY SHOULD BE A DEFAULT FIELDS LIKE THE COUNTRY so we can translate address in front end #71

Closed
Sophie-2e opened this issue Apr 10, 2024 · 2 comments
Assignees

Comments

@Sophie-2e
Copy link

Hello Team Dokan,

If the Country field works well in the Seller Address, it does not for the City which is manually added via text by the sellers, while he needs to select a country field (that indeed can be translated in WPML strings).

You can see the seller address on his store and in the store lists and in the My Account > Followers:

You can see in the image below tha sellers added the city in english 'Brussels', while in french it should be 'Bruxelles' and Dutch 'Brussel':

Screenshot 2024-04-10 at 14 56 15
Screenshot 2024-04-10 at 14 55 59
Screenshot 2024-04-10 at 14 55 43

This result in the address being half translated in front end where only the country will be in the right language but the city will be written as the seller has added it in the Seller Registration form or in Vendor Dashboard > Settings > Store > Address or in the Vendor Wizard or in the Verification Module (Vendor Dashboard > Settings > Verification).

This feature will also reduce the errors in address registration for both customers, sellers, and order delivery.

@pronob1010 pronob1010 self-assigned this Dec 20, 2024
@pronob1010
Copy link
Contributor

@imtiaz-pranto Bhai, I have discussed this with @jamil-mahmud Bhai. As WooCommerce doesn't support this, we won't be adding support for full address translation and I also investigated the given scenario there. The state and country name are working as expected, so this issue may not be valid anymore.

Image

@jamil-mahmud
Copy link

@pronob1010 vai, according to your finding from our side we won't further progress on this unless heavy requirement comes on this. That is why closing this according to current solution

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