Site creation fails when using Japanese characters for site name
See original GitHub issueTrying to create a site with the following:
sites = "遊び場"
new_site = TSC.SiteItem(name=site, content_url=site.replace(" ", ""), admin_mode=TSC.SiteItem.AdminMode.ContentAndUsers)
server.sites.create(new_site)
This errors with:
409002: Resource Conflict
A site already exists with the content URL '遊び場'
The site doesn’t exist on my server.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
File Explorer Not Displaying Japanese Characters Properly (Win
4) Press "Change System Locale" and select "Japanese (Japan)" from the drop-down menu. Important thing here: make sure the box that says "Beta: ......
Read more >How to Remove Japanese Keyword Hack From Your Website
Japanese keyword hack is a type of SEO spam in which auto generated Japanese text starts to appear on your site. Know how...
Read more >How to fix search engine results that are appearing as ...
How to fix search engine results that are appearing as Japanese characters? I am having big issues with our website. When we search...
Read more >Error deploying ADC rule project that includes Japanese ...
Deployment Errors occur when deploying ADC rule project that includes Japanese characters in Data source Name from Studio. Steps to Reproduce.
Read more >html - japanese character is not supported in localhost
On your local copy of .html , there are no such headers, so the browser checks the <meta/> tags (which are missing), and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe have it be a property that takes an argument and call it something like “allowed_characters”? And then define “allowed_content_url_characters” somewhere which includes a string (or list/tuple) of all of the allowed characters in a content url?
Or maybe a regex validation method?
Resolved in #64