I had plenty of “orphaned” relationship records, and security suite records, but it was caused by my own large successive imports (done by php code, not by the “wizard”) on my development machine. As I was fixing the Import routine, I kept deleting things over and over, but traces were left behind.
Basically, what I mean is that the DB doesn’t seem to enforce “cascaded deletes”, maybe the application level handles that, but you might want to check what all those security suite records are pointing to - is it something real, something still in your DB, or is it a lost link?
@Will or anybody: Could somebody explain what exactly this scheduled script does:
“removal of documents from the file system” ?
Does it automatically remove files saved in the /upload folder? when no longer referenced in the database (e.g. the “notes” table?)
If yes, that would be great for pruning the system. We could just delete old database-entries and have SuiteCRM take care of deleting the files. But I’m not confident that’s what’s going to happen… Anybody have any experience with this?
Funny enough, at first glance I can’t spot any file deleting commands in there. I would say it deletes just directories, unless I’m missing something.
$return=true; is just setting a variable that tells the calling function whether there was success or not. It doesn’t really change whether the rows are deleted…