Did EPG behavior change in 7.0.5?

[jrea8830]

Hi,

I recently updated to 7.0.5, I was on 7.0.2 just before the upgrade. 

After the upgrade I got a strange error that was stating my EPG file (which is raw XML) was in an unsupported compression and could not be loaded. After a while, I figured out that if I forced my EPG into a .gz compression then the error goes away. 

My question is if this is a new requirement or change? In 7.0.2 it was able to use the raw XML file for my EPG listing, maybe I somehow got lucky and it never was supposed to do that. 

I figured I'd come ask the experts!

TIA,
James

[mvallevand]

Yes explained here https://forums.nextpvr.com/showthread.php?tid=66905 for a dropbox user. There is is patch to override this but it is the provider's issue setting a bad content type.

Martin

[Basche]

Yes explained here https://forums.nextpvr.com/showthread.php?tid=66905 for a dropbox user.  There is is patch to override this but it is the provider's issue setting a bad content type.

Martin

Hi Martin, is there a way we can get the patch, or a way to roll back to previous 7.0.3 when it was working before?

[mvallevand]

https://forums.nextpvr.com/showthread.ph...#pid607140 has the patch.  It allows entering a a valid content type on EPG URLs by adding |Content-Type=text/xml to override stupid defaults like DropBox sends.

Martin

[Basche]

https://forums.nextpvr.com/showthread.ph...#pid607140 has the patch.  It allows entering a a valid content type on EPG URLs by adding |Content-Type=text/xml to override stupid defaults like DropBox sends.

Martin

Thanks for this, but how do I apply this when using docker?

[mvallevand]

See https://forums.nextpvr.com/showthread.ph...#pid586679

Martni