Description
By default, WordPress converts single and double quotation marks into their curly alternatives. This plugin prevents that from happening, so you can enjoy your quotation marks in their non-curly glory. If your content happens to already have curly quotation marks in it, then this plugin can optionally also convert them to their non-curly alternatives.
Note: Despite the unfortunately misleading name, this plugin is NOT the antithesis of WordPress’s wptexturize()
function. This ONLY prevents WordPress from making HTML entity code substitutions of single and double quotation marks with their curly alternatives and does NOT prevent wptexturize()
from making any other character and string substitutions. See the FAQ for details on the filters processed by the plugin.
Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage
Developer Documentation
Developer documentation can be found in DEVELOPER-DOCS.md. That documentation covers the numerous hooks provided by the plugin. Those hooks are listed below to provide an overview of what’s available.
c2c_wpuntexturize
: An alternative approach to safely invokec2c_wpuntexturize()
in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site. This only applies if you use the function directly, which is not typical usage for most users.wpuntexturize_filters
: customize what filters to hook to be filtered with wpuntexturize. See the Description section for a complete list of all filters that are filtered by default.c2c_wpuntexturize_replacements
: Customize the character replacements handled by the plugin.c2c_wpuntexturize_convert_curly_quotes
: Enable conversion of preexisting curly quotes into their non-curly alternatives.
Screenshots
Installation
- Install via the built-in WordPress plugin installer. Or download and unzip
wpuntexturize.zip
inside the plugins directory for your site (typicallywp-content/plugins/
) - Activate the plugin through the ‘Plugins’ admin menu in WordPress
- Optional: If you want to also convert existing curly quotation marks within posts to their non-curly alternatives, then on the Settings -> Reading admin page check the checkbox labeled “Convert existing curly quotes in posts to their non-curly alternatives”. (Reminder that the plugin will always prevent WordPress from converting non-curly quotation marks to the curly alternatives.)
FAQ
-
Why are certain characters in my posts still being replaced by their HTML entity encoded version?
-
This ONLY prevents WordPress from making HTML entity code substitutions of single and double quotation marks with their curly alternatives and does NOT prevent WordPress from making any other character and string substitutions.
-
Why do I still see curly quotation marks in my posts?
-
Most likely these curly quotes are actually present in your originally post content and are being directly shown to visitors. WordPress isn’t converting these to curly quotes since they are already that way. This could happen if you copy-and-pasted text from another source.
If you don’t want any curly quotes to appear in your posts at all, then on the Settings -> Reading admin page check the checkbox labeled “Prevent all curly quotes?”. (Or if you’re a developer, look into use of the
c2c_wpuntexturize_convert_curly_quotes
filter.) -
What text does this plugin modify/filter?
-
This plugin potentially modifies the post content, excerpt, title, comment text, widget text, and more.
More specifically, it performs a wpuntexturize on every filter that WordPress applies the wptexturize to by default. This list comprises:
comment_author, term_name, link_name, link_description, link_notes, bloginfo, wp_title, widget_title, single_post_title, single_cat_title, single_tag_title, single_month_title, nav_menu_attr_title, nav_menu_description, term_description, get_the_post_type_description, the_post_thumbnail_caption, the_title, the_content, the_excerpt, the_excerpt_embed, comment_text, list_cats, widget_text, widget_text_content
This complete list can be filtered via wpuntexturize’s own filter,
wpuntexturize_filters
. -
Does this plugin include unit tests?
-
Yes. The tests are not packaged in the release .zip file or included in plugins.svn.wordpress.org, but can be found in the plugin’s GitHub repository.
Reviews
Contributors & Developers
“wpuntexturize” is open source software. The following people have contributed to this plugin.
Contributors“wpuntexturize” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “wpuntexturize” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
2.3 (2025-04-07)
Highlights:
This recommended release drops support for versions of WP older than 5.5, prevents translations from including unintended markup, verifies compatibility through WP 6.8+ and PHP 8.3+, and a few more minor changes.
Details:
- Change: Remove code supporting versions of WP older than 5.5
- Change: Escape output of all translated strings
- Change: Discontinue explicit and unnecessary loading of textdomain
- Change: Remove
is_wp_55_or_later()
- Change: Sanitize the plugin’s setting value
- New: Add
sanitize_boolean()
- Change: Note compatibility through WP 6.8+
- Change: Drop compatiblity with versions of WP older than 5.5
- Change: Confirm compatiblity through PHP 8.3+
- Change: Shorten plugin description in plugin header and readme.txt
- Fix: Fix typo in ‘Author URI’ plugin header value
- Change: Update copyright date (2025)
- Unit tests:
- Change: Explicitly define return type for overridden method
- Change: Delete tests for removed back-compatibility
2.2.2 (2024-08-08)
- Change: Note compatibility through WP 6.6+
- Change: Update copyright date (2024)
- Change: Reduce number of ‘Tags’ in readme.txt
- Change: Remove development and testing related files from release packaging
- Unit tests:
- Hardening: Prevent direct web access to
bootstrap.php
- Change: In bootstrap, store path to plugin file constant
- Change: In bootstrap, add backcompat for PHPUnit pre-v6.0
- Hardening: Prevent direct web access to
2.2.1 (2023-04-29)
- Change: Note compatibility through WP 6.3+
- Change: Update copyright date (2023)
- Change: Add link to DEVELOPER-DOCS.md in README.md
- New: Add
.gitignore
file - Unit tests:
- Fix: Allow tests to run against current versions of WordPress
- New: Add
composer.json
for PHPUnit Polyfill dependency - Change: Prevent PHP warnings due to missing core-related generated files
Full changelog is available in CHANGELOG.md.