FAQ¶

Short answers to the questions people ask about Gorilla Version Pin, the same questions as on the About tab under Tools → Version Pin, each with a link to the full explanation.

What do version numbers like 5.3.7 mean?¶

5 is the major number, 3 the minor number and 7 the patch number. The first changes for big changes that can break things, the second when features are added, and the last for small fixes, including most security fixes. Version Pin calls the first two numbers the series: 5.3.7 is in the 5.3 series. See What 5.3.7 means.

What is the difference between an exact pin and a patch pin?¶

An exact pin allows nothing newer than the pinned version. A patch-only pin also allows newer releases in the same series: pinned at 5.1.4, 5.1.5 and 5.1.10 install, and 5.2.0 waits until you raise the pin. Betas and release candidates are never allowed. See How it works.

Will an exact pin stop security updates?¶

Yes. That is why patch-only pins exist: if a security fix is released inside the pinned series, a patch-only pin lets it through. For plugins not hosted on WordPress.org, only when the vendor offers it. If you need a fix from a newer series, raise or remove the pin. See Allow an update.

How do I know a newer version is being held back?¶

A line under the pinned plugin says so, on the Plugins screen and on the Pins tab, for example "5.7.2 is available, held back by this pin." The same goes for WordPress. The newer version comes from WordPress's own update check, so nothing extra is requested. See Held back.

Why did my patch pin not receive an older-series fix?¶

Because WordPress only offers a plugin's newest release. If the author has moved on to 5.2 and then publishes 5.1.7 as a fix, WordPress never offers 5.1.7. For plugins hosted on WordPress.org, switch on Find older-series fixes; for premium plugins, only what the vendor's updater offers can be allowed. Some authors publish no fixes for older series at all. See Older-series fixes.

What happens with WP-CLI?¶

wp plugin update and wp plugin install --force are refused for a version outside the pin, with a message naming the pin. That is deliberate: a pin that the command line ignores is not a pin. Remove the pin first with wp version-pin remove <plugin>. See WP-CLI.

What if a pinned plugin is updated anyway, for example over FTP?¶

The pin shows Drift, on the Pins tab and on the Plugins screen, so you can see it and decide: roll back, or raise the pin. No plugin can stop files being copied over FTP or deployed with git. See Drift.

What happens if I delete a pinned plugin and install it again?¶

The pin still applies, and shows Missing while the plugin is deleted. Installing a version outside the pin is refused. Install the pinned version, for example from a zip, or remove the pin first. See Reinstalling a deleted plugin.

Does it work with other update managers?¶

Yes, but two plugins that both control updates make it hard to see which one is deciding, so use one. The Pins tab shows a note when it finds another. See Other update managers.

What happens when I deactivate or delete Version Pin?¶

While it is deactivated, pins do not apply; they apply again when you reactivate it. When you delete it, all pins are removed and updates behave normally again. See While Version Pin is deactivated.

Does it send any data anywhere?¶

Not unless you switch on Find older-series fixes. That asks WordPress.org for the release lists of patch-pinned plugins hosted there, and like every WordPress update check the request carries your WordPress version and site address. Nothing else is sent. See What is sent, and when.

What does "Find older-series fixes" do?¶

It lets a patch-only pin receive a fix that an author released for an older series, which WordPress itself never offers. It asks WordPress.org for the release lists of your patch-pinned plugins hosted there, and offers the newest release in your pinned series. It is off by default. See Older-series fixes.

Does it work on multisite?¶

Not yet. On a multisite network it enforces nothing, and its screen says so. See Multisite.

What should I send with a support request?¶

The system information from the About tab: open System Information, choose Copy to Clipboard and paste it into your request. It lists the plugin, WordPress, PHP and database versions, the server software, the active theme and the number of active plugins. It also includes your site's addresses, so check it before you post it in a public forum.

How do I report a security issue?¶

Please do not post it in the support forum. Report it privately through the Gorilla DevOps contact form.