Orphaned Files

I've been using the tool "Search orphaned files" to search for MP3 files not linked to a sermon. This works without any problems. However, I'm starting to notice that the tool is displaying files that are not orphaned because they are indeed attached to a sermon. Is there a way force a rescan for orphaned files?

It always does a scan when you press the button. The result isn't stored anywhere. So it's always "live".

Do you see a pattern of which files the search fails? The method basically gets a list of files on the hard disk and a list of files references in the database and then deletes all matches. WHat is left is the orphaned list.

I've not identified a pattern. I've been consistently naming our MP3 files in the format (YYYYMMDDMessage-Speaker) for example (20150426Message-DrSpeaker.mp3). I will then upload the files via FTP to our Joomla server.

I've wondered if is a browser issue. I have one computer with IE at the church that I use but I use Chrome on my laptop when I'm offsite. I've been working on adding our old sermons to SermonSpeaker remotely. This is why I've got a large number of orphaned files.

I'm still looking for a pattern. If I add the file again from my laptop, the orphaned file does not show up again. So, I just delete the original sermon that was uploaded.

I found that if I go to the "Search orphaned files" tool, copy the relative path of the sermon of one of the existing sermon that should not be orphaned, navigate back to the specific sermon, paste the link for the file location, and then save the sermon again. The sermon now disappears from the orphaned list. This will save me some clean-up time. This somehow associates the file with the sermon article once again.

However, I'm still able to listen to the sermon audio file prior to making this re-association.

Interesting....

Was the file previously stored differently? Like as an absolute URL? Or without a leading slash or so?

The browser doesn't make a difference. It's all done on the server, Maybe the connection speed may play a role, but I doubt it.

I've not used absolute URLs. However, I did notice that the audio file location had added an additional "directory slash" to the path of the file. If I remove this extra slash then the file is no longer orphaned. The audio file continues to play either way. I can quickly remove the extra slash. I'm just not sure how it's getting there since I'm adding files using the tool.