We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When audio files use non-roman filenames they don't always play using the WordPress media player.
https://www.webonary.work/nanai/songs/ https://www.webonary.work/nanai/language/audiostories/?lang=en The above pages have this problem for both UI languages. The English and Russian tabs aren't exactly the same.
On the Russian Songs page you can click on any of the files and the first few play (it varies between 2-4) but won't play all 6.
https://www.webonary.org/nanai/songs/ is using roman filenames and all media files will play.
I couldn't find conclusive information about this but it seems like a WordPress bug. Can you confirm this?
The text was updated successfully, but these errors were encountered:
This is happening because the editor is saving the file name as HTML entities, which are invalid in a URL.
https://www.webonary.work/nanai/files/Грехопадение-Ноябрист-05082015.wav
I will check if there is anything we can do about it.
Sorry, something went wrong.
phillip-hopper
No branches or pull requests
When audio files use non-roman filenames they don't always play using the WordPress media player.
https://www.webonary.work/nanai/songs/
https://www.webonary.work/nanai/language/audiostories/?lang=en
The above pages have this problem for both UI languages. The English and Russian tabs aren't exactly the same.
On the Russian Songs page you can click on any of the files and the first few play (it varies between 2-4) but won't play all 6.
https://www.webonary.org/nanai/songs/ is using roman filenames and all media files will play.
I couldn't find conclusive information about this but it seems like a WordPress bug. Can you confirm this?
The text was updated successfully, but these errors were encountered: