You can now continue with the WordPress Network setup using the Codex instructions found here. You should now have a WordPress 3 install working nicely available at with the WordPress admin available at Don’t forget that just like our test.html file, WordPress needs to be installed in the folder that you specified when you configured MAMP. You’ll find full instructions for setting up WordPress locally on MAMP here. You can create the WordPress database using MAMP’s built-in version of phpMyAdmin. You can now download and install WordPress as normal using .uk as the WordPress Address (URL) and Site Address (URL) fields within WP’s ‘Settings’ menu. If everything is ok, the file should render correctly and the host name in your browser address bar shouldn’t append a port number and certainly shouldn’t revert to localhost Install WordPress ![]() Save the file as something like test.html and then visit in your browser. To check that everything is working as expected, create a really basic HTML file and save it in the folder that you specified as MAMP’s Apache root. You can now restart MAMP and your browser. If you’re happy to do so, you might also do well to clear the browser cache as well. Probably best to restart your browser now as well. Ensure that the changes you made to /etc/hosts have been saved and exit your Terminal session. If the MAMP servers are still running, stop them and then quit the application. If you’re unsure of how to use vi, take a look at this very helpful guide. This basically means that from now on when you type .uk in to your browser it will actually point to the IP address of your local computer – the localhost. This will cause MAMP to request your OS X admin password whenever you start your MAMP server but if you’re savvy enough to be setting up a local web server, you can probably be trusted with an OS X administrator account!Īdd an entry to your hosts file using OS X's Terminal Now set MAMP’s Apache and MySQL ports to web server defaults ( respectively). Users/mymacusername/Sites/mydomain/wordpress This is likely to be something like this: Configure MAMPįirstly, set MAMP’s Apache document root to the proposed root of your local WP install. No need for the Pro version, just the regular version of MAMP is all you’ll need. Otherwise OS X’s built in Apache server will get in the way of MAMP’s. Head in to System Prefs and make sure that Web Sharing is switched off. ![]() ![]() Switch off OS X’s built in Apache web server. This wasn’t an issue for me as I need just this type of configuration. It’s also worth noting that, as far as my research could see, it is impossible to setup WordPress network in its sub-domain configuration on MAMP so the only option is to set it up in its sub-directory configuration. For the record, I’m using OS X 10.6.8 and MAMP version which includes PHP version and MySQL version. Here’s how I got round the problem and got my WordPress Network working nicely on my local Mac. However, with a few simple config changes to MAMP and and some very minor tinkering on the command line, you can overcome this problem. By default, MAMP uses port 88 for Apache and MySQL respectively, resulting in the host name which WordPress Network won’t accept (the setup discussed here fails when using a host name that has a port number appended to it). The problem is a result of WordPress Network’s inability to handle a host name with a specified port number. Essentially WordPress plays nicely with MAMP so long as you don’t want to switch on the Network feature that has been rolled in to the WordPress core since version 3.0 (it was previously available as WordPress MU (Multi User). I happened upon an interesting problem today whilst setting up WordPress 3.3.2 on MAMP.
0 Comments
Leave a Reply. |