[mythtv-users] mythtv-frontend format issue

[Jim Abernathy]

On 11/10/18 1:08 PM, Bill Meek wrote:
> On 11/10/18 11:58 AM, James Abernathy wrote:
>>
>>> On Nov 10, 2018, at 11:09 AM, Jonatan Lindblad 
>>> <lindbladjonatan at gmail.com> wrote:
>>>
>>> Den 2018-11-10 kl. 15:48, skrev James Abernathy:
>>>>>
>>>>>> On Nov 9, 2018, at 4:30 PM, Jonatan Lindblad 
>>>>>> <lindbladjonatan at gmail.com <mailto:lindbladjonatan at gmail.com>> 
>>>>>> wrote:
>>>>>>
>>>>>> Den 2018-11-06 kl. 13:18, skrev Jim Abernathy:
>>>>>>> I just noticed in mythfrontend a formating issue on Information 
>>>>>>> Center -> System Status -> Listing Status.
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> I just got the warning email from SD and I renewed it for 
>>>>>>> another year. That's why I noticed the display problem.
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> Jonatan
>>>>>
>>>>> 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.
>>>
>>> I was trying to say that it is not a formatting issue.  First of 
>>> all, December 2 2019 is a Monday.  Second, there is no way the code 
>>> will format the year 2019 as 2:19pm, see [1][2].
>>>
>>>> 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.
>>>>
>>>> Could this be an issue with XMLTV JSON not updating the 
>>>> subscription expiration date in the database???
>>>
>>> Yes, that explains why the message hasn't been updated.
>>>
>>> Jonatan
>>>
>>> [1] 
>>> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythtv/datadirect.cpp#L450
>>> [2] https://doc.qt.io/qt-5/qdatetime.html#toString 
>>> <https://doc.qt.io/qt-5/qdatetime.html#toString>
>>
>> Sounds like that field will never be updated on my system because of 
>> XMLTV JSON usage.  So is the date in the database wrong now and will 
>> never be changed?  Is there an SQL command I could do to display and 
>> then clear that field?
>>
>> Jim A
>
> curl -H Accept:Application/JSON 
> localhost:6544/Myth/GetSetting?Key=DataDirectMessage\&HostName=_GLOBAL_
>
For me the curl command yields:

jim at mythbuntu:~$ curl -H Accept:Application/JSON 
localhost:6544/Myth/GetSetting?Key=DataDirectMessage\&HostName=_GLOBAL_
{"String": "Your subscription expires on Sun Dec 2 2:19 PM"}

> I'm trying tv_grab_zz_sdjson_sqlite for a completely unrelated
> reason, but this what I see in the DB and on the Information
> screen:
>
>     Your subscription expires on Fri Mar 8 2019 11:22 AM    --- 
> tv_grab_zz_sdjson_sqlite response
>     Your subscription expires on Fri Mar 8 (2019) 11:22 AM  --- SD DD 
> response
>
> Looks good to me. What's the name of your grabber?

I'm using tv_grab_zz_sdjson_sqlite.

Use to be mythfilldatabase would display the subscription expires 
message, but it doesn't on my machine.

Jim A