Answers.Body: <p>If the Update Asset Indexes fails on a MAMP install, double check to make sure ALL assets source paths are correct and exist on the file system.  </p>
  
  <p>I had defined a asset source to a folder which I had planned on using but had not yet created on the file system, and this caused the Update Asset Indexes to fail w/o any warning messages, save for a JS error in the console.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-11T06:23:05.620Z
Answers.LastActivityDate: 2014-08-11T06:23:05.620Z
Answers.UserDisplayName: Steve Adams
Body: <p>Having an issue with assets not reindexing from the Update Asset Indexes option.  If I add new folders to the file system they do not appear after I run the Update Asset Indexes, if I upload them manually in the backend then they do appear as normal.  </p>
  
  <p>How would I diagnose this?  Running Apache as my logged in user so it's does not seem to be a group / permissions related issue. </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-11T06:03:27.880Z
Comments.Text: Do you get any JS errors in your browser's console when you run Update Asset Indexes?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-11T06:05:38.310Z
Comments.Text: Yup:  POST http://smt.craft.dev/index.php/admin/actions/tools/performAction 500 (Internal Server Error) jquery-2.1.0.min.js?d=1406143654:4
  l.cors.a.crossDomain.send jquery-2.1.0.min.js ...
Comments.UserDisplayName: Steve Adams
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-11T06:06:07.957Z
Comments.Text: On Craft Client 2.1.2566
Comments.UserDisplayName: Steve Adams
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-11T06:06:43.613Z
Comments.Text: Check your craft/storage/runtime/logs files to see what the underlying error is for the 500 Internal Server Error.
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-11T06:18:31.740Z
Comments.Text: Cool... probably worth adding that as the official answer in case someone else runs into it.
Comments.UserDisplayName: Brad Bell
Tags: <assets><reindex><mamp>
Title: What would prevent my assets from reindexing on a local MAMP install
ThreadText: # What would prevent my assets from reindexing on a local MAMP install
  
  (Asked by: username_0 on 2014-08-11)
  
  Having an issue with assets not reindexing from the Update Asset Indexes option. If I add new folders to the file system they do not appear after I run the Update Asset Indexes, if I upload them manually in the backend then they do appear as normal.
  
  How would I diagnose this? Running Apache as my logged in user so it's does not seem to be a group / permissions related issue.
  
  **Tags:** assets, reindex, mamp
  
  > **Comments:**
  > **username_1**: Do you get any JS errors in your browser's console when you run Update Asset Indexes?  
  > **username_0**: Yup:  POST http://smt.craft.dev/index.php/admin/actions/tools/performAction 500 (Internal Server Error) jquery-2.1.0.min.js?d=1406143654:4 l.cors.a.crossDomain.send jquery-2.1.0.min.js ...  
  > **username_0**: On Craft Client 2.1.2566  
  > **username_1**: Check your craft/storage/runtime/logs files to see what the underlying error is for the 500 Internal Server Error.  
  > **username_1**: Cool... probably worth adding that as the official answer in case someone else runs into it.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2014-08-11. Score: 1
  
  If the Update Asset Indexes fails on a MAMP install, double check to make sure ALL assets source paths are correct and exist on the file system.
  
  I had defined a asset source to a folder which I had planned on using but had not yet created on the file system, and this caused the Update Asset Indexes to fail w/o any warning messages, save for a JS error in the console.
  
  
  ---
  
  