Weave Code
Media Pagepart Bundle Laravel Package
kunstmaan/media-pagepart-bundle
Provides a media page part for Kunstmaan CMS, letting editors insert images, video and audio into pages via the standard page part workflow. Ships admin form types and Twig templates for consistent front-end rendering.
KunstmaanMediaPagePartBundle adds media-focused page parts to the Kunstmaan CMS, letting editors drop images, videos, and slideshows into any page straight from the page editor. It builds on KunstmaanMediaBundle, so assets are reused from a central media library instead of being duplicated per page.
- Image page part with caption and link support
- Video page part for embedded media
- Slideshow page part for rotating galleries
- Seamless media picker integration with KunstmaanMediaBundle
- Overridable Twig templates for full front-end control
Requires Symfony and the Kunstmaan bundle stack.
Frequently asked questions about Media Pagepart Bundle
- Can I use kunstmaan/media-pagepart-bundle in a Laravel application?
- No, it is a Symfony bundle built for the Kunstmaan CMS ecosystem, not a Laravel package. It depends on KunstmaanPagePartBundle and KunstmaanMediaBundle, so direct Composer installation in Laravel would pull in legacy Symfony and Kunstmaan dependencies and likely cause framework conflicts. Treat it as a design reference only, or isolate it in a legacy Symfony service if you must keep it.
- What does kunstmaan/media-pagepart-bundle actually do?
- It adds a media page part to Kunstmaan CMS so editors can select images or other media from the media library and insert them directly into page content through the admin interface. The bundle keeps KunstmaanPagePartBundle decoupled from KunstmaanMediaBundle. It is specific to the Kunstmaan CMS and Symfony stack, not a general-purpose Laravel media library.
- How do I install kunstmaan/media-pagepart-bundle?
- In a compatible legacy Symfony and Kunstmaan project you would install it with Composer using kunstmaan/media-pagepart-bundle, then register and configure the bundle according to the Kunstmaan CMS setup. There is no supported modern Laravel installation path. For Laravel, do not install it; build or use a Laravel-native page-part and media component instead.
- Which Laravel versions support kunstmaan/media-pagepart-bundle?
- None are officially supported. The package has a last release date of 2014-05-20 and assumes legacy Symfony and Kunstmaan versions. Modern Laravel 10 and 11 applications on PHP 8.x should expect Composer dependency conflicts and framework incompatibility.
- Is kunstmaan/media-pagepart-bundle maintained or abandoned?
- It is effectively abandoned for modern PHP and Laravel use. The last release was in 2014, it has 13 stars, 0 dependents, and a low score of 0.185. Retaining it would require fork ownership, dependency pinning, and security review.
- What are alternatives to kunstmaan/media-pagepart-bundle for Laravel media page parts?
- Use a maintained Laravel block or page-part package, a Filament or Nova field, or a native Laravel media library integration. Define a small internal page-part and media abstraction so rendering stays separate from media storage. This avoids importing legacy Symfony and Kunstmaan dependencies into Laravel.
- How can I safely test or evaluate kunstmaan/media-pagepart-bundle?
- Evaluate it only in an isolated legacy Symfony and Kunstmaan environment pinned to compatible PHP and Symfony versions. Audit its dependencies and security posture before any use. Do not add it to a Laravel dependency graph; if you need its output, expose legacy content through an API instead.
- What are the production risks of using kunstmaan/media-pagepart-bundle?
- Expect Composer conflicts, framework incompatibility, security vulnerabilities, stale admin or rendering behavior, broken media-bundle assumptions, and storage path issues. Upstream patching is unlikely because the package is unmaintained. A legacy runtime also increases deployment and observability complexity.
- Can I migrate content from Kunstmaan media page parts into Laravel?
- Avoid a direct migration into Laravel. Define an internal page-part and media abstraction, then import media assets and page-part content through a controlled migration process. Map media references behind stable interfaces. If the legacy bundle must remain, isolate it and expose content via API rather than embedding it in Laravel.
- When would kunstmaan/media-pagepart-bundle still make sense?
- Only in an existing Symfony and Kunstmaan CMS estate already pinned to compatible legacy versions. Even then, confirm PHP, Symfony, KunstmaanPagePartBundle, and KunstmaanMediaBundle compatibility first. For Laravel, use it as a conceptual reference for decoupling page parts from media, not as a dependency.
Weaver
How can I help you explore Laravel packages today?