Ever since I switched to a brand new retina MacBook Pro, I'm not able to setup a new Drupal installation anymore...

I use MAMP and I configure my vhosts.conf so I can work on virtual hosts (like dev.newproject.com). But whenever I try to install a new Drupal installation, it looks like the setup is confused...

Normally, you have

 1. Choose profile
 2. Choose language
 3. Verify requirements
 4. Set up database
 5. Install profile
 6. Configure site
 7. Finished

But for some reason, after step 5, het installation goes back to step 1 or 3 or whatever step... When I look in my database, it looks like Drupal has been installed and also a settings.php file was created, but I'm in an infinite set-up loop...

Has anyone ever experienced such weird behaviour? And how can I fix this?

  • Did you disable JavaScript in your browser? Perhaps you could try to clear all your browser's cache and cookies for this domain. Does it happen on another browser? Jan 6, 2014 at 13:24
  • It happens in all browsers with empty caches. And JavaScript is enabled...
    – Michiel
    Jan 6, 2014 at 14:16

3 Answers 3


It could be write permissions of the files - try chmod -R a+rw . command in Terminal in the root of your drupal folder. It could be a time out meaning that the database is not been written correctly (don't have a remedy for that, except for not using a native setup, but rather a Virtual Machine, VM-based setup...)

You might want to consider a VM-based setup (which would more closely resemble your production environment), see a guide I wrote to using Vagrant to automate generation of a setup here: https://stackoverflow.com/a/15067918/227926

  • The Terminal command didn't work out... Could you summarise in 1 sentence the advantage of using Vagrant over MAMP? :)
    – Michiel
    Jan 7, 2014 at 12:01
  • 1
    OK here goes - my own words, in one sentence as requested "Vagrant provides a consistent, automated setup and that isolates the Drupal site from your machine's environment, allowing you to share your setup with others than can help/work with you." Jan 7, 2014 at 12:35
  • 1
    P.S. Don't get put off by the length of instructions in the links I sent you. A particular Vagrant-based setup that works well for me is: github.com/mikebell/drupaldev-apache Like you, I used to use MAMP but found myself starting to do quite a bit of manual setup and hacking for some things, stuff that wasn't easily containable and repeatable. Jan 7, 2014 at 12:38
  • 1
    A further benefit of a Vagrant-based setup is that it is fairly isolated from any OS upgrade that might alter environmental settings on your machine. Vagrant is also multi platform, in that you can run your site stack on Linux or Windows machines too. Jan 7, 2014 at 12:39

It appears more people suffer from this issue. It has nothing to do with the brand new retina structure.

This question on SE describes the same issue. Solution is waiting a few seconds WITOUT filling in the database credentials again and refresh the page. You'll see, the installation profile completes.


Check your MAMP error logs. It is very probably, than in a default MAMP installation (with no modifications), either your MySQL or PHP ran out of memory while in the midst of installing the default profile.

Also, did you take a look at this answer? It has some excellent links.

  • I assigned 1024MB memory to PHP and MySQL, which met the criteria for years... So I doubt that's the issue. I only have 1 error in my logs and it has something to do with the .DS_Store file. Any change it has something to do with my issue?
    – Michiel
    Jan 6, 2014 at 14:17
  • Did you look at drupal.stackexchange.com/questions/89651/… and drupal.stackexchange.com/questions/21178/…? Memory is not the only thing that can give issues. Updated answer. Jan 6, 2014 at 14:56
  • Non of the suggestions there are helpful I'm afraid... My max allowed packet is set to 1024M (more then enough I might think) and I'm not suffering any WSOD's.
    – Michiel
    Jan 7, 2014 at 11:59

Your Answer

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

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