Open gabrielsoldani opened 3 months ago
You might want to manually edit your custom profiles for now. I've been digging through the code to see if im capable of adding profile editing functionality back in and it looks like a significant undertaking for myself, might be do-able though since some of the controls still exist in the plugin code.
had a similar error with the protocol, but my file contained and empty protocol=""
attribute which wasn't valid either. Removing the entire attribute manually helped.
After upgrading Jellyfin to 10.9.z and migrating to the DLNA plugin, I've copied my
/config/dlna/user
directory over to/plugins/configurations/dlna/user
and I'm running into issues with one of my profiles (created using the Web interface in 10.8.z).This is my profile:
First, I ran into this issue:
In the
TranscodingProfiles
section of the profile, there are problematicTranscodingProfile
entries withprotocol
attribute set to an empty string. The 10.8.z interface for creating profiles generated profiles with such entries when the protocol input field is empty (rather than omitting theprotocol
XML attribute), so these should be accepted for backwards compatibility.As a workaround, I tried editing the profile to omit the
protocol
attribute (and other empty options):But this triggered a different error:
It seems like
protocol
is expecting a lower-case"http"
instead of the capitalized"Http"
. TheMediaServerProtocol
enum (defined here) has lower-case members since jellyfin/jellyfin#11126, but before that, it had capitalized members when it was introduced in jellyfin/jellyfin#10153.As a second workaround, I've edited the profile to change
protocol="Http"
toprotocol="http"
and it worked.Since these profiles were generated by stable versions of Jellyfin, they probably should be supported for backwards compatibility.