Finally got time to looking at this, and this will be fixed using MaterialSkin 2.9.9 and APK version 0.2.1 - both still to be released. Currently Material tries to embed the PDF in the current page, which works for desktop but not mobile. Material will no longer do this for android, and instead will open as a URL. The APK will catch this, and if filename endswith ".pdf" it will set the correct file type and then ask Android to handle this. Android should then use whatever PDF handler you have installed to show the file.
Results 8,681 to 8,690 of 8988
Thread: Announce: Material Skin
-
2022-07-02, 04:54 #8681
- Join Date
- Mar 2017
- Posts
- 3,630
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
2022-07-02, 04:56 #8682
- Join Date
- Mar 2017
- Posts
- 3,630
Can't say for other controllers, or the default skin, but Material will check if the URL already exists - so it could just be Material blocking this. The reason for this is that Material uses the URL presence in favourites to know whether to show "Add to favourites" or "Remove from favourites"
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
2022-07-02, 04:57 #8683
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 9,276
-
2022-07-02, 05:03 #8684
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 9,276
-
2022-07-02, 05:19 #8685
- Join Date
- Feb 2019
- Posts
- 104
Hi,
I have what seems to be a small bug to report.
When adding the parameter $HOST to a weblink in the action.json file, the target link is added to the current location. For example:
{
"album":[
{
"title":"Album details",
"weblink":"$HOST:5000/LMSalbum#$ALBUMID#$ID"
}
],
"track":[
{
"title":"Album details",
"weblink":"$HOST:5000/LMSalbum#$ALBUMID#$ID"
}
],
"system":[
{
"title":"Player",
"weblink":"$HOST:5000/LMSplaylist#$NAME#$ID"
}
]
}
The first two actions work, but the last one results in this adress (concatanation of the material adress + target): "http://192.168.1.177:9001/material/192.168.1.177:5000/LMSplaylist"
-
2022-07-02, 05:44 #8686
- Join Date
- Mar 2017
- Posts
- 3,630
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
2022-07-02, 05:58 #8687
- Join Date
- Feb 2019
- Posts
- 104
-
2022-07-02, 06:07 #8688
- Join Date
- Feb 2019
- Posts
- 104
I figured out that the album action in fact only works from the My Music > Albums view. If click on the album action item from any other view (for ex: My Music > Random Albums, or My Music > Album Artists > artist xyz > album) it does not work...
-
2022-07-02, 06:34 #8689
- Join Date
- Mar 2017
- Posts
- 3,630
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
2022-07-02, 06:44 #8690
- Join Date
- Feb 2019
- Posts
- 104