❗️ UPDATE: Please note that VersionPress is not actively developed, see #1483

Maintenance release focusing on bug fixes and improvements of the dev / testing infrastructure.

Released 15 April 2019.

• Download
• Installation instructions

Developer Preview note:
VersionPress is not production-ready, use it with care. Learn more.

Highlights

The main changes since the previous beta are:

• Several bugs have been fixed by contributors @mkreckovic, @candrews, @lframnes, @x1024 and others.
• Our extensive test suite now fully passes and tests run automatically on Travis thanks to a great work done by @candrews. In general, we invested in a dev / testing infrastructure to make future contributions easier.
• @iamlisaross worked on modernizing our docs site and the results are awesome – each page is easily editable via GitHub, the dev topics like plugin support are published in the new "Developer" section, there is full text search now, etc. We blogged about it.

On a related note, @pavelevap is joining the project as an official maintainer and we hope to work on full Gutenberg compatibility next.

Full changelog

Noteworthy issues

#1259 Travis CI
#1389 Improve Dockerized testing infrastructure

Noteworthy pull requests

#1385 Fix merge driver on Debian-based systems (#1384)
#1324 Fix wrong SELECT and SHOW queries detection
#1370 Make getMenuReference return "terms" instead of "term_taxonomy" (#1369)
#1368 Deploying docs site to Netlify (#1367)
#1334 Switch to MkDocs for documentation (#1332)
#1329 Dev setup updates – spring 2018

Pull requests

#1425 Add --format markdown option to the changelog tool
#1424 Changelog script
#1423 Update docs on development process (#1417)
#1422 Fix run-tests.ts: return non-zero exit code when tests fail
#1415 Have Travis run tests (#1259)
#1418 Update frontend dependecies
#1414 Fix markdownlint violation in docs/content/en/troubleshooting/iis.md
#1411 Small updates of exploring the test WP site after tests have run
#1410 Fresh site setup before CloneMergeTest (workaround) (#1409)
#1403 Docker Toolbox on Windows – notes (#1389)
#1401 New run-tests.ts, making test runs more reliable (#1389, #1400)
#1404 'Scripts' project with its own package.json, deps update (#1389)
#1399 Stop containers after tests (#1389)
#1398 Use digests for Docker images (#1389)
#1396 Use named volumes for tests (#1389)
#1397 Run CLI image as UID 33 (Debian's "www-data") (#1389)
#1395 Separate docker-compose files for dev and tests (#1389)
#1394 Revert "Run tests in Travis" for now
#1393 Minor docs updates around dev setup and testing (#1389)
#1392 Docs: separate page on Testing (#1389)
#1388 Run CLI as user 33:33 to match Debian's www-data (#1383)
#1385 Fix merge driver on Debian-based systems (#1384)
#1381 Run tests in Travis (#1259)
#1379 Make sure the test-logs directory exists
#1377 Upgrade to PHP_CodeSniffer and fix newly identified issues
#1378 Use PHP 7.2 in Travis to be consistent with Docker images
#1375 require_once for WordPress includes (#1374)
#1372 Update lockfile for npm 6.7
#1371 Set the "z" option for Docker volumes
#1324 Fix wrong SELECT and SHOW queries detection
#1370 Make getMenuReference return "terms" instead of "term_taxonomy" (#1369)
#1368 Deploying docs site to Netlify (#1367)
#1358 Add VSCode settings
#1353 Update frontend dependencies (#1351)
#1348 Use markdownlint for Markdown files
#1349 Fix subheading nesting in plugin-support.md
#1343 Updated docs page on Developer Preview
#1342 Docs README small update
#1340 Document VP_WP_CLI_BINARY setting
#1341 Update intro section on Docker
#1338 Fix frontend package vulnerabilities (#1335)
#1337 Update frontend dependecies (#1335)
#1334 Switch to MkDocs for documentation (#1332)
#1329 Dev setup updates – spring 2018
#1318 Fix typo in activation message
#1314 Add error when re-activating VP with WP-CLI (#1313)
#1310 Use WP 4.9 for test sites – part 2
#1309 Make checkboxes for bulk update checkable (#1308)
#1307 Use WP 4.9 for test sites

Direct commits to master

77ad593c Link to Gitter and support repo in ISSUE_TEMPLATE.md
84d3229e Updated intro message to mention beta instead of alpha
8244d42a Added link to announcement blog post

See [all iss...

Building on 4.0-alpha1, this beta brings user-editable plugin definitions, better stability and support for WordPress 4.7 & 4.8.

Released 9 July 2017. Announcement blog post.

• Download
  • (Note: You can also download newer build from January 2019 – it contains several smaller fixes.)
• Installation instructions

Developer Preview note:
Developer Preview is a period during which VersionPress is reasonably stable but still young, limited in scope and external backup is recommended at all times. Learn more.

Notable changes

• For plugin definitions, the WP_CONTENT_DIR/.versionpress/plugins/<plugin-slug> location is now supported and actually preferred #1176
• Filterable action priorities #1232
• Support for serialized arrays inside serialized arrays, a.k.a., inception #1234
• Most actions now use the verb 'update' rather than 'edit' #1120
• Schema updates for WordPress 4.7 (#1164) and 4.8 (#1217)
• Fixed many bugs reported in 4.0-alpha1
• Updates to Plugin-Support.md based on feedback (current state)
• Dockerized development environment and tests #1041
• Both backend and frontend dependencies updated after a while
• We've adopted GitHub projects to manage the development process
• 'Developer Preview' is now used instead of 'Early Access' #1201
• Docs have been merged into the main repo (used to be versionpress/docs) #1218

See all 120+ issues and PRs resolved in 2.0-beta or the GitHub project.

Upgrade notes

To upgrade from 4.0-alpha1 and earlier, uninstall (delete) the previous version and install again.

System requirements

• WordPress 4.8+
• PHP 5.6+
• Git 1.9+ (2.13 or newer recommended)
• proc_open() enabled

VersionPress 4.0 introduces support for WordPress plugins and themes. The other significant changes are a much-improved search, staging visualization and Composer workflows support.

This is the first alpha, released on 10th October 2016. Read the release blog post or see the full release notes.

• Download
• Installation instructions

Note: this is an Early Access release. These warnings and limitations apply.

New in 4.0-alpha1

Plugin support

👋 We're looking for feedback on this, please chat with us on Gitter.

Plugins can now be described to VersionPress using a set of plugin definitions in a .versionpress folder. These include:

• actions.yml defining plugin actions
• schema.yml describing how the plugin stores data in the database
• shortcodes.yml defining any new shortcodes the plugin introduces
• hooks.php containing any filters and actions further customizing the functionality

See docs/Plugin-Support.md for more details. Issue: #1036 (PR #1075).

New features

• Significant search improvements – #805
• Branching and merging visualization – #1043
• Composer workflows – #1037

Other significant changes

• MobX introduced as a state management library for the React frontend – #1091
• Frontend generally reviewed and cleaned up (React component structure, code style, etc.) – #1083

Upgrade notes

To upgrade from 3.0 and earlier, please do a full re-activation. The recommended procedure is:

1. Put the site in a maintenance mode.
2. Deactivate VersionPress (just deactivate, do not uninstall).
3. Delete the contents of wp-content/plugins/versionpress and extract the current version there.
4. Activate & initialize the plugin again.
5. Disable maintenance mode.

System requirements

General system requirements:

• PHP 5.6.0 or later
• WordPress 4.4 or later
• Git 1.9 or later
• proc_open() enabled

System requirements for sync / multi-environment workflows:

• Custom server or VPS is recommended.

❗️ UPDATE: Please note that this release is from July 2016. The newest beta release is 4.0-beta2 but importantly, VersionPress is not actively developed so don't use any of the versions in production please. #1481 explains more.

More reliable REST API response handling. Released on 22 July 2016. Release blog post.

• Download versionpress-3.0.2.zip
• Installation instructions

Note: this is an Early Access release. These warnings and limitations apply.

New in 3.0.2

This release fixes 3 issues via 2 pull requests. Main changes are:

• Malformed REST API responses, e.g. because of PHP notices, are handled better by the client-side, JavaScript code. #1074
• Fixed "Click here to show [uncommitted] changes" bug introduced in 3.0.1. #1073

Update notes

The best way to update from 3.0 or above is to run this WP-CLI command:

wp vp update /path/to/versionpress-3.0.2.zip

If you're updating from an older release or cannot use WP-CLI, full reactivation is required, see Update.

System requirements

General system requirements:

• PHP 5.6.0 or later
• WordPress 4.4 or later
• Git 1.9 or later
• proc_open() enabled

System requirements for sync / multi-environment workflows:

• Custom server or VPS is recommended.

Bug fixes and reliability improvements. Released on 30 May 2016. Release blog post.

• Download versionpress-3.0.1.zip
• Installation instructions

Note: this is an Early Access release. These warnings and limitations apply.

New in 3.0.1

This release fixes 6 bugs and brings 3 other improvements. No issue has been identified as critical.

Update notes

The best way to update from 3.0 is to run this WP-CLI command:

wp vp update /path/to/versionpress-3.0.1.zip

If you're updating from an older release or cannot use WP-CLI, full reactivation is required, see Update.

System requirements

General system requirements:

• PHP 5.6.0 or later
• WordPress 4.4 or later
• Git 1.9 or later
• proc_open() enabled

System requirements for sync / multi-environment workflows:

• Custom server or VPS is recommended.

Major usability and reliability release. See release notes for full list of changes.

Please download versionpress-3.0.zip, not the source code ZIP. Installation instructions.

This release accompanies the open-source announcement.

Full release with blog post, release notes etc. will be available in about a week or two, in the meantime, please refer to the release notes draft.