<p>I just introduced a new (2nd) locale to my site. It now seems I can easily set up translated versions for "single" and "channel" pages that I set up new. </p>

<p>The <em>old entries</em>, which existed <strong>prior to introducing the new locale</strong>, are not translatable however:</p>

<p>The little (green) dot after the language switch in these entries’ individual editor is only a grey circle instead of a green one like with the newly setup pages. If I click the new language I get a native "Page not found" error.</p>

<p>I have set the specific legacy pages to be fully translatable though in the Sections settings, set them to be available in both locales but I get the feeling that <strong>Craft is not able to handle "legacy" singles &amp; entries that were introduced during a one-locale setup of the page, is that correct?</strong> </p>

<p>Is there any way of working around the hassle of having to delete all the pre-multi-locale pages and re-setting them up to have them available in both locales (which would solve my problem but is a pain with so many pages/entries)?</p>

CC BY-SA 3.0
2018-04-14T23:22:35.027Z
I'm assuming this is for Craft 2?  Did you enable the locale for the sections you are having problems with? https://docs.craftcms.com/v2/localization-guide.html#step-2-update-your-sections  Probably worth verifying the rest of the steps in that guide as well.
Brad Bell
CC BY-SA 3.0
2018-04-16T12:53:46.957Z
Everything was setup correctly and now it seems to work fine. I suppose the task for translating the pages was stuck or something, so I didn’t see the translations until some voodoo happenend in the background an hour later or so, flushing whatever pipeline there might have been.
Tobias S.
CC BY-SA 3.0
2018-04-16T17:21:41.127Z
Fair enough... would you mind adding that as an official answer in case it might help someone in the future?
Brad Bell
CC BY-SA 3.0
2018-04-17T08:45:23.883Z
Will do so, currently still running into 404s with the new locale, so I want to make sure first there is no overlap between these problems.
Tobias S.
<entries><localization><settings>
Craft 2: New locale introduction not affecting old entries
# Craft 2: New locale introduction not affecting old entries

(Asked by: username_0 on 2018-04-13)

I just introduced a new (2nd) locale to my site. It now seems I can easily set up translated versions for "single" and "channel" pages that I set up new.

The *old entries*, which existed **prior to introducing the new locale**, are not translatable however:

The little (green) dot after the language switch in these entries’ individual editor is only a grey circle instead of a green one like with the newly setup pages. If I click the new language I get a native "Page not found" error.

I have set the specific legacy pages to be fully translatable though in the Sections settings, set them to be available in both locales but I get the feeling that **Craft is not able to handle "legacy" singles & entries that were introduced during a one-locale setup of the page, is that correct?**

Is there any way of working around the hassle of having to delete all the pre-multi-locale pages and re-setting them up to have them available in both locales (which would solve my problem but is a pain with so many pages/entries)?

**Tags:** entries, localization, settings
> **Comments:**
> **username_1**: I'm assuming this is for Craft 2?  Did you enable the locale for the sections you are having problems with? https://docs.craftcms.com/v2/localization-guide.html#step-2-update-your-sections  Probably worth verifying the rest of the steps in that guide as well.  
> **username_0**: Everything was setup correctly and now it seems to work fine. I suppose the task for translating the pages was stuck or something, so I didn’t see the translations until some voodoo happenend in the background an hour later or so, flushing whatever pipeline there might have been.  
> **username_1**: Fair enough... would you mind adding that as an official answer in case it might help someone in the future?  
> **username_0**: Will do so, currently still running into 404s with the new locale, so I want to make sure first there is no overlap between these problems.  

---

## 0 answers

