Answers.Body: <p>Since files that begin with a dot are hidden by default in Unix-based systems like OS X, Craft ships with a “htaccess” file rather than “.htaccess”. If you are using Apache and want to use this file, you need to rename it to .htaccess when you upload it to your web server.</p>
  
  <p>Not sure why suddenly your site stopped working, but I can tell you that Craft auto-updates will only ever touch files within the craft/app/ folder, so if your .htaccess file was misnamed, it’s definitely not due to a Craft auto-update.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-08T17:44:53.100Z
Answers.LastActivityDate: 2014-10-08T17:44:53.100Z
Answers.UserDisplayName: Brandon Kelly
Body: <p><a href="http://denizen.tv/work/2011-kca-image-campaign" rel="nofollow">http://denizen.tv/work/2011-kca-image-campaign</a></p>
  
  <p><a href="http://denizen.tv" rel="nofollow">http://denizen.tv</a> has been up and running well since June, but it's suddenly throwing 404s. It looks like the same <code>/index.php/</code> problem I was recently having with my own Craft install. The coincidence makes me think it must be a bug with a recent release. </p>
  
  <p>Anyone else getting this error?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-06T00:30:40.607Z
Comments.Text: The .htaccess file hasn't been modified?  What happens if you set the ['omitScriptNameInUrls'](http://buildwithcraft.com/docs/config-settings#omitScriptNameInUrls) config setting to true?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-06T12:24:46.417Z
Comments.Text: Looks like the .htaccess file had been misnamed (on purpose). Adding back fixed the problem. But I hadn't changed anything since May/June, so could you guess why the problem happened only yesterday? thanks for the help
Comments.UserDisplayName: brian
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-06T15:36:36.173Z
Comments.Text: Can you add that as an official answer, then?  Maybe it was reading settings from cache the entire time and the cache was only recently cleared.
Comments.UserDisplayName: Brad Bell
Tags: <404-page><index>
Title: 6 month old site is suddenly throwing 404s
ThreadText: # 6 month old site is suddenly throwing 404s
  
  (Asked by: username_0 on 2014-10-05)
  
  <http://denizen.tv/work/2011-kca-image-campaign>
  
  <http://denizen.tv> has been up and running well since June, but it's suddenly throwing 404s. It looks like the same `/index.php/` problem I was recently having with my own Craft install. The coincidence makes me think it must be a bug with a recent release.
  
  Anyone else getting this error?
  
  **Tags:** 404-page, index
  
  > **Comments:**
  > **username_1**: The .htaccess file hasn't been modified?  What happens if you set the ['omitScriptNameInUrls'](http://buildwithcraft.com/docs/config-settings#omitScriptNameInUrls) config setting to true?  
  > **username_0**: Looks like the .htaccess file had been misnamed (on purpose). Adding back fixed the problem. But I hadn't changed anything since May/June, so could you guess why the problem happened only yesterday? thanks for the help  
  > **username_1**: Can you add that as an official answer, then?  Maybe it was reading settings from cache the entire time and the cache was only recently cleared.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2014-10-08. Score: 3
  
  Since files that begin with a dot are hidden by default in Unix-based systems like OS X, Craft ships with a “htaccess” file rather than “.htaccess”. If you are using Apache and want to use this file, you need to rename it to .htaccess when you upload it to your web server.
  
  Not sure why suddenly your site stopped working, but I can tell you that Craft auto-updates will only ever touch files within the craft/app/ folder, so if your .htaccess file was misnamed, it’s definitely not due to a Craft auto-update.
  
  
  ---
  
  