[wp-trac] [WordPress Trac] #10690: Wordpress does not support non-ascii characters in URLs

WordPress Trac wp-trac at lists.automattic.com
Wed Mar 30 16:50:24 UTC 2011


#10690: Wordpress does not support  non-ascii characters in URLs
--------------------------+------------------------------
 Reporter:  paddya        |       Owner:  markjaquith
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Canonical     |     Version:  2.8.4
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |
--------------------------+------------------------------

Comment (by hakre):

 Replying to [comment:25 codestyling]:
 > Replying to [comment:24 hakre]:
 > > Replying to [comment:22 codestyling]:
 > > > Replying to [comment:20 hakre]:
 > > > > Replying to [comment:18 codestyling]:
 > > > >
 > > > > Can you specify `Ajax.Request`? Is that of some javascript
 library?
 > > >
 > > > Yes I can. This is belongs to ''Prototype.js'' library shipped with
 WordPress as one of the standard libraries. Documentation can be found
 here: http://api.prototypejs.org/ajax/Ajax/Request/
 > >
 >
 > > Thanks for providing the information. Can you provide a link to the
 prototype documentation of that `Ajax.Request` that is specifying the
 encoding of the URL parameter? The link you provided does not say in which
 encoding/format the URL has to be provided. This might just be a bug in
 prototype, not Wordpress.
 >
 > Here ist the default option description of Prototype.js Ajax classes:
 http://api.prototypejs.org/ajax/

 The link you provided says nothing about which encoding/format is
 expected/supported by that function for which browser. Until this
 information is not provided it can not be where exactly the cause of the
 problem is. I normally only fix problems if I know their cause, so that's
 why I was asking. Until provided I will step back from the discussion a
 bit.

 >
 > Even if this could be a bug at Prototype.js it affects function of
 WordPress plugins/themes using the onboard shipped Prototype.js
 functionality to solve the goals.

 That's the case for any library used: If the library has a bug, that bug
 might get transparently transported into the application making use of the
 library.

 If you see a problem in using Prototype.js Ajax across different browsers,
 please report the problem back to the prototype library project so they
 can fix it and every user of the library can benefit from the fix. Thanks.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10690#comment:26>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list