Re: [SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-07-12 Thread dolodobendan
afriend wrote: > Native support for more tags, related to classical music or not, would > be nice, agreed. But my guess is that it won't probably happen anytime > soon. It appears it would take quite a lot of work and testing to set it > up with all the changes to the database and creating the

Re: [SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-07-12 Thread afriend
Native support for more tags, related to classical music or not, would be nice, agreed. But my guess is that it won't probably happen anytime soon. It appears it would take quite a lot of work and testing to set it up with all the changes to the database and creating the corresponding browse

Re: [SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-07-11 Thread dolodobendan
afriend wrote: > -Kind of- means that there's still a quirk in the menu creation part I > need to work out. But that's only related to compilation albums showing > up on the second menu level where they shouldn't.. So nothing serious. > As for custom tags... I don't use custom tags (with my

Re: [SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-07-11 Thread afriend
-Kind of- means that there's still a quirk in the menu creation part I need to work out. But that's only related to compilation albums showing up on the second menu level where they shouldn't.. So nothing serious. As for custom tags... I guess that might work. I don't use custom tags (with my

Re: [SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-07-10 Thread dolodobendan
afriend wrote: > I thought CustomBrowse and MultiLibrary used utf-8 allowing for special > characters like umlauts. Anyway I stopped using CustomBrowse and > MultiLibrary (since they're no longer maintained and all) and created my > own plugin. It basically achieves what those two used to do

Re: [SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-07-09 Thread afriend
I thought CustomBrowse and MultiLibrary used utf-8 allowing for special characters like umlauts. Anyway I stopped using CustomBrowse and MultiLibrary (since they're no longer maintained and all) and created my own plugin. It basically achieves what those two used to do for me: define libraries

Re: [SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-06-21 Thread dolodobendan
Still a thing with the latest nightly build. I had a look at the links in Home / My Music. A comparison between the audiobook and the classical music link shows that not all necessary info makes it to the link: Code:

[SlimDevices: SqueezeCenter] WebUI: Custom browse menu with umlaut not accessible (but it is with Material)

2019-06-17 Thread dolodobendan
When I click on this menu I get an error message: Code: 404 Not Found: player=xxx[/B] I think it worked at some point. With the Material skin, I can access this menu, iPeng also has no problems. QLMS 7.9.2@2.04 x64 (digimaster) with perl