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.

Sign up for GitHub

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

Jump to bottom

Added from Browse uses incorrect URI #829

Closed
2 of 10 tasks
jaedb opened this issue Apr 9, 2022 · 2 comments
Closed
2 of 10 tasks

Added from Browse uses incorrect URI #829

jaedb opened this issue Apr 9, 2022 · 2 comments
Labels
bug confirmed A bug that has successfully been replicated and can be resolved

Comments

@jaedb
Copy link
Owner

jaedb commented Apr 9, 2022

Iris version

3.62.0

Operating system(s) affected

  • Windows
  • MacOS
  • iOS
  • Android
  • Linux
  • Other

Browser(s) affected

  • Firefox
  • Chrome
  • Edge
  • Other

What happened?

Adding a track from Browse/Files will use an incorrect URI. It seems the name element is missing.

  1. Go to Browse
  2. Go to Files, and into a folder (eg "My Folder")
  3. Add to queue
  4. Click on newly-added track(s)
  5. Observe URI is missing /My Folder before the encoded URI

Logs

No response
@jaedb jaedb added bug confirmed A bug that has successfully been replicated and can be resolved labels Apr 9, 2022
@chiefy
Copy link

chiefy commented Apr 13, 2022

Same as #819 ?

jaedb added a commit that referenced this issue Sep 4, 2022
@jaedb
Browse URI + name syntax, fixes #829
0f950ed
jaedb added a commit that referenced this issue Sep 4, 2022
@jaedb
Removing iris:browse: URI prefix, fixes #829
e3989c2
@jaedb
Copy link
Owner Author

jaedb commented Sep 4, 2022

Will be included in next release

@jaedb jaedb closed this as completed Sep 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug confirmed A bug that has successfully been replicated and can be resolved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chiefy @jaedb