<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""><blockquote type="cite" class=""><div class="">On Nov 9, 2018, at 4:30 PM, Jonatan Lindblad <<a href="mailto:lindbladjonatan@gmail.com" class="">lindbladjonatan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Den 2018-11-06 kl. 13:18, skrev Jim Abernathy:<br class=""><blockquote type="cite" class="">I just noticed in mythfrontend a formating issue on Information Center -> System Status -> Listing Status.<br class=""><br class="">At the bottom, Your Subscription Expires on Sunday Dec 2 2:19pm is what mine says. However my subscription really expires on Dec 2, 2019.<br class=""><br class="">I just got the warning email from SD and I renewed it for another year. That's why I noticed the display problem.<br class=""></blockquote><br class="">This text is stored in the database when the guide data is updated so this is probably from before you renewed the subscription. The code that builds this text will include the year even if your DateFormat setting does not and if the subscription does not expire within the current year. So if the expiration date is always included in the SD data then you can probably expect the year to be included next time you check.<br class=""><br class="">Jonatan<br class=""></div></div></blockquote><div class=""><br class=""></div>I’m not sure I understand your explanation, but I updated to the most current mythtv software on both the frontend and backend. mythfilldatabase ran last night and the formatting issue remains. It’s like it’s using the Year numbers as a time.</div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""></div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">Jim A</div><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""></div></div></blockquote></div></blockquote><br class=""></div><div>Just an additional thought. When I was using SchedulesDirect (non-JSON) the console output would show you the expiration date of your ScheduleDirect subscription. I’m on XMLTV JSON SchedulesDirect now and it does not display anything about your subscription expiration date.</div><div><br class=""></div><div>Could this be an issue with XMLTV JSON not updating the subscription expiration date in the database???</div><div><br class=""></div><div>Jim A</div><div><br class=""></div><br class=""></body></html>