SiteSelf Connector

Descrição

SiteSelf is a service that works on your WordPress site for you and reports
back in chat. This plugin is the part that lives on your site. It lets your
agent work on your theme and plugin files, settings and updates, not only on
your content.

What it can do

  • Read and write files in your themes, plugins and must-use plugins folders
  • Send SiteSelf a copy of those folders, so SiteSelf keeps a history of your
    site’s code, and write a change from that history back on your yes
  • Tell SiteSelf how the site is built: WordPress and PHP versions, theme,
    plugins and host
  • Read and change your site’s settings, except settings that hold a
    credential and a few that are never changed (listed below)
  • Update plugins, and install, update, switch and delete themes
  • Make a backup of your database on your own server before a plugin or theme
    is updated or deleted, and before PHP code that changes your site runs
  • Clear caches
  • Send SiteSelf a copy of your database and site code, and measure the
    site’s size, when SiteSelf asks. SiteSelf does not use this yet.
  • Run PHP code that SiteSelf sends, inside WordPress
  • Keep a log of what it did, under Tools SiteSelf

Limits

  • It never sends or changes a setting whose name looks like a key, token or
    password. It never changes your site’s address, who may sign up, or the
    user roles.
  • It writes files only inside your themes, plugins and must-use plugins
    folders, and never follows a symlink out of them.
  • It follows WordPress’s own file permissions, so DISALLOW_FILE_MODS,
    DISALLOW_FILE_EDIT and a host that turns file changes off apply to it.
  • Before it replaces a file, it keeps the previous version. It refuses PHP
    files with a syntax error.

These limits apply to the plugin’s file and settings requests. PHP code that
SiteSelf sends runs as WordPress code, and these limits do not apply to it.

How access works

The plugin works only for a WordPress administrator signed in with an
application password. You create that password when you connect, and you can
revoke it at any time under Users Profile Application Passwords.

External services

This plugin connects your site to SiteSelf, a service run by Refact at
https://siteself.com. It does not work without that service.

The plugin contacts api.siteself.com only when an administrator acts:

  • Connect this site / Get a new key: a new application password (Connect
    only), your username, the site’s addresses, its public identity key, whether
    it uses Elementor, Divi, Beaver Builder or WooCommerce, whether your host
    marks it as a staging copy, and the plugin version.
  • Disconnect, deactivate or delete: the site’s id and addresses, the reason,
    and the plugin version. No credential is sent.
  • Check again: a request to api.siteself.com/health, to see whether SiteSelf
    answers. It sends nothing about your site: SiteSelf sees only your server’s
    IP address, as any website it contacts does. The same button has your site
    load its own REST API, a request that stays on your site.

Otherwise the plugin only answers requests from SiteSelf. What those requests
can return:

  • How the site is built: site name, addresses, language, WordPress and PHP
    versions, plugins, theme, host, server software, install path, post and page
    counts, and whether file changes are allowed.
  • Your themes, plugins and must-use plugins, file by file, without files that
    hold credentials, repositories, logs, caches and backup archives.
  • The contents of a file in those folders, a folder listing, or a setting’s
    value, with credentials hidden.
  • Before SiteSelf changes something, the database rows the change touches, so
    SiteSelf can undo the change. These rows can hold your content and personal
    data your site stores.
  • Whatever PHP code SiteSelf sends prints or returns. This can be anything
    WordPress can read, including your content and your users’ personal data.
  • A copy of your database and site code, as described under “Site copy”
    below. The database copy holds your content and the personal data your
    site stores.

Site copy (not in use yet). The plugin can send SiteSelf a copy of your
database tables and your site’s code, without uploads, wp-config.php or
files that hold credentials. It can also report the size of your tables and
folders, and your free disk space. Only SiteSelf’s own systems can ask for
this. SiteSelf does not ask for it today. Each copy shows in the log under
Tools SiteSelf.

Backups stay on your server and are never sent to SiteSelf.

Service terms: https://siteself.com/terms
Privacy policy: https://siteself.com/privacy

Instalação

This plugin does nothing on its own. It is the site-side half of a service, so
there is a short setup after you activate it.

  1. Install and activate the plugin. It opens Tools SiteSelf, which lists
    what your site needs to connect and how to fix anything missing.
  2. Select Connect this site. The plugin creates an application password for
    your account and sends it to SiteSelf, which answers with a key.
  3. Copy the key and paste it at https://siteself.com/setup/key.

There are no settings to configure. Tools SiteSelf shows what your agent
has done, the previous versions of any file it replaced, and a button that
disconnects the site.

To stop it at any time: select Disconnect under Tools SiteSelf, or delete
the plugin. Either tells SiteSelf and removes the application password the
plugin created. Deactivating the plugin keeps your site connected.

Perguntas frequentes

Can I see what the agent has done?

Tools SiteSelf lists the last 500 actions made through this plugin. Content
changes go through WordPress’s own REST API, so they are not in this log.

How do I stop it?

Select Disconnect under Tools SiteSelf, or delete the plugin. Either
tells SiteSelf, removes the application password the plugin created, and
takes effect immediately. Deactivating the plugin keeps your site connected.

Does it run code on my site?

Yes, when SiteSelf sends it, and only then. The plugin can write and run PHP
code, only on a WordPress site connected to SiteSelf, a SiteSelf customer’s.
Your agent uses it to read data and, when a job needs it, to change your site.
Every run is in the log under Tools SiteSelf, with the start of its code. To
stop it, disconnect the site or delete the plugin.

Does it work without the SiteSelf service?

No. This plugin is the site-side half of a service at https://siteself.com.

Where are backups kept?

In a siteself-backups folder on your server, outside the public web folder
(on WP Engine, in its private folder). To choose another folder, define
SITESELF_BACKUP_DIR in wp-config.php. The newest five are kept. If there is
no private folder, no backup is made. The change still goes ahead, and your
agent tells you that there was no backup.

Can it edit files if my host has locked them down?

No, and that is deliberate. It asks WordPress the same question WordPress asks
before showing you its own file editors. If your host or your wp-config.php
has switched file changes off, this plugin is refused too, and your agent will
tell you which setting stopped it.

Avaliações

Não há avaliações para este plugin.

Colaboradores e desenvolvedores

“SiteSelf Connector” é um programa de código aberto. As seguintes pessoas contribuíram para este plugin.

Colaboradores

Registro de alterações

0.11.4

  • Tools SiteSelf checks what your site needs before you connect: PHP,
    application passwords, whether it can reach SiteSelf, its REST API and a
    public address. Each check that fails says how to fix it.

0.11.3

  • Fixed: on a server whose PHP has no sodium extension, Connect stopped with a
    fatal error and WordPress paused the plugin. It now connects.
  • If Connect runs into an unexpected error on your site, the plugin shows it
    with a code to send us, instead of stopping.

0.11.2

  • No change to the plugin. This page now describes what the plugin does more
    plainly, and says more clearly what it sends to SiteSelf.

0.11.1

  • The changes listed for 0.11.0, which was not published to this directory.

0.11.0

  • SiteSelf keeps a history of your site’s code, must-use plugins included,
    through this plugin alone, and can put any change to it back.
  • Your agent can change your settings, and install, update, switch and delete
    plugins and themes. What a change did to your database can be put back.
  • The plugin can run PHP code that SiteSelf sends, only on a site connected to
    SiteSelf. See “Does it run code on my site?” in the FAQ.
  • Before a plugin or theme is updated or deleted, and before PHP that changes
    your site runs, a backup of your database is made on your server.
  • A change to a must-use plugin that stops your site from loading is put back
    at once.

0.10.0

  • Your agent can work with more of your site’s settings.

0.9.0

  • Deactivating the plugin no longer disconnects your site. SiteSelf is told
    the plugin is off, and your site stays connected.
  • Deleting the plugin now disconnects your site, as deactivating it did before.
  • Tools SiteSelf offers Deactivate beside Disconnect, says under each what it
    does, and asks before either.

0.8.3

  • Connecting and disconnecting now work on a server whose clock is wrong.

0.8.2

  • Sites connected to SiteSelf before 0.7.0 now show as connected.
  • Disconnecting also sends this site’s addresses, so a staging copy of your
    site is not taken for the live one.
  • Read-only files are left unchanged, and .phtml and .inc files are checked
    for PHP errors too.
  • Other small fixes.

0.8.1

  • A file is saved in one step, so it is never left half-written.
  • If a PHP change causes a fatal error on your home page, the previous version
    is put back.
  • Credential files, such as .env files and private keys, are not read.

0.8.0

  • When SiteSelf builds a staging site from yours — a private working copy
    where a change is tried before it reaches your live site — the plugin sends
    it your database and your site’s code in small, checksummed pieces, when
    SiteSelf’s own systems ask; never your uploads, wp-config.php or a file
    that holds a credential. See “Staging sites” above.
  • Your agent can make a backup on your own server before it changes your live
    site, covering the database tables and theme or plugin files the change
    touches. Backups stay on your server, in a private folder, and are never
    sent anywhere; the newest five are kept.
  • Your agent can change two settings through the plugin: whether search
    engines may index your site, and the separator Yoast SEO puts in page titles.
    Each change reads the setting first, is written the way WordPress’s own
    screens write it, and is read back. Every change and every refusal is in the
    log under Tools SiteSelf.
  • The plugin can measure your site — the sizes of your database tables and
    folders, free disk space and your server’s PHP limits — so SiteSelf knows
    what a copy or a backup takes before it starts one.

0.7.2

  • No change for your site. The status the plugin reports to SiteSelf no longer
    includes a setting that always read “no”, whatever your server has. It was
    about how that one request ran, not about your server, and it was misread.

0.7.1

  • No change for your site. Tools SiteSelf now takes the SiteSelf address it
    names, and the link where you paste your key, from the one address this copy
    of the plugin connects to, rather than writing them out separately. A copy
    that SiteSelf’s team points at its test service now sends its key there too.

0.7.0

  • Connecting your site is now one button. Press Connect this site and the
    plugin creates an application password for SiteSelf, sends it to SiteSelf
    with your site’s address, and shows you a connect key. Paste that key at
    siteself.com and your site is connected. You no longer type your site’s
    address anywhere.
  • Getting a new key does not create a new application password.
  • Activating the plugin opens its screen, Tools SiteSelf, once. Bulk
    activation is left alone.
  • The screen is shorter: three steps to connect, with what Connect sends one
    click away.
  • Disconnect and Deactivate are separate. A connected site shows Disconnect,
    which asks you to confirm and keeps the plugin active so you can connect
    again. A site that is not connected shows Deactivate.
  • Disconnecting keeps this site’s SiteSelf identity, so connecting again is
    recognised as the same site.
  • A connected site says so at the top of Tools SiteSelf, in green.
  • Disconnect and deactivation now tell SiteSelf, so the site shows as
    disconnected there too, and remove the application password the plugin
    created. Updating the plugin does not disconnect it.
  • A connect key now works for a year, until it is pasted or replaced by Get a
    new key.

0.6.1

  • No change to the plugin. A link in the repository’s own README pointed at a
    file that moved, and the version moves with any change inside the plugin
    folder.

0.6.0

  • Closed a hole in the file rails. A file that was a shortcut to somewhere else
    (a symlink) could be written through, which meant a write inside your themes
    folder could change a file outside it. Those are now refused. If you have
    deliberately symlinked a theme or plugin file, your agent will now say it
    cannot write to it rather than quietly changing the file at the other end.
  • File editing now uses exactly the permissions WordPress uses for its own
    editors. On a multisite network this is a real change: only a network
    administrator can edit theme and plugin files now, because those folders are
    shared by every site on the network. A single-site administrator is
    unaffected. Sites whose host switches file changes off through a filter
    rather than a constant are now correctly refused as well.
  • Tools SiteSelf and your SiteSelf dashboard now report whether writes are
    actually permitted, rather than only whether the two wp-config.php
    constants are set. The two can disagree, and it was the second one that was
    being shown.

0.5.0

  • Updates now come from WordPress.org, like every other plugin on your site.
    Earlier versions fetched their own updates from siteself.com because this
    plugin was not in the directory yet. Nothing changes on your Plugins screen —
    the update button is in the same place and works the same way.
  • This is the last update that arrives from siteself.com. After it, your site
    checks WordPress.org.

0.4.0

  • Your site can now tell SiteSelf who it is, so moving to a new domain no longer
    looks like a different site. The plugin creates a key the first time SiteSelf
    asks about your site, and keeps it here. The private half never leaves your
    server — not to SiteSelf, not in any request.
  • Nothing else changes, and there is nothing to set up. If you move your site,
    restore a backup, or your host makes a staging copy, SiteSelf can tell which
    one is which instead of guessing from the address.
  • Removing the plugin leaves the key in place, so reinstalling brings your site
    back as the same site. Disconnect, under Tools SiteSelf, is what removes it.

0.3.0

  • Updates now arrive on your own Plugins screen. Earlier versions had no way to
    tell WordPress where newer copies live, so updating meant deleting the plugin
    and uploading a zip by hand. It is now an ordinary one-click update, and can
    be turned on for automatic updates like any other plugin.

0.2.0

  • Renamed from “Refact Agent Connector” to “SiteSelf Connector”, including the
    plugin folder and the REST namespace. WordPress treats a renamed plugin as a
    different one, so this version had to be installed by hand alongside removing
    the old one — the change in 0.3.0 exists so that never happens again.

0.1.0

  • First release: status, file read/write with backups, allowlisted settings
    reads, cache flush, and the activity log.