-
Notifications
You must be signed in to change notification settings - Fork 205
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
WPML - DOKAN : VENDOR STORE URL SLUG TRANSLATION NOT WORKING - Incompatibility DOKAN - well translated in WPML but page not found in front end #2123
Comments
also reported here by @YeasinArafat1998 : #2081 |
@shohag121 Please analysis first. Is is possible or not? |
Hello @Sophie-2e, Thank you for reporting the issue. Right now, the explanation video you gave is expired. Thank you. |
Hello @shohag121 , you're welcome, yeah I cannot keep the videos forever and this video was shared in customer support ticket a year ago and unfortunately, me I am not paid to report Dokan bugs, nor to test Dokan, nor shoot videos for Dokan developers. But the issue is simple, if we translate the slug for vendor store, url store in other languages will return 404 error: |
Analysis Report@shams-sadek1981 Bhai, We might achieve this by registering additional This needs additional analysis. |
@shohag121 I also reopened here 2 weeks ago in the WPML repository : getdokan/dokan-wpml#58 |
Hello @shohag121 @YeasinArafat1998, can we hope to have this feature released this year? |
Bug Description
WPML - DOKAN : VENDOR STORE URL SLUG TRANSLATION NOT WORKING - Incompatibility with DOKAN> Store url slug well translated in WPML but page not found in front end: https://share.vidyard.com/watch/bR4Uhp1wJL8pUCWFtBLaTW
Step To Reproduce
https://share.vidyard.com/watch/bR4Uhp1wJL8pUCWFtBLaTW
Expected Behaviour
Don't have 404 error on the translated store URL and don't be redirected to the home page on the translated page
Actual Behaviour
https://share.vidyard.com/watch/bR4Uhp1wJL8pUCWFtBLaTW
Additional Information
No response
Environment (please complete the following information)
The text was updated successfully, but these errors were encountered: