Hi all,

 

I have just made the move from 4.7 to 5.0-beta7 and have come up with a bit of a problem...

 

I currently only have two user shares: 'Media' and 'Files & Programs', both of which seem to be 100% accessible since the upgrade.

 

However, when browsing the GUI for new features etc, i clicked the 'Files & Programs' link, under the shares tab and was presented with the 'Share Settings' heading, but with 'Share Files has been deleted. OK (button)' underneath.

 

I then went back to the shares main page and clicked the folder button next to 'Files & Programs' which loaded a page saying...

 

Index of /mnt/user/Files

Warning: scandir(/usr/local/emhttp/mnt/user/Files ): failed to open dir: No such file or directory in /usr/local/emhttp/plugins/indexer/Browse.php on line 19 Warning: scandir(): (errno 2): No such file or directory in /usr/local/emhttp/plugins/indexer/Browse.php on line 19 Warning: array_diff(): Argument #1 is not an array in /usr/local/emhttp/plugins/indexer/Browse.php on line 19 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/indexer/Browse.php on line 19

 

But as i said, the share seems to be working perfectly.

 

Any ideas?

 

N.B i had to run the 'new permissions utility' after upgrading as i initially wasn't able to access anything; disks or shares.

Ok, in the end i backed up the contents of the share, then emptied the share folder, but could still not gain access to delete it.

 

I tried to create a new share with the same name which, instead, renamed the original share to 'files' and then brought back 100% functionality.

 

So the share is now called 'Files and Programs' and seems to be working well 

Ok, in the end i backed up the contents of the share, then emptied the share folder, but could still not gain access to delete it.

 

I tried to create a new share with the same name which, instead, renamed the original share to 'files' and then brought back 100% functionality.

 

So the share is now called 'Files and Programs' and seems to be working well  

I think the issue is the "&" in the share name.   This is a bug.  

 

I'm moving this thread to the 5.0 Development forum where is will be more likely to be noticed.  It does not belong under general support.

 

Joe L.

I thought it might have something to do with the '&', which is why i ended up going with 'and' instead 

 

Sorry about the incorrect placing, i was struggling to find an appropriate heading.

I had a similar message when I was trying to remove my lost+found directory after I had copied what I wanted out of it. In the end I deleted it from the command line via telnet. However, the share only disappeared from the UI once I stopped and started the array.