WP Manifestindependent plugin directory
manifest / events / wp-plugin-municipio-event-extensions

Municipio Event Extensions

Server-rendered event modules with progressive enhancement for Municipio 6

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/municipio-se/wp-plugin-municipio-event-extensions/archive/refs/heads/main.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.

Server-rendered event modules for Municipio 6. Cards, filters and pagination work without JavaScript; JavaScript adds in-place updates and mobile carousel controls. The existing server-rendered list remains available. Import and storage remain with Event Manager Integration.

Activate alongside Event Manager Integration and Quality Extensions. Deactivating restores the existing views without a data migration.

Version 0.1.1 has been tested with Municipio 6.43.3, Event Manager Integration 3.1.4, WordPress 6.9.10 and PHP 8.3 on Nora and migrated Höör installations. Municipio 7 is not supported. PHP-rendered archives and details omit the legacy frontend bundle. Submission forms, older maps and widgets retain it where needed. This package does not remove React or jQuery dependencies from the whole site.

Install municipio/wp-plugin-municipio-event-extensions through a Composer VCS repository pointing to this GitHub repository, restricted with only to that package. Versions follow immutable SemVer tags and matching GitHub releases; Packagist registration is not required. Commit the consumer's Composer lockfile.

Verify with composer validate --strict, composer format, composer lint, node --test tests/events.test.mjs and, on a local WordPress fixture, wp eval-file tests/integration.php MODULE_ID. The integration check requires current events and compares the adapter to the existing REST endpoint; its taxonomy fixture must match the tested module's configured selection.