<p>Has this old issue recurred in a very recent update:
<a href="https://craftcms.stackexchange.com/questions/5069/uri-is-not-a-valid-uri">URI is not a valid URI</a></p>

<p>Just a few weeks ago I imported Korean content using FeedMe just fine, I have a setting 'limitAutoSlugsToAscii' => false, also. All Korean content and URLs were correctly showing in Korean. </p>

<p>I have updated Craft several versions since. </p>

<p>I need to do a re-import, but Korean is now all in English, and I get errors in FeedMe:</p>

<pre><code>KO Categories Feed: Node #30 - {"uri":["URI is not a valid URI"]} - Process.php: 460. 
</code></pre>

<p>If I manually edit the entry and set the URL to say 무게_감지_센서, the Admin CO also shows the error:</p>

<pre><code>URI is not a valid URI
</code></pre>

<p>Thanks</p>

CC BY-SA 4.0
2019-07-25T18:59:02.273Z
This was a Craft bug that has been fixed in 3.2.7: https://github.com/craftcms/cms/blob/develop/CHANGELOG-v3.md#327---2019-07-25
Brad Bell
CC BY-SA 4.0
2019-07-25T19:12:22.563Z
I confirm this fixes it for me, so thats excellent thanks for a speedy bug fix!
Laurence Cope
<craft3><localization>
URI is not a valid URI error after recent update
# URI is not a valid URI error after recent update

(Asked by: username_0 on 2019-07-24)

Has this old issue recurred in a very recent update:
URI is not a valid URI
Just a few weeks ago I imported Korean content using FeedMe just fine, I have a setting 'limitAutoSlugsToAscii' => false, also. All Korean content and URLs were correctly showing in Korean. 
I have updated Craft several versions since. 
I need to do a re-import, but Korean is now all in English, and I get errors in FeedMe:
KO Categories Feed: Node #30 - {"uri":["URI is not a valid URI"]} - Process.php: 460. 

If I manually edit the entry and set the URL to say 무게_감지_센서, the Admin CO also shows the error:
URI is not a valid URI

Thanks

**Tags:** craft3, localization
> **Comments:**
> **username_1**: This was a Craft bug that has been fixed in 3.2.7: https://github.com/craftcms/cms/blob/develop/CHANGELOG-v3.md#327---2019-07-25  
> **username_0**: I confirm this fixes it for me, so thats excellent thanks for a speedy bug fix!  

---

## 0 answers

