Sarcio

Build and change your WordPress site by asking in plain words. Preview it, approve it, undo it anytime. When something breaks, Sarcio drafts the fix.

[Sarcio @sarcioai]

Meet Sarcio: build and change your WordPress site by asking in plain words. You see the change on a preview of your real site, then apply it. Every change can be undone.

13 seconds, real recording: new opening hours, previewed and live.

[Sarcio @sarcioai]

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.

[Sarcio @sarcioai]

Plugin 0.16.2, a 14-day trial with no card: https://t.co/3IY4Y8WFGj

[Sarcio @sarcioai]

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.

[Sarcio @sarcioai]

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.

[Sarcio @sarcioai]

@catmanyau @batuhan @jetpack Full-page toggle on the site itself. The highlighting lives in the assistant's chat, where each change shows as a before and after with the changed words marked. Scroll position: not yet, the flip reloads at the top. Keeping your place is a small fix and next on the list.

[Sarcio @sarcioai]

@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.

[Sarcio @sarcioai]

@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.

[Sarcio @sarcioai]

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.

[Sarcio @sarcioai]

@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.

[Sarcio @sarcioai]

@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.

[Sarcio @sarcioai]

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.

[Sarcio @sarcioai]

@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. https://t.co/2SgjEI2dRt

[Sarcio @sarcioai]

@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: https://t.co/pmoaQ9sj0Q

[Sarcio @sarcioai]

Sorry, that's rotten luck. Sounds like you're in good hands. For when it's back: patched PHP stops new break-ins but doesn't remove what got in, so a restore from before the hack plus new passwords everywhere (site admin, hosting, database) is what makes it stick. Worth a quick look for admin users you don't recognise too.

[Sarcio @sarcioai]

@drwesterfield @willardhoppe @GoDaddyHelp @djbobbydrake If it helps getting the site back up, the steps for reading the build date are written out here, including the GoDaddy details (the PHP setting moved out of cPanel into your account). https://t.co/izoqoikJ1P

[Sarcio @sarcioai]

@joshuavandercar @bluehost @frosterxpalt @ThePHPF You asked for a page, so we wrote one: the fixed versions, how to confirm the fix with the build date, and what owners found at Bluehost (PHP is set in two places that can disagree). https://t.co/2SgjEI2dRt

[Sarcio @sarcioai]

The guide: version numbers, where WordPress shows yours, what owners found at GoDaddy, Bluehost and cPanel hosts, and the one question to ask your host. https://t.co/2SgjEI1G1V

[Sarcio @sarcioai]

Is your WordPress site patched for the PHP fix? The version number might not tell you.

Many hosts put the October 21 fix into the PHP they already run without changing the number. GoDaddy customers are seeing 8.4.26 with a build dated 10/21.

The build date is the proof. We wrote up how to check it, host by host, in plain words.