Hey, i think we were all just running around our own tails in this case.
But that is sort of along the lines which i started thinking. Instead of needing scripts etc, first you could reinstall the source since that should be easily doable. I suspect you tried this and and did not work, so bibsuspected there may be an issue with the database being compromised.
So in the end just for posterity, what exactly did the service staff have to do? As in what did they fix?
Anyhow, daily backups, or if data is mostly not chamging every day, whenever there is a major change. That way next time it happens. You just nuke the database and the php files for the cms. Reinstall and recover the database.
That hosting provider has backup options you should maybe have a look at.
Good luck and hope you can adress the cause so it does not happen again.
|