1.36 Can't delete Recorded TV entry (1 Viewer)

[Pablik]

Thanks for the new DLL. I'm not sure I did the right thing with the first one. TvBusinessLayer.dll exists in both "MediaPortal" and "MediaPortal TV Server". I put your first test version in "MediaPortal TV Server". Where does your test version belong?

The TV Server is the important one.

 

[framug]

This will remove the EPG problem as a possible source for your deletion problem. (There may be a problem with the code for grabbing by multiple tuners, or it may simply be that the arrangement of your broadcast EPG is not suitable for grabbing by multiple tuners.)

Hello,
I'm sorry but, I can't see link between grab EPG and delete file problem.

 

[Pablik]

Hmm, my guess is that MP is requesting PIN code to delete the recorded files. That is why the keyboard shows up.

 

[CyberSimian]

Hmm, my guess is that MP is requesting PIN code to delete the recorded files. That is why the keyboard shows up.

That could be what I am seeing on my MP 1.33 system. The difference compared to @rsbrux is that my system does not stop at the on-screen keyboard; instead, after displaying the keyboard for a fraction of a second, it then transfers immediately to the delete pop-up.

I suspect that few people use the "Delete" option on the context menu, so perhaps it has been this way for some time? I had a look at my "MediaPortal.log" (at DEBUG level), but there was no indication that the on-screen keyboard was being displayed. Puzzling.

-- from CyberSimian in the UK

 

[Pablik]

That could be what I am seeing on my MP 1.33 system. The difference compared to @rsbrux is that my system does not stop at the on-screen keyboard; instead, after displaying the keyboard for a fraction of a second, it then transfers immediately to the delete pop-up.

Can you check the pin code in MediaPortal.xml file? (section 'filemenu', entry 'pincode').
If the pin is empty then the keyboard shouldn't show up at all.

 

[CyberSimian]

Can you check the pin code in MediaPortal.xml file?

This is the "filemenu" section in my "MediaPortal.xml" file:

<section name="filemenu">
  <entry name="enabled">yes</entry>
  <entry name="pincode">
  </entry>
  <entry name="trashcan">
  </entry>
</section>

I notice that there are various other "pincodeX" entries in the xml file (where "X" is a numeric digit), although all seem to be empty.

-- from CyberSimian in the UK

 

[rsbrux]

The theory with the pin code is correct. I had enabled it for file menu, and when I entered the code into the dialog box, the recording was deleted. It never occurred to me that the recorded TV list would be considered a "file menu", but the mystery is now solved, and I have disabled it.
@Pablik I assume that your revised DLL was supposed to resolve the EPG errors. I have loaded it into the TV Server directory. Do you want new logs?
Should I also load it into the MediaPortal directory, or are these two different DLLs with the same name?

 

[Pablik]

This is the "filemenu" section in my "MediaPortal.xml" file:

<section name="filemenu">
  <entry name="enabled">yes</entry>
  <entry name="pincode">
  </entry>
  <entry name="trashcan">
  </entry>
</section>

I notice that there are various other "pincodeX" entries in the xml file (where "X" is a numeric digit), although all seem to be empty.

-- from CyberSimian in the UK

The TV plugin takes into account pincode from the filemenu section only. It's empty in your case so it's a bit of mystery to me where it comes from.

 

[Pablik]

@Pablik I assume that your revised DLL was supposed to resolve the EPG errors. I have loaded it into the TV Server directory. Do you want new logs?
Should I also load it into the MediaPortal directory, or are these two different DLLs with the same name?

Yes, please. I'd like to see what is going on. I need the TV server logs only.

PS: use the updated dll for TV server only

 

[rsbrux]

Today's TV Server logs are attached. I don't remember what time I loaded your latest DLL into the TV Server directory, but I restarted the system afterwards (maybe not immediately afterwards) and perhaps it will be evident from the logs.
Of course, it would be nice if the PIN dialog would indicate what input it's expecting.