| 开发者 |
honza.skypala
vyskoczilova |
|---|---|
| 更新时间 | 2026年9月26日 04:58 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.1.2 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
zalomeni_filtry filter so developers can add or remove the WordPress hooks Zalomení applies to.
For more information on Czech typographic rules, see the Institute of the Czech Language.
wp-content/plugins/.Yes. The plugin returned to active development in 2026 under maintainer Karolína Vyskočilová (vyskoczilova on WordPress.org). Issues and security fixes are addressed promptly.
Please report security bugs found in the source code of the Zalomení plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.
2.0 i a huge security release by a new maintainer: all user inputs are sanitized, regex inputs are escaped, admin output is escaped, and the codebase is now covered by PHPUnit tests. Updating is recommended for anyone still on 1.x.
Yes. Zalomení runs on WordPress output filters (the_content, the_title, the_excerpt, etc.), so it works regardless of which editor produced the content.
No. Zalomení hooks WordPress output filters, so it rewrites content on the way to the browser only. Your posts stay exactly as you wrote them, and deactivating the plugin removes every inserted non-breaking space.
Yes. The default lists of prepositions, conjunctions, and abbreviations are Czech, but they're fully editable under Settings → Reading. Replacing the Czech entries with Slovak ones gives you a working Slovak typography filter without any code changes.
Yes. Wysiwyg fields run through ACF's own acf_the_content filter instead of the_content, so the plugin hooks that one too. Text and textarea fields never pass through any content filter — the theme prints them itself — so the plugin hooks acf/format_value/type=text and acf/format_value/type=textarea.
Themes usually escape those values with esc_html(), which would turn a entity into visible text. For that reason text and textarea fields get the non-breaking space character (U+00A0) instead of the entity. It renders the same and survives escaping.
The plugin applies to these filters by default: comment_author, term_name, link_name, link_description, link_notes, bloginfo, wp_title, widget_title, term_description, the_title, the_content, the_excerpt, comment_text, single_post_title, list_cats, acf_the_content.
Fields of Advanced Custom Fields are covered as well — see the ACF question below.
Yes. Use the zalomeni_filtry filter to remove or add filters:
add_filter('zalomeni_filtry', 'remove_title_from_zalomeni');
function remove_title_from_zalomeni(array $filters) {
unset($filters['the_title']);
return $filters;
}
The ACF field filters have their own list, zalomeni_acf_filtry, which works the same way:
add_filter('zalomeni_acf_filtry', 'remove_acf_textarea_from_zalomeni');
function remove_acf_textarea_from_zalomeni(array $filters) {
unset($filters['acf/format_value/type=textarea']);
return $filters;
}
acf_the_content, text and textarea fields through acf/format_valuezalomeni_acf_filtry filter to change the list of ACF filters the plugin hooks entity, so it survives escaping in the theme