Sarcio @sarcioai

@emoabj @Hostinger You weren't alone. A lot of people lost an evening to that one: hosts quietly backported the fix and never said the number wouldn't change. Running end-to-end tests against production to confirm the site still worked is the part most people skip. Nicely done.

@christian_nolle That matches what we saw: shared hosts patch the whole server at once, so cheap-and-cheerful quietly won this week. The ones caught out were self-managed VPS boxes and anyone still on PHP 8.1 or older, where there's no fix to install. Any of yours stuck on an old version?

@PierreJoye @mikailhamzat Sixteen years on, the Cobol half of the title aged well, just not the way it meant: it's still running the things nobody dares switch off. The difference is PHP shipped fixes for four branches in a day.

@PierreJoye @mikailhamzat The obituary writers turned out to be the ones with the shorter lifespan. And credit where due: four supported branches patched in one release this week while half the internet was writing PHP's eulogy again.

@catmanyau @batuhan @jetpack Only the panel reloads, never the chat, and it does exactly the first part: saves the scroll position, flips, restores it once the page renders. An element anchor is a smart upgrade for when the change itself pushes content down. Adding it to the list.

Existing content is the main use: edits to pages, posts, menus, site styles, shop settings and prices all land on the preview first. The exceptions are things that don't exist yet to preview, like a brand-new page, a coupon or a plugin install. Those ask you to approve them on the spot.

Plugin 0.16.2, a 14-day trial with no card: sarcio.io/wordpress

New tonight: your preview now sits right beside the chat. Ask for a change, watch it land on your real pages, click around your site, and flip between your changes and what visitors see without losing your place. Nothing goes live until you apply it. Someone asked for this here a few hours ago. It's shipped.

New tonight: your preview now sits right beside the chat. Ask for a change, watch it land on your real pages, click around your site, and flip between your changes and what visitors see without losing your place. Nothing goes live until you apply it. Someone asked for this here a few hours ago. It's shipped.

@catmanyau @batuhan @jetpack Done. Shipped tonight in 0.16.1: the preview bar now has a Show live button. Flip any page between your changes and what everyone else sees, as often as you like, without applying or losing anything. Thanks for the nudge.

keyboard_arrow_left Previous keyboard_arrow_right Next

@DrAi404 @Pirat_Nation Finally, readers who make it past the homepage. Shame they only ever ask for the database password and never leave a comment.

We went with the real page over a diff: the change lands on a private preview of your own site that you click around in, and each step the assistant takes comes with a one-line "why". Owners judge by looking, not by reading fields. A field diff is great for developers though, and worth offering as a second view.

@LiveOverflow @0x4D31 The scanners checked the last post date, saw 2023 and assumed the server had already been abandoned to someone else. Most underrated security control of the year: a blog nobody, including the attackers, believes is still alive.

@Nonosam2 The three stages of a site going down this week: 1. it's PHP2Shell, 2. it's the host, 3. it's the thing I changed at 11pm. Glad you skipped straight to 3 and it was quick.

What usually gets a site back fastest after a copyright complaint: reply on the abuse ticket (not the support one) saying the specific URLs in the complaint have been removed. Hosts often block the whole account until that confirmation lands. If you think the complaint is wrong, ask them for the counter-notice process instead.

@stepru @GoDaddyHelp Following up on how to know: we wrote the whole check up step by step, in plain words, including what to ask GoDaddy and how to read the build date, since their patched PHP keeps the old version number. sarcio.io/docs/wordpress…

@djbobbydrake @GoDaddyHelp @GoDaddy Since a few people on GoDaddy cPanel hit the same wall, we put the steps in one place, including where GoDaddy moved the PHP setting (it's in your account now, not cPanel) and how to read the build date: sarcio.io/docs/wordpress…