Feature request, plugin management

I’d like to suggest a new feature that would bring CMS Builder up to modern standards for plugin and extension handling — something modeled after Piwigo’s excellent plugin management system.

Currently, installing or updating CMSB plugins involves manual file uploads and version tracking, which can become cumbersome as sites grow or as multiple developers manage different environments. A centralized, in-app plugin management interface would significantly streamline workflows, improve security, and encourage more active plugin development within the community.

Proposed Features

In-App Plugin Browser

• Search, install, and update plugins directly from the CMS Builder admin area.
• Include filters by category, popularity, and last update date.
• Display plugin metadata (author, description, version, changelog, compatibility).

Compatibility and Safety Checks

• Each plugin declares compatible CMSB versions.
• Show clear warnings if a plugin hasn’t been tested or maintained recently.
• Option to stage/disable plugins without uninstalling them.

Automatic Updates and Rollbacks

• One-click updates from within the admin panel.
• Retain a last-known-good version for easy rollback if something breaks.
• Optional update notifications and changelog previews.

Sandboxing and Permissions (Future Phase)

• Define plugin capabilities in a manifest (e.g., database access, file writes, external HTTP calls).
• Allow the admin to review and approve permissions before activation.
• Longer-term: support isolated plugin runtimes or namespaces.

Developer Publishing Interface

• Provide an official plugin repository or registry with submission guidelines.
• Display “verified developer” badges for trusted authors.
• Include GitHub/Bitbucket integration for version syncing and issue tracking

Benefits

• Ease of maintenance: No more manual FTP uploads or version guessing.
• Improved security: Centralized verification and optional signing.
• Community growth: Easier for new developers to share and update plugins.
• Better UX for admins: Transparent updates and safer testing.

Piwigo’s system is a great example of how this can work in practice — it’s lightweight, reliable, and user-friendly. Bringing similar functionality into CMS Builder would modernize plugin management and create a stronger ecosystem around the platform.

Thanks for considering this — happy to help outline technical requirements or testing scenarios if you move forward with it.