Well, this was easy in the older version of MAMP that I had. You would just drop them in place, and they worked. I was having a problem with something, so I thought maybe there was an updated version of MAMP that would solve the problem. Sure enough, there was. So I installed it and went along my way. Then, I went back to the local version of my site, and it was completely busted.
I finally tracked it down to .htaccess files being ignored. So I opened up my http.conf file and went down to line 378, and sure enough this is what I saw:
<Directory />
Options Indexes FollowSymLinks
AllowOverride None
</Directory>In the older version of MAMP that I had, the default for this value was All. In order to get .htaccess files working in the new version, I just had to change None to All, restart the server, and everything worked normally. Just thought I would share in case anyone else runs into this problem.
Categories
Recent Articles
May 2012
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 |
2 Comments
Christopher Beckwith
02.21.2011Nice catch.
I upgraded to the lastest version last week and did not experience this problem. I believe it’s because I use MAMP Pro.
On MAMP Pro, when you select the “Hosts” tab, there are radio buttons that let you select “AllowOverride, Order, Allow” and such that I assume overrite the http.conf.
I wonder why they would change the setting unexpectedly or without warning for the standard MAMP app?
Trevor
02.21.2011@Christopher-
Yeah, I know MAMP Pro gives you a GUI to manage the http.conf file; I’m just too cheap to spring for it. They may have documented the change somewhere, but I sure couldn’t find anything.
Too late, comments are closed!
Don’t worry, you can email me or contact me on Twitter.