Hi everyone, I'm new here and I need some help.
I'm trying to change the admin dashboard language to Vietnamese, but I don't know how to do it and I couldn't find any official guide. I've searched on Google and tried several solutions, but nothing worked.
Can anyone please help me with this? I'd really appreciate it. Thank you so much!
#change admin dashboard to vietnamese
1 messages · Page 1 of 1 (latest)
hello there, sorry for this, but I start the project with default command in https://docs.medusajs.com/learn/installation and it only have README.md tsconfig.json vite-env.d.ts in src/admin; can you give me a hint, what to do from here, thank you very much
Hi @onyx yoke
The link shared by @forest wyvern was more about contributing to the Medusa project
For a user approach, you'll need to log in into your Admin Dashboard and follow this path : Settings > Profile (Under the My Account sub group) > Profile (click Edit) button.
Then you'll have a list scrollable of languages Medusa supports, Vietnamese has been translated a few months ago by some community members so you can now enjoy it on the dashboard 🙌
hi Adil, thank you for your help. may I ask why my medusa starter only have 6 language, and doesn't have vietnamese, can you guide me to setup starter project just like you do, thank you very much for your help.
Of course, can you share your Medusa version with me ?
"dependencies": {
"@medusajs/admin-sdk": "2.8.4",
"@medusajs/cli": "2.8.4",
"@medusajs/framework": "2.8.4",
"@medusajs/medusa": "2.8.4",
"@mikro-orm/core": "6.4.3",
"@mikro-orm/knex": "6.4.3",
"@mikro-orm/migrations": "6.4.3",
"@mikro-orm/postgresql": "6.4.3",
"awilix": "^8.0.1",
"pg": "^8.13.0"
}, here it is
Got it, then have you tried to scroll inside the list of languages ?
the default username is [email protected]
mine is chrome in macos, which should I use
I have the same issue don't worry, I don't know why though 🤔
Wait can you check if the language is shared btw ?
how can I check it
I made some changes but wanted to know if changing it on my side was reflected on yours, but it's not the case
sure, can you show me your setup script to get to the point show in your video so I could try
I'm using the same version as yours, it was just in local development
Can you try locally if you can scroll inside the list of languages ?
On my side I've built the proejct and runned it, no issues + locally too
I'm wondering if there is not an issue with how the project is served, but I don't know, just a hypothesis
Also worth checking the Medusa GitHub for any related issues like this one
Otherwise you could have a hacky way of selecting it when the dropdown is opened and with the "Emulate a focused page" using Chrome 😆 :
const xpath = "//span[text()='Tiếng Việt']";
const spanElement = document.evaluate(xpath, document, null, XPathResult.FIRST_ORDERED_NODE_TYPE, null).singleNodeValue;
spanElement.parentNode.click()
I've found something similar on the GitHub issues :
https://github.com/medusajs/medusa/issues/12548
yeah, it's a bug, and it doesn't solve yet
Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: <button.transition-fg inline-flex items-center justify-center overflow-hidden rounded-md outline-none disabled:bg-ui-bg-disabled disabled:shadow-buttons-neutral disabled:text-ui-fg-disabled text-ui-fg-subtle bg-ui-button-transparent hover:bg-ui-button-transparent-hover active:bg-ui-button-transparent-pressed focus-visible:shadow-buttons-neutral-focus focus-visible:bg-ui-bg-base disabled:!bg-transparent disabled:!shadow-none h-7 w-7 p-1>
Ancestor with aria-hidden: <div.bg-ui-bg-base shadow-elevation-modal border-ui-border-base fixed inset-y-2 flex w-full flex-1 flex-col rounded-lg border outline-none max-sm:inset-x-2 max-sm:w-[calc(100%-16px)] sm:right-2 sm:max-w-[560px] data-[state=open]:animate-in data-[state=closed]:animate-out data-[state=closed]:fade-out-0 data-[state=open]:fade-in-0 data-[state=closed]:slide-out-to-right-1/2 data-[state=open]:slide-in-from-right-1/2 duration-200#radix-:r23:>
Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with
disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be us...
there is a high chance that this is some kind of css issue