PHPackages weblizards/tag-management-bundle - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. weblizards/tag-management-bundle ActivePimcore-bundle[Utility & Helpers](/categories/utility) weblizards/tag-management-bundle ================================ Re-introduces the 'Tag and Snippet Management' feature which was deprecated in Pimcore 6.x and removed in Pimcore 10. v1.2.0(1mo ago)2404↓36.7%GPL-3.0-or-laterPHP Since Feb 20Pushed 1mo agoCompare [ Source](https://github.com/weblizards-gmbh/tag-management-bundle)[ Packagist](https://packagist.org/packages/weblizards/tag-management-bundle)[ RSS](/packages/weblizards-tag-management-bundle/feed)WikiDiscussions main Synced 2d ago READMEChangelog (3)Dependencies (7)Versions (9)Used By (0) Tag Management Bundle for Pimcore 11 ==================================== [](#tag-management-bundle-for-pimcore-11) This bundle restores the "Tag & Snippet Management" area that was available in older Pimcore versions and removed later on. For Pimcore 10 please use the [pimcore 10 branch](https://github.com/weblizards-gmbh/tag-management-bundle/tree/Pimcore-10.x) Features -------- [](#features) The bundle allows you to inject HTML tags and snippets into websites based on different rules: - **URL patterns**: output only on matching requests - **HTTP methods**: restrict output to `GET`, `POST`, and similar methods - **Site checks**: assign tags to specific Pimcore sites - **Parameters**: check query or request parameters - **Positioning**: insert content at the beginning or end of `` or ``, or into CSS-selected target elements - **Scheduling**: define an expiry date per item - **Editmode control**: enable or disable items separately for Pimcore editmode - **Dynamic parameters**: no more fixed 5-field limitation in the admin UI - **Rename in admin**: tags can be renamed safely in the backend Requirements ------------ [](#requirements) - PHP `>= 8.2` - Pimcore `^11.0` Installation ------------ [](#installation) 1. Require the bundle via Composer: ``` composer require weblizards/tag-management-bundle ``` 2. Enable the bundle: ``` bin/console pimcore:bundle:enable WeblizardsTagManagementBundle ``` 3. Run the bundle migrations: ``` bin/console doctrine:migrations:migrate --prefix="Weblizards\\TagManagementBundle" ``` 4. If present, migrate legacy configuration from `var/config/tag-manager.php` into the Pimcore `SettingsStore`: ``` bin/console weblizards:tag-management:migrate-config-storage --dry-run bin/console weblizards:tag-management:migrate-config-storage ``` Optionally remove the legacy file after a successful migration: ``` bin/console weblizards:tag-management:migrate-config-storage --cleanup-legacy-file ``` Storage ------- [](#storage) Current versions persist tag configurations in the Pimcore `SettingsStore` using a bundle-specific scope. This is the intended Pimcore 11-compatible persistence path. For existing installations, a read-only fallback to the legacy file `var/config/tag-manager.php` remains in place during rollout. New or updated entries are persisted in the `SettingsStore`. Commands -------- [](#commands) ### Disable expired items [](#disable-expired-items) To persistently disable expired items: ``` bin/console weblizards:tag-management:disable-expired-items ``` This is suitable for a regular cron job. ### Normalize legacy date values [](#normalize-legacy-date-values) If existing data still contains legacy epoch timestamps or inconsistent date formats: ``` bin/console weblizards:tag-management:migrate-item-dates ``` ### Migrate legacy storage into SettingsStore [](#migrate-legacy-storage-into-settingsstore) To migrate the old PHP array file into the `SettingsStore`: ``` bin/console weblizards:tag-management:migrate-config-storage --dry-run bin/console weblizards:tag-management:migrate-config-storage ``` Useful options: - `--dry-run`: show what would be migrated without writing anything - `--overwrite`: overwrite existing SettingsStore entries - `--cleanup-legacy-file`: remove the old `tag-manager.php` after a successful migration Admin Routing ------------- [](#admin-routing) Inside the Pimcore admin, the bundle prefers `Routing.generate(...)` when a compatible global routing base is available in the current setup. For its own admin endpoints, it also provides an internal fallback to stable bundle paths under `/admin/tag-management/...`. This keeps the bundle functional even without a hard dependency on a specific JavaScript routing setup. Development and Testing ----------------------- [](#development-and-testing) The repository contains simple PHP-based regression tests and helper configuration for local development. Additional details can be found in [docs/development\_testing.md](docs/development_testing.md). Upgrade Notes ------------- [](#upgrade-notes) When upgrading from older bundle versions, these points are relevant: - Tag configurations are now persisted via the `SettingsStore`. - Existing configurations from `var/config/tag-manager.php` should be migrated using the provided migration command. - Legacy key names and older request payloads are still read tolerantly during the transition. - Expiry dates are normalized internally to a consistent ISO-8601 UTC format. License ------- [](#license) This bundle is licensed under [GPL-3.0-or-later](LICENSE.md). --- Developed by [pimcore](https://pimcore.com/) and further maintained by [Weblizards GmbH](https://www.weblizards.de). ### Health Score 42 — FairBetter than 88% of packages Maintenance91 Actively maintained with recent releases Popularity20 Limited adoption so far Community6 Small or concentrated contributor base Maturity40 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~18 days Total 6 Last Release 43d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/965bba97bac6bc4093543962fc1b38fee8b46438cda15afe98bb1ce96a3326f4?d=identicon)[ThomasKeil](/maintainers/ThomasKeil) --- Top Contributors [![ThomasKeil](https://avatars.githubusercontent.com/u/1055202?v=4)](https://github.com/ThomasKeil "ThomasKeil (40 commits)") ### Embed Badge ![Health badge](/badges/weblizards-tag-management-bundle/health.svg) ``` [![Health](https://phpackages.com/badges/weblizards-tag-management-bundle/health.svg)](https://phpackages.com/packages/weblizards-tag-management-bundle) ``` ### Alternatives [craftcms/cms Craft CMS 3.6k3.6M3.1k](/packages/craftcms-cms)[pimcore/pimcore Content & Product Management Framework (CMS/PIM/E-Commerce) 3.8k3.8M507](/packages/pimcore-pimcore)[blackfire/player A powerful web crawler and web scraper with Blackfire support 49617.1k](/packages/blackfire-player)[pimcore/data-importer Adds a comprehensive import functionality to Pimcore Datahub 46855.5k5](/packages/pimcore-data-importer)[drupal/core-dev require-dev dependencies from drupal/drupal; use in addition to drupal/core-recommended to run tests from drupal/core. 2022.6M344](/packages/drupal-core-dev)[open-dxp/opendxp Content & Product Management Framework (CMS/PIM) 9421.6k61](/packages/open-dxp-opendxp) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)