I wrote back in February about how ia archiver had got into a site's admin function and triggered the deletion of the entire database.
Well, it turns out that wasn't the only site affected. Just discovered another site that had the same problem. The other one is in development and it's really hard to get hold of the customer, so we hadn't noticed the problem.
The customer was supposed to call at 11:30 this morning to complete a few details, but as always, he failed to do so. But that didn't stop me having to spend the entire morning rebuilding his site from scratch!
Typical. Because it was in development and not moving when I checked all of the sites it was forgotten about. It's been around that long that the sample site is somewhere different to the rest of the ongoing samples.
You live and learn!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment