#116 closed enhancement (fixed)
The function which generate the 'nicename's is broken for unicode
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 1.2 |
Component: | Administration | Keywords: | |
Focuses: | Cc: |
Description
I'm about to run a non latin-1 site. While each post is linked with the post nicename, there is no nicename for non latin-1 posts, which gets null strings instead of nicename.
If the system do not like my nicename - it should ask for a manual nicename editing, not to make it null string!
Change History (8)
#5
@
19 years ago
We use the ID if sanitize_title returns an empty string. I was keeping the sanitize bugs open until we decided if we are going to expose category and author slugs in the admin UI. Are we, should we?
#6
@
19 years ago
- fixed_in_version set to 1.5
- Resolution changed from 10 to 20
- Status changed from assigned to closed
This ticket was mentioned in Slack in #forums by ipstenu. View the logs.
9 years ago
This ticket was mentioned in Slack in #forums by ipstenu. View the logs.
9 years ago
Note: See
TracTickets for help on using
tickets.
Yes, we should check for null strings and either prompt the user to provide a post slug that satisfies the character restrictions of RFC 2396 or autogenerate a post slug of the form "post #", for example, which the user can edit later.