Releases: mantekio/wp-arabic-slug-schema-guard
Release list
v1.3.0
v1.3.0
Re-syncs the Layer-2 fork with core (it had dropped core's entire
"strip these characters entirely" block since 1.0.0, so Arabic guillemets, LRM/RLM,
curly quotes and copyright survived into slugs), inverts ASG_L2_FAILSAFE away from
silent 200-byte truncation, rebuilds wp asg verify --data around what a real
Arabic corpus proves rather than what an encoding regex can see, and makes the plain
wp asg verify fail on both silent-truncation states so verify || alert works.
Adds a test suite that refuses to certify what it cannot verify.
Full changelog: CHANGELOG.md
v1.2.0
v1.2.0: per-layer switches; rename to wp-arabic-slug-schema-guard
v1.1.2
v1.1.2: document Composer install requirements (allow-plugins + mu-plugins autoloading), no functional changes
v1.1.1
v1.1.1: documentation and comment cleanup (no functional changes)
v1.1.0
feat: self-test the Layer-2 slug fork against core (v1.1.0)
remove_filter() leaves sanitize_title_with_dashes() callable, so the plugin now
uses core's own current implementation as a live oracle: it diffs the fork against
it on short fixtures (where neither byte cap fires), once per core version. On
divergence it logs + emails, and — with ASG_L2_FAILSAFE defined — falls back to
core's generator (slugs cap at 200) instead of running a drifted copy. Closes the
one silent-rot risk in the design: a future core rewrite of that function now
shouts the hour it happens, instead of surfacing weeks later as a 404 cliff.
- Layer-2 install is conditional on the drift status
- asg_l2_status is autoloaded (the fail-safe reads it on every request)
- README documents the self-test + the new ASG_L2_FAILSAFE constant