| 开发者 | |
|---|---|
| 更新时间 | 2026年8月26日 00:23 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
tel: links, WhatsApp links, and phones whose characters are split across nested HTML elements.
Only the configured source number is changed. Other numbers and pages remain untouched.
Features
tel: links, and phone-based messenger URLs.span or small elements.dialperpage.zip, install it, and activate DialPerPage.No. Replacement is applied to the final HTML response. Posts, page-builder data, theme files, and templates are not changed.
The plugin performs one exact path lookup. When no rule matches, output buffering does not start and the HTML is not scanned or copied.
No. Only the configured source phone is matched. For 11-digit Russian phones, 7 and 8 prefixes are treated as equivalent.
Yes, when source and replacement numbers contain the same number of digits. Only digits change; separators and HTML spacing entities remain in place. Compact tel: values remain compact.
Yes. Inside a matching tel: link, the plugin can replace digits distributed across nested span and small elements while retaining their tags, styles, classes, and microdata.
Yes. Both https://example.com/service/ and /service/ are accepted. Query parameters are ignored, and matching uses the normalized path.
Saving settings automatically purges Hyper Cache, WP Super Cache, WP Rocket, W3 Total Cache, Cache Enabler, and LiteSpeed Cache when their public purge APIs are available. After updating from an earlier DialPerPage release, clear any remaining hosting or CDN cache once. Then test the page in a private browser window and confirm that the saved path exactly matches the page path.
On pages with an active rule, DialPerPage marks managed tel: links and loads a lightweight browser guard in the document head. If a third-party script such as a dynamic call-tracking service changes a marked link later, the guard restores its configured number before interaction. Unmanaged links and pages without rules are not observed.
DialPerPage follows the current WordPress locale. Community translations are managed and delivered through the standard WordPress.org language-pack system.