Answers.Body: <p>When a new locale is added to an existing site, Craft re-saves the entries in the background. If you're unable to edit the entry in the new locale, it would indicate that the task has not completed. Check the craft_tasks table in your database to see if this is the case. <a href="http://buildwithcraft.com/help/stuck-tasks" rel="nofollow">More info on stuck tasks here.</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-04T20:03:28.170Z
Answers.Text: i looked at the craft_tasks table and none of the rows have a status column that is still running. is there anyway I can fix my locales?
Answers.UserDisplayName: testing guest
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-05T00:19:57.993Z
Answers.Text: Are there any rows in the table at all? Are you seeing any errors in your logs?
Answers.UserDisplayName: Patrick Nesbitt
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-04T04:05:11.103Z
Answers.LastActivityDate: 2015-09-04T04:05:11.103Z
Answers.UserDisplayName: Patrick Nesbitt
Body: <p>I've set up a new locale fr_ca according to the localization guide. 
  I've defined my site url's accordingly and set the files like so that english is on the top level and an fr_ca folder contains the index.php file. </p>
  
  <p>I've set the craft folder accordingly, and defined CRAFT_LOCALE. 
  I've also enabled the locale in all my sections.</p>
  
  <p>Now when i access a singles entry, and I click Canadian French on the right to switch locales, I get a Page Not Found error, the requested URL was not found on this server.</p>
  
  <p>I've also set my templates so that inside my templates folder, i have a folder fr_ca containing a new index.html file to be served. When I try to access the site from the front end, using www.example.com/fr_ca, I get an entry is not defined error (which makes sense). </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-03T23:31:08.610Z
Comments.Text: the main concern is that the light to the right of the locale (Canadian French) is still white. What could cause this problem?
Comments.UserDisplayName: testing guest
Tags: <localization><sections>
Title: Localization - Getting page not found from CP when trying to edit new locale
ThreadText: # Localization - Getting page not found from CP when trying to edit new locale
  
  (Asked by: username_0 on 2015-09-03)
  
  I've set up a new locale fr\_ca according to the localization guide.
  I've defined my site url's accordingly and set the files like so that english is on the top level and an fr\_ca folder contains the index.php file.
  
  I've set the craft folder accordingly, and defined CRAFT\_LOCALE.
  I've also enabled the locale in all my sections.
  
  Now when i access a singles entry, and I click Canadian French on the right to switch locales, I get a Page Not Found error, the requested URL was not found on this server.
  
  I've also set my templates so that inside my templates folder, i have a folder fr\_ca containing a new index.html file to be served. When I try to access the site from the front end, using www.example.com/fr\_ca, I get an entry is not defined error (which makes sense).
  
  **Tags:** localization, sections
  
  > **Comments:**
  > **username_0**: the main concern is that the light to the right of the locale (Canadian French) is still white. What could cause this problem?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-09-04. Score: 2
  
  When a new locale is added to an existing site, Craft re-saves the entries in the background. If you're unable to edit the entry in the new locale, it would indicate that the task has not completed. Check the craft\_tasks table in your database to see if this is the case. [More info on stuck tasks here.](http://buildwithcraft.com/help/stuck-tasks)
  
  > **Comments:**
  > **username_0**: i looked at the craft_tasks table and none of the rows have a status column that is still running. is there anyway I can fix my locales?  
  > **username_1**: Are there any rows in the table at all? Are you seeing any errors in your logs?  
  
  ---
  
  