Skip to content
Situnio

Maintenance

Apply updates

Update WordPress, plugins and themes from Situnio: one item, one site or all your sites at once, premium included.

Part of the Maintenance pack.

On this page

From the Updates page#

  1. Open Updates. Each item shows its New version and the Affected sites.
  2. Click Update on the line you want, or Update all for everything.
  3. Confirm with Run, then keep the page open: it is what runs the updates. Three sites move forward at the same time, and a bar shows how far the batch has got, what each site is doing and what failed.
The Updates page
The Updates page

From a site page#

The Available updates part of the page lists this site’s items, and Update all (…) runs them in sequence.

See what changes before updating#

For a plugin published on WordPress.org, a small document icon follows its name on the Updates page, on the site page and in the plugin manager. It opens the plugin’s changelog: only the versions released since the installed one (on the Updates page, since the oldest one across your sites), with a link to the full changelog. The text comes from WordPress.org, as the author wrote it.

Premium plugins do not have this icon: their changelog is not published on WordPress.org.

Set an update aside#

A premium plugin without a licence announces new versions it cannot install. To stop it skewing your counters:

  • Licence required: when WordPress announces a version without providing a file to download, Situnio flags it on its own with Licence required. There is nothing to do: activate the licence in WordPress and the update comes back at the next sync. This needs a recent connector, which updates itself.
  • Ignore: on the site page, Ignore… offers Ignore version … (it comes back when a newer version is released), Always ignore on this site or Always ignore on all sites. On the Updates page, Always ignore applies to all sites.

These updates no longer count on the dashboard, in the site list or in Update all. They stay visible under Updates set aside, where Stop ignoring brings them back. Client reports list them separately, with the reason.

Ignoring requires the Apply updates and roll them back permission; ignoring on all sites is reserved for the owner and administrators.

Updates made in WordPress#

An update installed by WordPress itself, or from its dashboard, also shows up in the site’s Update history, marked In WordPress. Situnio spots it at the next synchronisation, because the version has changed: the date shown is when it noticed. Client reports count it, with a note about its date. There is no rollback for these: the previous version was not archived.

Turn off WordPress automatic updates#

WordPress installs some updates by itself, with no backup beforehand and no site check afterwards. You can turn them off, category by category: WordPress patches, New WordPress versions, Plugins, Themes and Translations. Each one is set to WordPress decides (as without Situnio) or Off.

  1. On the Updates page, in the WordPress automatic updates section, the Default setting applies to all your sites. Only the owner and administrators can change it.
  2. For a few sites, tick them in the list (or pick a tag), say what changes, then click Apply. Leave unchanged leaves a category as it is, Default setting puts it back on the organisation’s setting.
  3. For a single site, the same section is in the Updates tab of its page.

The setting goes to the sites right away. A site that does not respond receives it at its next synchronisation and shows Waiting to be sent until then. Situnio Connector always keeps its own automatic updates. This requires a recent connector, which updates itself. If the pack stops, everything is handed back to WordPress.

What happens, in order#

  1. Backup first: if you have enabled it and no backup less than an hour old exists, the site is backed up first. See Configure backups. If it fails, Situnio asks whether to continue.
  2. Archive of the current version: each plugin or theme is archived just before updating, which makes rollback possible.
  3. Update: one item at a time on a given site, in this order: WordPress, plugins and themes, Translations (language packs), then databases. Three sites are handled at the same time. Under each site, the page shows the languages its translations concern: several packs often target a single language (WordPress, then each plugin and each theme), and they all go together.
  4. Health check: Situnio checks the home page. If it no longer responds normally, you are told and can roll back.
  5. Site re-read: the state displayed is refreshed.

If the host blocks requests from the site to itself#

Premium offers use a request from the site to itself. If the host blocks it, add define('SITUNIO_CONNECTOR_NO_LOOPBACK', true); to wp-config.php.

The connector is too old#

Situnio then shows Connector to update. The connector updates itself: wait a few minutes, then synchronise the site.

Some translations remain after the update#

If WordPress could not install a language pack, the Translations line shows as failed and gives, for each pack, the plugin or theme, the language and the reason given by WordPress. The other packs are installed. Most common reasons: a file in the wp-content/languages folder that PHP cannot modify (uploaded by FTP with another owner: fix its permissions at your host), or an interrupted download from WordPress.org (just run the update again).

If the same translation comes back right after a successful update, the line also turns to failed with the note “Still offered after installation”. Most often, WordPress.org announces a newer translation than the file it sends: the site is not at fault, and the offer keeps coming back until WordPress.org fixes it, usually within a few days. Hovering over a site on the Updates page shows which plugins are concerned for each language.

Who can do it#

The organization’s owner and administrators. During a support session on your account, everything stays read-only.

Still have a question? Write to us.