外掛標籤
開發者團隊
原文外掛簡介
Ask for a change in plain words, such as a new phone number in the footer or a product on sale. Sarcio makes it on a preview of your real site that only you see. Apply it when it looks right; undo it any time.
What you can ask for
Pages, posts and products, including the words on Elementor and Divi pages
Menus, header and footer text on block themes, and colours and fonts through the site styles or your theme’s own options
WooCommerce prices, sales, coupons and orders (never a refund)
Comments, redirects (with Redirection), alt text, and SEO titles (with Yoast SEO or Rank Math)
Your other plugins’ settings, through their own checks
Changes you apply are listed under Recent changes with an Undo button. A change can also be scheduled for a time you pick, with an optional time to change it back.
When something breaks
A Report a bug button lets people say what is wrong on the page; you choose who sees it. Sarcio drafts a small fix, explained in plain words, into Sarcio → Inbox. Preview it on your site, approve it with your Sarcio password or an authenticator code, and an administrator can keep it: a kept fix works even without Sarcio.
Updates with a way back
Ask the assistant to update a plugin or theme from WordPress.org. It checks your key pages before and after, and puts the earlier version back on its own if something broke. It checks that your pages work, not what an update contains.
What it will not do
It works as you, so it can only do what your WordPress role allows. It never edits theme or plugin files, writes code or changes page-builder layouts, and installs plugins only from WordPress.org, only when you tick the box. Anything it can do can be switched off under Settings → Sarcio → Assistant.
Looking after client sites?
One Sarcio account covers your client sites. With “Who applies changes” set to administrators, a client’s changes wait under Sarcio → Requests for an administrator to apply, and your Sarcio Inbox lists them. Your agency’s name, logo and colour replace ours on the screens a client sees, and each site can email a monthly report. See https://www.sarcio.io/wordpress/agencies
Set up in a minute
Install, open Sarcio in the left-hand menu and click Start free. Plans start at $19 a month for one site, 14 days free with no card: https://www.sarcio.io/wordpress. Developer settings are under Installation and the FAQ.
External services
This plugin connects to the Sarcio service, operated by Sarcio (Dayne Mentier) at sarcio.io: the control plane https://control.sarcio.io, https://www.sarcio.io and your workspace’s https://
Connecting. When an administrator clicks Start free or a Connect button, or a user who can review patches clicks Connect your Sarcio account, their browser goes to https://www.sarcio.io/app carrying the site’s name, its home address, its admin address, the address to return to, which button was clicked and, for an account connection, the site key. After they confirm in Sarcio, the browser returns with a one-time code, and your WordPress server exchanges that code with the control plane for the site key and secret key (site connections only) and a Sarcio sign-in for that WordPress user.
Loading the reporter widget. On pages where the widget is enabled, the visitor’s browser loads the widget script from https://control.sarcio.io/sarcio.js, which nothing in the plugin can change. The request carries the usual browser data (IP address, user agent, referring page) and your site key.
Fetching and receiving patches. The widget fetches your site’s active, signed DOM patches and your workspace’s public signing key from the control plane, and keeps a WebSocket open to receive newly approved patches. These requests carry your site key and the page origin, and no personal data.
Submitting a bug report. Only when a person who can see the reporter presses Send report, the widget sends the report to the control plane: the description they typed, the page URL, the browser’s user agent and viewport size, an optional screenshot of the page, the selector and HTML of an element they picked (if any), and recent console errors and warnings plus metadata of recent network requests on the page (method, URL, status, duration, content type; never request or response bodies or authorization headers).
Sarcio noticed. Only after an administrator turns it on for the site in the Sarcio dashboard (Sites → Manage → Sarcio noticed), the widget sends the control plane, when a visitor leaves a page on which something failed, one line per failure: the text of an error the page logged, or the method, address (without its query string) and status of a request that came back broken, and on a WooCommerce checkout page whether the checkout form and a way to pay showed. Nothing the visitor typed, no page content, no cookies, no screenshot; the request carries the site key and the usual browser data. Sarcio opens a report once several visitors hit the same failure (sooner, marked urgent, for a broken checkout).
Fetching server patches. When you enter the site’s secret key, your WordPress server (not the visitor’s browser) requests your site’s active, signed server patches and your workspace’s public signing key from the control plane: on WP-Cron when the cached set is older than the refresh interval (30 seconds by default), after you save the settings, when you press Check for patches now, or on wp sarcio pull. The requests carry your site key, the secret key as a bearer token (patches only; the signing key request is anonymous) and a user agent naming the plugin’s shim version. No visitor or request data is sent.
Workspace details. Your WordPress server sends the control plane your admin’s address (scheme and host only), with the site key and the secret key, and gets back your workspace’s name, its address and its branding, which the Sarcio pages show and link to.
Staying signed in. The Sarcio sign-in from connecting is stored for that WordPress user only, encrypted with a key derived from your site’s salts, and renewed when due (a daily WP-Cron task). While that person has the Inbox or Live fixes page open, your server uses it to read this site’s open reports, their fixes and the live fixes (and to look up this site, so nothing from another site shows), and to send what they choose: preview, approve, turn down, turn a live fix off, or ask for a different fix with their note. Approving or turning off asks for their Sarcio password or an authenticator code, passed on for that one request and never stored. Signing out deletes the sign-in and asks the control plane to revoke it; uninstalling deletes every stored sign-in. These requests carry the sign-in and the site key, and no visitor data.
Update checks. Only when a safe update finds a problem, your WordPress server sends the control plane the update’s name and versions, what changed on each key page it looked at (its name, address and a few words such as “server error 500”) and what it did, then the owner’s choice, with the site key and secret key. The checks themselves only open your own pages from your own server.
Keeping a fix. Only when an administrator clicks Keep this fix, your WordPress server asks the control plane for that fix’s signed details (site key and secret key) and your workspace’s public signing key, checks the signature, and saves the fix in this site’s database. From then on the fix is applied by the plugin itself, with no request to Sarcio; page fixes are applied by a small script bundled with the plugin and printed into your own pages.
Asks across sites. Only after an administrator ticks Receive changes your agency writes for several sites under Settings → Sarcio (off by default), every five minutes a connected site asks the control plane whether the agency wrote a change for it (site key and secret key). If so the assistant prepares it as a preview (the conversation request above, limited to content and design; never plugins, themes, users or settings) under Sarcio → Requests and reports one line per change. No visitor data is sent.
Review links. Share for review makes a link on your site; anyone opening it gets a cookie for a week, sees the preview served by your own server, and can pin notes (a name they type, the note, the page and the spot). Notes stay in your site’s database and reach the control plane only when the assistant is asked about them.
Waiting reports. While someone who can review fixes is in wp-admin, your WordPress server reads how many of the site’s reports are waiting, how many fixes are live, and (with Sarcio noticed on) which failures visitors hit this week (site key and secret key), at most once every two minutes, for the count on the Sarcio menu and the Dashboard boxes. No visitor data is sent.
The assistant. Only when a person who can review fixes sends a message on the Sarcio → Assistant page, your WordPress server sends the control plane that conversation (what they typed, the answers, and the results of what it looked up or changed, such as a page’s text), the list of changes that person is allowed to make here, and these site details: name, home and admin addresses, WordPress version, active theme, language, time zone, whether WooCommerce is active, whether plugins may be installed, and the person’s role. The request carries the stored sign-in and the site key. The control plane answers with text and the next change to look up or make; every change runs on your WordPress server, by this plugin, as that person, and never from the control plane. In a long conversation the oldest messages are sent once more to be summarised, and the summary replaces them. Installing a plugin from the assistant downloads it from WordPress.org exactly as Plugins → Add New does. Conversations are saved in this site’s own database, per person, never in Sarcio; the preview is held on your site, keyed by a cookie for your browser alone, until you apply or discard it or for two hours. When you ask about them, that context can also include: other plugins’ settings (any setting whose name says it holds a key, token, password or licence is replaced by “(hidden)” before it leaves your site) and the names and descriptions of their abilities; comments (name and words, never email or address); categories, tags, earlier versions of a page and redirects; recent WooCommerce orders (first name, items and total; never addresses, emails or payment details) and what sold; Gravity Forms entries (never kept in a saved conversation); plugins with updates waiting; users (display name, login and role; never an email or password); Site Health results, widget areas, Elementor’s global colours and fonts, and links on your own pages that answered with an error (checked by your WordPress server).
AI models. To draft fixes and answer the assistant, the control plane (never your server or your visitors’ browsers) sends the report or conversation above to an AI model through OpenRouter (https://openrouter.ai; terms https://openrouter.ai/terms, privacy https://openrouter.ai/privacy), which passes it to the model’s provider (Anthropic’s Claude models by default).
Usage. While the settings page is open, your WordPress server reads this month’s AI usage for the site from the control plane (site key and secret key), at most once every five minutes.
Previewing a server patch. When a browser opens the site with a preview link from Sarcio (?sarcio_preview=), your WordPress server sends that preview token, with the site key and secret key, to fetch the patch being previewed. It applies only to that browser, through a cookie that lasts up to 15 minutes.
Feedback when deactivating. Only when someone deactivating the plugin clicks Send and deactivate, your WordPress server sends https://control.sarcio.io their answer and note, the plugin and WordPress versions, the site’s language and whether it was connected; no address, site key, name or email.
With the optional Sarcio sidecar (a sidecar address is set under Advanced settings), the plugin talks only to that sidecar over a local socket on your host, and the sidecar fetches the patches instead.
The screenshot library, html2canvas 1.4.1 (MIT, https://html2canvas.hertzen.com), is bundled with the plugin and served from your own site; the plugin loads nothing from a third-party CDN.
Terms of service: https://www.sarcio.io/terms
Privacy policy: https://www.sarcio.io/privacy
