xinaes

So it turns out that the problem was that my ‘DocumentRoot’ setting had changed, along with ports as I’d noticed. I still don’t know at what point this happened – my recollection is probably not perfect, but as I said in my initial post, I believed everything to have been working with the version of MAMP I had installed.

So it’s now working, and if I were to move away from MAMP I would at least be more likely to know under what conditions my configuration should change.

I don’t really understand why it stopped working in quite the way it did. Each of my VirtualHost entries has an appropriate DocumentRoot (“/Users/peter/Documents/code/www/wp/sitename” for the WP versions), and as mentioned, the main index as well as wp-admin stuff was working. I don’t understand exactly how Apache rules for AllowOverride etc apply in this kind of situation, but suppose that must be where the problem was (as I thought, no sign of problem in the .htaccess files).

Perhaps if I were trying to do something interesting or unusual that I felt warranted me feeling motivated to learn about Apache configuration then I wouldn’t find it quite so mind-numbingly tedious, but as it stands it only ever presents itself to me as ‘something that used to work is now randomly broken’ (normally on some fairly dull site that isn’t particularly related to real work)…

Anyway, perhaps some of this information can be of use to future Googlers.

• This reply was modified 7 years, 6 months ago by xinaes.

(Also you’ll notice that support is something you only get with MAMP Pro or MAMP Cloud (ie paid license)… I’m not against supporting developers work, but don’t have any desire for the extra features, and this isn’t really motivating me to pay them money – might switch to a Linux VM or something instead).