Files Plugin crashes when there is an ' in the file name.

[cbgifford]

Hi Martin,

I checked the Wiki again just to make sure and the original Files is supposed to update the "NPVR database according". I reloaded the old one and moved something without an ' in it and it did update the database to where I could see and play it.

[mvallevand]

I checked the Wiki again just to make sure and the original Files is supposed to update the "NPVR database according". I reloaded the old one and moved something without an ' in it and it did update the database to where I could see and play it.

I totally get that, since it is updating the database for me. I am trying to find out why that doesn't work for you. Maybe after a move try and play the file from Recordings so I can see where NextPVR thinks it is.

Martin

[cbgifford]

I totally get that, since it is updating the database for me. I am trying to find out why that doesn't work for you. Maybe after a move try and play the file from Recordings so I can see where NextPVR thinks it is.

Martin

I misunderstood you, sorry Martin. It's not in the Ready Recording at all to even try and play. Ok, I'm going to look at the db record of one I move before I move it and again right after I move it and see what happens to it using DB Browser For SQLite

The filename field in the scheduled_recording table does not change to the new location.

Which menu option are you using, Move or Archive? I've been using Move because I haven't resolved my permissions issue yet with the archive feature.

[mvallevand]

I misunderstood you, sorry Martin. It's not in the Ready Recording at all to even try and play. Ok, I'm going to look at the db record of one I move before I move it and again right after I move it and see what happens to it using DB Browser For SQLite

The filename field in the scheduled_recording table does not change to the new location.

Which menu option are you using, Move or Archive? I've been using Move because I haven't resolved my permissions issue yet with the archive feature.

I'm using Move. I do spew out some junk to the console debug. If you have sysinternals tools installed run dbgview to see it. I can put more info on the file check against the database if you'd like.

Martin

[cbgifford]

I'm using Move. I do spew out some junk to the console debug. If you have sysinternals tools installed run dbgview to see it. I can put more info on the file check against the database if you'd like.

Martin

Don't know how informative it is but the output from dbgview is attached...

[mvallevand]

It's more the location of the files.

The command that is being issued is

update SCHEDULED_RECORDING set filename = @target where filename like @filename

@target is \\HT01\Recordings\All in the Family\All in the Family.S08E16.Archie and the Super Bowl.ts
@filename is \\DT01\Recordings\All in the Family\All in the Family.S08E16.Archie and the Super Bowl.ts

Martin

[cbgifford]

It's more the location of the files.

The command that is being issued is

update SCHEDULED_RECORDING set filename = @target where filename like @filename

@target is \\HT01\Recordings\All in the Family\All in the Family.S08E16.Archie and the Super Bowl.ts
@filename is \\DT01\Recordings\All in the Family\All in the Family.S08E16.Archie and the Super Bowl.ts

Martin

There's the rub, \\DT01\Recordings. It's D:\Recordings in the database. Where is it picking up \\DT01\Recordings from?. I would have assumed you would use the OID to look up the record instead of the original location and update it that way.

[cbgifford]

There's the rub, \\DT01\Recordings. It's D:\Recordings in the database. Where is it picking up \\DT01\Recordings from?. I would have assumed you would use the OID to look up the record instead of the original location and update it that way.

You wouldn't know the OID, I think I know what's happening now.

[mvallevand]

I would have used the oid but tmrt used the filename so as I wrote I didn't change db logic, just changed it to use parameters. That is why I don't understand why you say it works differently

I assume \\DT01\Recordings is coming from your Files configuration for the source Location.

Martin

[cbgifford]

Here's what happened. I configured files to use the UNC path instead of the physical path trying to make it work on any client. For that to happen, I would also need to configure the default recording directory to use the UNC path as well instead of the drive letter. What caused me to do that in the first place was that the recording machine was having hardware issues so I moved the tuners to my desktop.

All I need to do to fix the problem is change the source recordings back to the physical drive instead of the UNC patch. On your end, I would add a check to make sure the source exists in the database and if it doesn't make a log entry for it then continue with the move.

Awesomeness!