NG Extension Manager 2.3.72 - Release Notes

[canvrs]

🔧 NG Extension Manager – Patch Notes

✅ Fixed: Invalid Manifest Configuration

We resolved a critical issue where the NG Extension Manager’s manifest.json was invalid. This prevented the extension from loading in Chrome and other Chromium-based browsers.

Root Cause

The error was caused by a missing background.js file that was referenced in the manifest but not included in the source code.

---

⚙️ Manifest & Compatibility Updates

• The manifest has been updated to ensure compatibility with the NGEM Rules Management add-on.
• Several improvements and permissions were added:
  • Enables developers to create more specific and advanced add-ons.
  • ⚠️ Note: Some new permissions may pose higher security risks (e.g., broader access to browser features). Use caution when integrating third-party add-ons.

---

📂 Added: background.js

• The missing background.js file has been added.
• This change ensures:
  • Manifest validation passes.
  • Compatibility with NGEM Rules Management.

---

🐞 Known Issue: Extensions Without Icons

There is a known bug affecting extensions without icons, usually those not installed via the Chrome Web Store.

Description:

NG Extension Manager attempts to load the icon regardless of its existence, resulting in repeated errors. In high-usage scenarios, this can generate thousands of identical error messages within minutes, which may impact performance.

A fix for this issue is planned for an upcoming release.

---

📦 Download

You can download this version from:

• Your in-app NG Extension Manager Updates page
• Or directly on GitHub by downloading the source code from the main repository

  Tip: Click the green Code button, depending on your GitHub theme.

---

Full Changelog: v2.3.71...v2.3.72

---

This discussion was created from the release NG Extension Manager 2.3.72 - Release Notes.