WordPress.org
Get WordPress

Make WordPress Core

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#36122 closed defect (bug) (fixed)

Emoji not accepted for blog title and subtitle

Reported by: marcomarsala's profile marco.marsala Owned by: pento's profile pento
Milestone: 4.6 Priority: normal
Severity: normal Version: 4.2
Component: Emoji Keywords:
Focuses: administration Cc:

Description

Emoji inserted in blog title or subtitle will be stripped out.

Attachments (1)

2016-03-09 (1).png​ (240.2 KB) - added by marco.marsala 9 years ago.

Download all attachments as: .zip

Change History (8)

#1 @dd32
9 years ago

This is working for me with utf8mb4.

@marco.marsala Can you let us know what database charset you're using is? You'd need to look at the wp_options table directly. It'll probably be utf8 or utf8mb4.

#2 @marco.marsala
9 years ago

Seems I'm already using utf-8. Please find the screenshot attached.

@marco.marsala
9 years ago

#3 follow-up: @pento
9 years ago

  • Version changed from 4.4.2 to 4.2

Is there anywhere we use blogname or blogdescription that wouldn't like it if emoji were HTML encoded? If not, we could tweak sanitize_option() to do that.

#4 in reply to: ↑ 3 @SergeyBiryukov
9 years ago

Replying to pento:

Is there anywhere we use blogname or blogdescription that wouldn't like it if emoji were HTML encoded?

#25485 and #27942 are related, but the former is invalid and the latter appears to be resolved.

#5 @pento
9 years ago

  • Milestone changed from Awaiting Review to 4.6
  • Owner set to pento
  • Status changed from new to assigned

#6 @pento
9 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 37469:

Emoji: Allow emoji in blogname and blogdescription on utf8 installs.

When the options table is set to utf8 instead of utf8mb4, emoji will be stripped from the blog name and description when they're saved. Instead of stripping them, they can be encode as HTML entities.

Fixes #36122.

#7 @pento
9 years ago

In 37470:

Tests: Fix an incorrect @ticket header included in [37469].

See #36122.

Note: See TracTickets for help on using tickets.