I turn the site in maintenance mode for update Drupal Core from 7.30 to 7.32. I follow the step on Drupal docmentation to delete all folders and files, beside "site" folder(on step 5). However, I got the error message and warning about missing files. I dont think that how maintenace mode should be. What am i missing?

1. the site does show in maintenance mode before I delete all the folders and files(beside site folder)
2. Site back to normal after copying v7.32 folders and files(beside site folder)

  • What exactly you did, step by step? And what you expected? If you delete files, and before you will upload new ones, you will have missing files. That's pretty obvious, isn't it?
    – Mołot
    Commented Oct 27, 2014 at 15:32
  • @Mołot I followed all the steps in Update Drupal Core Documentation(drupal.org/node/1494290). The only issue I have is step 5. I got an error message instead of maintenance mode until I copy all the new files back. I thought the whole process would be in maintenance mode.
    – CocoSkin
    Commented Oct 27, 2014 at 15:39
  • "I got an error message instead of maintenance mode until I copy all the new files back." - that's expected - you deleted Drupal, and there was not enough of it left to handle even maintenance mode. That's why in pro environments things like that are made differently, with second (virtual) server and so on.
    – Mołot
    Commented Oct 27, 2014 at 15:42
  • 1
    Yes. To prevent changes from happening in the meantime. Imagine someone adds new content, or fills multistep form. What happen if you delete PHP file right before it is needed? You can end up with inconsistent data in database. You don't want that. Maintenance mode is the best simple way to prevent it. Even in two-machine upgrade scenario I turn on maintenance mode on machine that's going to get upgrades - and this machine is not visible to anyone but me, my boss and our admins.
    – Mołot
    Commented Oct 27, 2014 at 15:48
  • 1
    What I would recommend though, is that you look at git. If you do the update through git, the update will take milliseconds, and no one will ever even notice the site was missing.
    – Letharion
    Commented Oct 27, 2014 at 18:54

1 Answer 1


Rather than the two step deleting the folders and then uploading the new ones, I would recommend just copying over the old ones with new ones. You'll probably have to tell your FTP program to overwrite but when I upgrade in this fashion, I select all the files and directories except for sites folder and push them to the server.

When possible, I use the Drush tool via a terminal window as it is a much quicker and easier solution.

  • not sure about this. There must be a reason why the Update Drupal Core Documentation says to delete all these files. It’s possible the new and old Drupal has different amount of files?
    – CocoSkin
    Commented Oct 27, 2014 at 16:07
  • Yes, I'm not sure about that either except perhaps for thoroughness. Most FTP client programs I've used will prompt you to overwrite a file or directory if it already exists so maybe the folks at Drupal.org were concerned about confusing the issue. If you delete a folder and then upload the new one, there is less chance of confusion in that regard. Commented Oct 27, 2014 at 18:01
  • There's (at least two risks). One is that if the update gets "half done", you have no way to tell, and might not even know. Instead you end up with odd and hard to reproduce bugs because you run some sort of 7.31 and half chimera. The other is that the update might require the removal of some file, so again, you end up with parts of the previous version, that may cause problems in the new version. In most cases it will all work just fine though, but the official guide has to be careful.
    – Letharion
    Commented Oct 27, 2014 at 18:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.