Signet 1.1.0

When I started testing my extensions against the first beta of Retraceur 4.0.0, I wasn’t expecting to release a new version of Signet. However, those tests quickly uncovered an issue that prevented the block from working correctly in this new environment.

As a result, Signet 1.1.0 is primarily a maintenance release. But, as is often the case when you take the time to investigate a problem all the way to its root cause, it also led to an improvement in Retraceur itself.

An issue uncovered by Retraceur 4.0.0-beta1

Retraceur 4.0.0 introduces several internal changes that pave the way for future features.

While testing the potential impact of the first Retraceur 4.0.0 beta on Signet, I noticed that bookmark blocks inserted into posts before this update would consistently trigger an error in the block editor. Although clicking the block’s Attempt Block Recovery button immediately fixed the issue, I wanted to understand what was actually happening and implement a proper long-term fix.

After several rounds of investigation, I identified the root cause and implemented the necessary changes in Signet. If you’re interested in the technical details, you can follow the entire investigation in Signet issue #5.

This fix restores full compatibility with Retraceur 4.0.0 while remaining compatible with previous Retraceur releases.

An older issue brought to light

As I continued my testing, I discovered that Signet was never able to retrieve the description of the posts published on this blog.

Since version 3.0.0, Retraceur has included its own OpenGraph API, providing standardized metadata for applications that generate rich previews of web pages.

Whenever this API is available, Signet naturally relies on it and, more specifically, on the <meta property="og:description"> tag to retrieve the page description. My investigation revealed that a bug inherited from WordPress^® prevented Retraceur’s REST API from exposing this information correctly.

The fix implemented in Retraceur now allows the page description to be retrieved as expected. This benefits not only Signet, but also any application relying on Retraceur’s REST API to access OpenGraph metadata.

The entire analysis and the corresponding fix are documented in Retraceur issue #232.

Install Signet

Once the signet.zip Block archive is downloaded from the asset section of the 1.1.0 GitHub release note, you’ll just need to upload it on your Website from your Block Administration screen.

Why these tests matter

This work is a good illustration of why regularly testing Plugins and Blocks against Retraceur pre-releases is so valuable.

On the one hand, it allows Plugin and Block developers to verify that their code remains compatible with changes introduced by the framework it depends on.

On the other hand, an issue observed in a Plugin is not always caused by the Plugin itself. Sometimes it reveals a deeper problem within Retraceur. In those cases, resolving the issue depends not only on the Plugin developer but also on the maintainers of the core project.

This is one of the greatest strengths of an open source project: anyone can report an issue, investigate its root cause, and contribute a fix. Beyond solving a local problem, this process helps improve the overall quality and robustness of Retraceur.

As always, bug reports, suggestions, and contributions are welcome on the project’s GitHub repositories.

Featured photo credits : Angèle Kamp sur Unsplash

Note: The WordPress^® trademark is the intellectual property of the WordPress Foundation. The use of the WordPress^® name in this article is for identification purposes only and does not imply endorsement by the WordPress Foundation.