Skip to content

Settings

Every setting of Gorilla Version Pin, what it does, its default and when to change it. All of them are on one tab, Tools → Version Pin → Pins, and one Save Changes button at the bottom saves them all. What the tab shows besides the fields is on The Pins tab.

WordPress core

Pins WordPress itself. The section is shown only to people allowed to update WordPress, as an administrator is.

Pin WordPress core

Switch it on to hold WordPress at a version. Default: off, and WordPress updates as usual. Switching it off and saving removes the WordPress pin; the note is kept for next time.

Pin at version

The highest WordPress version allowed. Default: the version running now; leave it empty to use that. Change it when you want to allow a little more, for example 7.2 once you have tested 7.2.

Patch releases

On: WordPress security and maintenance releases still install. Pinned at 7.1.3, 7.1.4 installs but 7.2 does not. Off: WordPress stays at exactly this version. Default: on. Leave it on unless you need WordPress to stay at one exact version.

Note

Why WordPress is held, for example "Waiting for the theme update before 7.2". Shown when an update is refused. At most 200 characters, one line. Default: empty.

Add a pin

Pins one more plugin. After saving, the plugin moves into the pin table and leaves this list. When every installed plugin is pinned, the section says "Every installed plugin is already pinned."

Plugin

Any installed plugin, active or not. Its installed version fills in below. Plugins that are already pinned, and Version Pin itself, are not listed. To pin a plugin that is not installed, use WP-CLI.

Pin at version

The highest version allowed, usually the one installed now. Default: the installed version; leave it empty to use that. A version starts with a digit and may hold digits, letters, dots and the characters +, _ and -, up to 40 characters. You can pin at two numbers, such as 5.1, to allow every 5.1 release: see Pinning at two numbers.

Patch releases

On: small bug-fix and security updates still install. Pinned at 9.9.3, 9.9.4 installs but 9.10.0 does not. Off: the plugin stays at exactly this version. Default: on. See Exact pin and Patch-only pin.

Note

Why the plugin is pinned, for example "9.10 breaks the checkout, ticket 218". Shown on the Plugins screen and wherever an update is refused. At most 200 characters, one line. Default: empty, but a note helps whoever looks at the site next.

Change a pin

Each row of the pin table holds the same three fields as Add a pin: Pin at, Patch releases and Note. Change them in the row and choose Save Changes. Raise Pin at to allow a newer version; the update is offered again with WordPress's next update check.

Remove a pin

Tick Remove in the plugin's row and choose Save Changes. The plugin then updates as usual. From the command line: wp version-pin remove <plugin> (WP-CLI).

Find older-series fixes

In the WordPress.org release lookup section. On: for each patch-pinned plugin hosted on WordPress.org, Version Pin asks WordPress.org for its release list, so a patch-only pin can also receive a newer release in its own series, such as a security fix for an older version. Default: off. Switch it on if you pin plugins from WordPress.org with patch releases. What it sends and when: Older-series fixes.

Save Changes

Saves everything on the tab at once: the WordPress pin, a new pin, changes to the pin table and the lookup switch. The messages you may see after saving are explained on The Pins tab.

Who can change pins

Anyone allowed to update plugins, as an administrator is, can see the screen and change plugin pins. Only people allowed to update WordPress see the WordPress core section. On a site where file changes are disabled, nobody can update plugins, so administrators can still see and change the pins.

Version Pin has no settings in wp-config.php.