| @@ -3,9 +3,9 @@ | ||
| 3 | 3 | Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=4026696 |
| 4 | 4 | Tags: antispam, mail, spam protection, email encryption, privacy |
| 5 | 5 | Requires at least: 6.7 |
| 6 | 6 | Tested up to: 7.1 |
| 7 | -Stable tag: 4.2.0 | |
| 7 | +Stable tag: 4.2.1 | |
| 8 | 8 | Requires PHP: 8.1 |
| 9 | 9 | License: GPLv2 or later |
| 10 | 10 | License URI: https://www.gnu.org/licenses/gpl-2.0.html |
| 11 | 11 | |
| @@ -127,8 +127,14 @@ | ||
| 127 | 127 | |
| 128 | 128 | For more information, visit the [Plugin Homepage](http://weber-nrw.de/wordpress/cryptx/ "Plugin Homepage") |
| 129 | 129 | |
| 130 | 130 | == Changelog == |
| 131 | += 4.2.1 = | |
| 132 | +* **Fixed** with the JavaScript variant switched on, the script is now delivered on every page, not only on pages that themselves carry a protected address. Themes that exchange page content in the browser without rebuilding the document -- swup.js and other client-side routers work that way -- brought protected links onto the screen for which no click handler had ever been loaded. Those links did nothing at all until the visitor reloaded the page in full. It has been that way since 4.0.12, when delivery was made conditional on the page at hand | |
| 133 | +* **Fixed** the same for the stylesheet with "Instead of the address, show" set to one of the picture options: `css/cryptx.css` is now delivered as soon as a picture variant is configured, so a link that reaches the browser after the page was built is still shown at the right size | |
| 134 | +* **Fixed** a single click could open the mail program twice wherever a theme or a loader runs the script a second time on the same document. The guard against attaching the click handler twice is now kept on the document rather than inside the script, which also makes `initCryptxLinkHandler(document)` work on a second document, as it was always meant to | |
| 135 | +* if you run a full-page cache, empty it after the update: pages stored before it do not carry the script yet, and they stay broken until the cache turns over by itself | |
| 136 | + | |
| 131 | 137 | = 4.2.0 = |
| 132 | 138 | * **New** on a multisite network, the network administrator can set the defaults a newly created site starts with, under Network Admin / Settings / CryptX. Sites that already exist are never changed -- every site keeps its own settings, as it has since 4.1.1. Two settings are deliberately not shareable: excluded post IDs and the uploaded image refer to things that exist on one site only, and copying the first of them is exactly what left addresses unprotected before 4.1.1 |
| 133 | 139 | * **New** WP-CLI: `wp cryptx settings` reads and writes the settings, `wp cryptx scan` runs the body and the title of every published post through the real filters and reports the ones that still carry a readable address -- including addresses in titles, which CryptX cannot protect because a title reaches the page along a path no plugin filter touches. With `--url` both work per site, so a network can be handled from a shell loop rather than from forty screens |
| 134 | 140 | * **Fixed** changing "Key strengthening" under Advanced silently broke every link that had already been delivered -- in every cached page and in every browser tab still open. The number of rounds was read from the page's configuration at the moment of the click, not from the link, so a link made with the old value could no longer be opened. Each link now records what it was made with, and the ones written before this update keep working as they did |
| @@ -372,8 +378,11 @@ | ||
| 372 | 378 | = 2.4.0 = |
| 373 | 379 | * Add Option to disable CryptX on single post/page |
| 374 | 380 | |
| 375 | 381 | == Upgrade Notice == |
| 382 | + | |
| 383 | += 4.2.1 = | |
| 384 | +Fixes protected links that did nothing on themes which exchange page content in the browser. Nothing to do -- unless you run a full-page cache: empty it, because pages stored before the update do not carry the script yet and stay broken until the cache turns over. | |
| 376 | 385 | |
| 377 | 386 | = 4.2.0 = |
| 378 | 387 | Contains a security fix: with the picture variant, the address stood in the web address the picture was fetched under, and so in your access log. Also fixes changing "Key strengthening", which until now broke every link already published. Nothing to do. |
| 379 | 388 | |
