• I noticed that ez_encode_unicode aggressively encodes all non-ASCII characters into HTML entities. This causes two issues:

    1. It breaks CSS content properties containing Cyrillic text (e.g., content: 'Text' renders as literal code &#x...).
    2. It messes up data for external tools/scrapers that expect standard UTF-8.

    Since modern WordPress and browsers handle UTF-8 natively, this encoding seems redundant. I resolved it efficiently by overriding ez_encode_unicode to return the content as-is. Please consider removing this forced encoding in future updates.

    Thanks!

You must be logged in to reply to this topic.