Jump to content

PW 3.0.12: Support for extended (UTF8) page names/URLs


ryan
 Share

Recommended Posts

On 5/8/2017 at 11:28 AM, Gideon So said:

Hi,

I don't think this is a good way to do it either. Seems other CMSs get a more simple way.

Gideon

I'm using processwire and CI too to build site for client.

In CI way, it has permitted_char config for allowed char in url too, but CI could accept a utf-8 code range in the config

something like

$config['permitted_uri_chars'] = 'a-z 0-9~%.:_\-\x{4e00}-\x{9fa5}';

I found this information from a chinese post to solve utf-8 url in CI
http://codeigniter.org.cn/forums/thread-20990-1-1.html

 

I suggest @ryan should reference the CI way for processwire to handle UTF-8 url

Link to comment
Share on other sites

 

 

2 hours ago, adrianmak said:

I'm using processwire and CI too to build site for client.

In CI way, it has permitted_char config for allowed char in url too, but CI could accept a utf-8 code range in the config

something like


$config['permitted_uri_chars'] = 'a-z 0-9~%.:_\-\x{4e00}-\x{9fa5}';

I found this information from a chinese post to solve utf-8 url in CI
http://codeigniter.org.cn/forums/thread-20990-1-1.html

 

I suggest @ryan should reference the CI way for processwire to handle UTF-8 url

I would suggest that you open a ticket in Github to properly track this change/enhancement:

https://github.com/processwire/processwire-issues/issues

or

https://github.com/processwire/processwire-requests/issues

If you have already done this, please post a link in this post for reference purposes.  Thanks.

Link to comment
Share on other sites

  • 11 months later...
  • 6 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...