Hi, I started noticing this with my DNN sites a few weeks ago after moving to 4.7. There is definitely an issue and nothing suggested so far fixes it. Ever since installing DNN 4.7 and re-creating my portal from fresh (I didnt upgrade) I have NEVER turned on the schedule filesync - so personally I would rule that out completely. As with default install though the autosnyc setting is checked in my host settings.
The upshot for myself is sporadically entries in the files table disappears. This causes:
1) The logo to disappear
2) Images in the Events Module disappear
3) Images in another module I run 'ImageLinks' disappear
4) Vendor banners disappear
Ther must all be re-added manually only to disappear again a while later!
It is unbelievably frustrating... my file names do not contain apostrophes though they do contain underscores and hyphens (but I believe these a valid in file names???)
I do occassionally run the synchronise function in the file manager of my various portals. I do this when I have for example sent an image by ftp...
Also, if its any help the only things running in host > schedule are:
1) DotNetNuke.Modules.Events.EventNotification, DotNetNuke.Modules.Events
2) DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
3) DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE
but i dont really see how these would affect anything - indeed I have turned them all off and ran them individually one by one to see if they cause any entry loss in the files table and they dont appear to.
So where do we go from here? THIS IS SUCH A HUGE PROBLEM... If I cant get a solution to this I'm going to have to ditch DNN because I cant have logos and images etc just disappearing randomly every few days or weeks...
PLEASE PLEASE HELP!!!
(p.s. I dont think the above post refering to Charles Nurse has anything to do directly with this issue... thats seems to be to do specifically with file sync in host file manager and also to do with problems regarding files not appearing in host file manager... no offence I could well be wrong)