Changelog

Every released version appears in the Quick Maps changelog below. The list comes straight from the WordPress.org plugin API, so it updates itself whenever a new build ships.

How to read a version number

Quick Maps uses a date-based version rather than semantic versioning. A release numbered 26.08.07.23 was built on 7 August 2026, at 23:00. A higher number is therefore always a later build, and there is no separate major or minor track to interpret.

Updating the plugin

Updates arrive through the normal WordPress channel. Open Plugins, then Updates, and Quick Maps appears there like any other directory plugin. Alternatively, download the current build from the WordPress.org listing and install it by hand.

An update never changes your shortcodes. The quick-maps tag, its attributes, and your saved defaults all survive, because a release overwrites no stored settings. Read the shortcode reference if you want to confirm what each attribute does.

What tested up to means

Each release declares the newest WordPress version it has been checked against. If your site runs something newer, then the plugin will usually still work, since it leans on long-stable core APIs. However, that declaration is what the directory listing shows, and we raise it as we test.

Rolling back to an older build

Previous versions stay available on the directory listing, under Advanced View, so a bad update is never a dead end. Download the build you had, deactivate the current one, and install the older zip. Then tell us what broke, because a rollback that nobody reports gets shipped again.

Reporting a problem in a release

If a build breaks something, say so on the support forum with your WordPress version and the shortcode you used. We reproduce it, fix it, and record the fix in the next entry of this Quick Maps changelog. For licensing or billing questions instead, use the contact form.

Styling and facade options ship separately in Quick Maps Pro, which follows the same version scheme and the same update channel.