We have moved to Github. Please open tickets there.

Opened 5 years ago

Closed 3 years ago

#542 closed Defect (duplicate)

elgg_get_friendly_title() not multibyte safe

Reported by: lungkao Owned by:
Priority: low Milestone: Elgg 1.8.0
Component: Core Version: 1.0
Severity: annoying Keywords: i18n
Cc: brettp Difficulty:

Description (last modified by brettp)

Multibyte characters are replaced with nothing.

Attachments (1)

11-11-2551 0-55-37.png (28.8 KB) - added by lungkao 5 years ago.
elgg in thai languages on title can't show on url

Download all attachments as: .zip

Change History (8)

Changed 5 years ago by lungkao

elgg in thai languages on title can't show on url

comment:1 Changed 4 years ago by marcus

  • Summary changed from elgg in thai languages on title can't show on url to Internationalisation of friendly url [Was: elgg in thai languages on title can't show on url]

comment:2 Changed 4 years ago by vurban

But how to change URL on DATE-style?

For ex. may i do like this: site.com/pg/blog/user/D_A_T_E?

or smth else?

comment:3 Changed 4 years ago by ben

Could you provide more information about how this transformation could be done?

My suggestion would be to add a plugin hook to the getURL() function and transform from there.

comment:4 Changed 3 years ago by brettp

  • Milestone changed from Elgg 1.1 to Elgg 1.8

comment:5 Changed 3 years ago by brettp

  • Description modified (diff)
  • Keywords i18n added
  • Priority changed from high to low
  • Severity changed from major to annoying
  • Summary changed from Internationalisation of friendly url [Was: elgg in thai languages on title can't show on url] to elgg_get_friendly_title() not multibyte safe
  • Type changed from unconfirmed defect to confirmed defect

comment:6 Changed 3 years ago by brettp

This function is primarily used in URLs. Since the URLs are still functional even though an empty string is returned, I'm dropping the priority.

comment:7 Changed 3 years ago by brettp

  • Resolution set to duplicate
  • Status changed from new to closed

Closing in favor of #2276 (more discussion, proposed solutions).

Note: See TracTickets for help on using tickets.