Menu

WordPress published a change nobody re-approved: the SHA-256 fix
πŸ“°

WordPress published a change nobody re-approved: the SHA-256 fix

DEV Community: phpΒ·Denis FejzaΒ·about 10 hours ago
#r3gcH7av
#devto#dev#approved#approval#publish
Reading 0:00
15s threshold

WordPress published a change nobody re-approved: the SHA-256 fix

A writer drafts. A reviewer signs it off. An hour before launch, somebody fixes "just a typo" β€” except the typo was the price in the third paragraph. The post still says approved . It still publishes.

Nothing in that story is a permissions bug. The approval was a flag with no memory of what it approved .

What actually breaks

What the site has What it proves What it misses

A status like approved , or "Editor can publish" Somebody pressed a button at some point Whether the text in the row is the text that was on screen then

Revisions History exists after the fact Nothing stops the write; you find out from a client email

A staging site A copy existed somewhere Production still accepts any edit, from anyone, at any time

A hash of title + content + excerpt taken at approval This exact text was signed off Edits, and nothing else β€” see the limits below

The first three answer "was this workflow followed?" .…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.