Our first fishing trip was crowned by some great catches. Found anomalies have been corrected in this second beta of Retraceur, which should also give us even more confidence about the stability of the next major version of the software, scheduled for release on September 21.
The challenge has gotten tougher: 2.0.0-beta2 is our opportunity to check that the 1-click Retraceur core upgrade feature is behaving as expected. Note that this opportunity exists when the version currently being beta tested is 2.0.0-beta1.
Checking the 1 click upgrade works as expected
This feature saves time compared to a manual update. Doing the click will download the upgraded version to your site’s /wp-content/upgrade directory and replace all Retraceur files except for most of those in the /wp-content directory. For more details on this feature, please read this documentation.
How to do this check?
If you’re taking the Retraceur 2.0.0 bug fishing campaign mid-stream, start by installing the first beta of that major release.
Next, go to the Upgrades Administration screen on your dashboard, which should look something like the screenshot above.
If the first button, which should be labeled « Update to 2.0.0-beta2« , is missing, it’s probably because you forgot to set the filter hook to test this feature. In this case, please follow the instructions specified in first beta’s post about it in order to make this famous button appear!
If after clicking this button you notice that the upgrade has failed, please report it by sending a detailed anomaly report as much as possible.
Ready to go fishing for bugs, again?
The whole point of pre-releases is to ensure that the software updates work as expected and haven’t caused regressions or generated bugs. This is especially important since Retraceur offers configuration, customization, and extension options that you can use in very different ways: I can’t anticipate them all in my tests!
Contributing to the beta test of this 2.0.0-beta2 is an investment in the stability of your installation and contributes to the stability of all other users. If you’ve chosen to trust Retraceur to power your online publishing hub, I encourage you to fish with me and report any bugs you encounter.
NB: do not test Retraceur on your production website; use a local development site (using MAMP, LAMP, or WAMP, depending on your hardware) or a remote one. If you have forgotten how to install Retraceur since version 1.0.0, please have a look at this documentation resource.
Featured image credits : Dmytro Yarish sur Unsplash
Conversation
Rejoignez la conversation depuis Bluesky