Jump to content

Removing folders from library, manage folders error


Go to solution Solved by Luke,

Recommended Posts

Posted

Hi,

 

I have version 3.2.60.0, and I went to delete a folder from my TV library.  Folders as per below.

  • \\networkshare1\TV
  • G:\TV
  • \\networkshare2\TV
  • \\networkshare3\\tv

I pressed on the remove button on the G: entry and it prompted with the warning and I confirmed and migrated out of that section.   Then I went back in later after a library scan to notice that the first entry had been removed and the G: entry was still there. I then clicked on the G: entry again and 'removed' it and found that the network entry below it was removed.  I couldn't get it to delete until I removed all entries and it was the last one.  Then I had to add all the network paths back in.

 

Not sure if this a bug?

Posted

Hi,

 

I have version 3.2.60.0, and I went to delete a folder from my TV library. Folders as per below.

  • \\networkshare1\TV
  • G:\TV
  • \\networkshare2\TV
  • \\networkshare3\\tv
I pressed on the remove button on the G: entry and it prompted with the warning and I confirmed and migrated out of that section. Then I went back in later after a library scan to notice that the first entry had been removed and the G: entry was still there. I then clicked on the G: entry again and 'removed' it and found that the network entry below it was removed. I couldn't get it to delete until I removed all entries and it was the last one. Then I had to add all the network paths back in.

 

Not sure if this a bug?

I'm not a dev or anything but, out of curiosity, was your G path still valid? I mean was stuff still reachable following that path?

 

I had the same issue before and my hunch was that when an invalid path is deleted, emby deletes the first valid path in the list.

 

I raised it on the forum but i never found out if that was right. I just resorted to not deleting invalid paths via the interface.

 

I might be wrong though... :)

 

Sent from my SM-G920W8 using Tapatalk

Posted

I'm not a dev or anything but, out of curiosity, was your G path still valid? I mean was stuff still reachable following that path?

 

I had the same issue before and my hunch was that when an invalid path is deleted, emby deletes the first valid path in the list.

 

I raised it on the forum but i never found out if that was right. I just resorted to not deleting invalid paths via the interface.

 

I might be wrong though... :)

It was now an empty folder, but the path G:\TV was still valid and accessible.   Good thought though.

  • Solution
Posted

This is a bug affecting installations of a certain age or greater, and we're still trying to track it down. It won't happen anymore on a brand new server installation. thanks.

  • Like 1
Posted

I'm in the process of migrating my current Window 10 server install to an Ubuntu VM, so will not longer have an old installation.   If I can help in testing of the current install, I'm happy too.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...