Changes in MAMP Pro
This first step involves making changes to MAMP Pro. The process I typically follow goes a little something like this:- Open MAMP Pro and select the Host your currently using.
- Click the Permissions button
- Set Owner to your Mac username, for me it’s kevinleary
- Set Group to www
- Under permissions, check off Change for both Directory and File, and check off the boxes to the left for setting a
CHMOD 777
.
CHMOD
means, refer to the screenshot for a visual reference. You should probably learn this at some point if your doing professional development, it plays an important role in web security.
Adjustments in wp-config.php
The second step in the process involves adding the following line to yourwp-config.php
file:
[php]define('FS_METHOD', 'direct');[/php]
That’s it, you should now be able to upgrade WordPress core, install new plugins, and update plugins on your MAMP Pro localhost server.Revisions
- May 14, 2012 @ 06:50:42 [Current Revision] by PeterLugg
- May 14, 2012 @ 06:48:32 by PeterLugg
Revision Differences
May 14, 2012 @ 06:48:32 | Current Revision | ||
---|---|---|---|
Content | |||
Added: I do all of my WordPress development locally, and typically deploy that to a staging server, or sometimes a live server, using Beanstalk’s SVN deployment feature. | |||
Added: I use a Mac for development, and MAMP Pro to run a localhost environment with multiple hosts (local.website1, localhost.website2, etc.). | |||
Added: Occasionally I need to upgrade or install WordPress plugins locally in order to test them before pushing things to the web. I seem to continuously run into issues with MAMP Pro and the WordPress upgrader. I’ve found a solution, which I’ve documented here for myself and anyone else having similar issues. | |||
Added: <h2>Changes in MAMP Pro</h2> | |||
Added: This first step involves making changes to MAMP Pro. The process I typically follow goes a little something like this: | |||
Deleted: | Added: <ul> | ||
Added: <li>Open MAMP Pro and select the Host your currently using.</li> | |||
Added: <li>Click the <strong> Permissions</ strong> button</li> | |||
Added: <li>Set <strong> Owner</strong> to your Mac username, for me it’s <em>kevinleary</em></li> | |||
Added: <li>Set <strong> Group</strong> to <em>www</em></li> | |||
Added: <li>Under permissions, check off <em>Change</em> for both <strong> Directory</strong> and < strong>File</strong>, and check off the boxes to the left for setting a <code>CHMOD 777</code>.</li> | |||
Added: </ul> | |||
Added: If you’re not sure what <code>CHMOD< /code> means, refer to the screenshot for a visual reference. You should probably learn this at some point if your doing professional development, it plays an important role in web security. | |||
Added: <h2>Adjustments in <code>wp- config.php</code></h2> | |||
Added: The second step in the process involves adding the following line to your<code>wp- config.php</code> file: | |||
Added: [php]define('FS_METHOD', 'direct');[/php] | |||
Added: That’s it, you should now be able to upgrade WordPress core, install new plugins, and update plugins on your MAMP Pro localhost server. |
Note: Spaces may be added to comparison text to allow better line wrapping.
No comments yet.