✅Release 2.1.0

Release 2.1.0 was published to the Chrome Web Store on August 26, 2024

Action Required by August 26th: changes to PixieBrix Mod Development

In this release, all mods you’ve built will require a mod id. To simplify the transition, we’ll be automatically updating the mods on your account to have an assigned id.

Here’s what you need to know:

• When 2.1.0 is published on August 26th, we’ll automatically assign an id to each of your saved mods that do not already have an id

• You will lose access to your id-less mods on August 26th if you do not have a username/alias set for your account.

  • To set a username/alias, open the Page Editor and save any mod

• If you want to manually set a mod id for any mods, save/share the mod before August 26th:

  • On the Extension Console Mods Screen, select “Share with Teams” from the 3-dot menu, and enter a mod id

  • In the Page Editor, save the mod and enter a mod id

• Before upgrading your browser extension to 2.1.0, after August 26th you will see duplicate entries in the Mod Screen for activated mods that don’t have an assigned mod id

Have questions/concerns? Email [email protected] or visit the Slack Community.

🎨 User Experience

• Automatically convert all remaining standalone mod components installed on the Extension to mods (#8989)

🐛 Bug Fixes

• Fixed a bug in the Page Editor where the mod version always showed the latest version instead of the activated version (#9026)

• Fixed the integration validation in the Extension Console when activating a mod -- failing to select a required integration will trigger an error message when clicking "Activate" (#9036)