You may have noticed my site went down for a few hours today. I had two issues, one of which I am eager to discuss with you. The second issues was my sectary fix I did on the weekend worked but only temporally. What I was trying to do was block access so that users could not download my database. My database is SQL lite and is enchchaully a 'flat file' that acts as an advanced database. I had somehow made the sectury too high so no images could be accused by Drupal itself. This borke things. I couldn't figure out how to block just ".ht" files and I ended up blocking all files in the folder. As a quick workaround I moved the database to it's own folder.
The first issue I had is the one I want to talk about. After I updated the database and some modules, the site did not look write and had some errors. I uploaded it several times in-case it was corrupt. (which seems to happen often with FTPing large files). I then decided to put the site into 'maintenance mode' so users would see a message saying the site is being worked on rather then the mess of a site I was seeing. I uploaded the database but I did not see the maintenance message and at that point I realized the problem! I was uploading the wrong database, now this CAN happen with 'normal' database engines too if you grab the wrong dump file. So the leason here is make sure you have the correct database. I have a lot of backups sitting around on the server and my local machine where the database belongs. I have to go out soon but tonight I will clean those up and move them somewhere else.(some in the trash depending on their age).
No comments:
Post a Comment