Weave Code
Page Module Laravel Package
idavoll/page-module
A Laravel package for adding CMS-style pages to your application, with page management, routing, and Blade rendering. It integrates with Eloquent and Laravel conventions to help you create, organize, and serve editable content pages.
[READ ONLY] see AsgardCMS/Platform
Frequently asked questions about Page Module
- What is idavoll/page-module used for?
- It adds CMS-style pages to an AsgardCMS application, including page management, slug-based routing, and Blade rendering. It is a module of AsgardCMS rather than a standalone Laravel package. Use it only when you are already running that CMS and need editable content pages.
- Can I install idavoll/page-module in a fresh Laravel application?
- No, not cleanly. It depends on the AsgardCMS runtime, including its module loader, admin menu registry, Sentinel ACL, repository and presenter conventions, and translation tables. A fresh Laravel app would have to adopt that CMS kernel, which is a much larger commitment than adding a pages package.
- Which Laravel and PHP versions does idavoll/page-module support?
- The package resolves into the Laravel 5.x and PHP 7.x era because it is tied to a dormant AsgardCMS upstream. It is not a Laravel 10, 11, or 12 package. Treat any version pins in composer.json as legacy and verify them before planning an install.
- Is idavoll/page-module compatible with Laravel 11?
- No. The dependency chain is anchored to Laravel 5.x-era code and an inactive CMS upstream, so Laravel 11 is not a supported target. Running it on modern Laravel would require a port rather than a normal Composer upgrade. For a new Laravel 11 app, model pages directly instead.
- What license does idavoll/page-module use?
- Composer reports the license as NOASSERTION, which means there is no clear automated license declaration. That is a legal blocker until a human reads the LICENSE file and confirms the grant. Do not assume MIT or any redistribution rights without review.
- How do I install and configure idavoll/page-module?
- It is intended to be installed inside an existing AsgardCMS installation as part of that module ecosystem, not through a typical standalone Laravel package workflow. Configuration follows AsgardCMS module registration, permissions, and translation patterns. The provided README excerpt does not document a standalone install path, so rely on the AsgardCMS platform docs for your legacy version.
- Can I use idavoll/page-module in production?
- Only in a legacy AsgardCMS deployment that you must keep alive, and only with strong controls. Pin PHP, Laravel, Sentinel, and the module loader atomically, commit composer.lock, run in a container, and disable automated dependency updates. The main risks are unpatched Laravel 5.x security issues and silent module-loader failures.
- How do I test idavoll/page-module?
- There is no meaningful modern test path because the package depends on the AsgardCMS kernel and has no ecosystem evidence of third-party fixes. For a legacy install, test inside the exact pinned container stack and cover the page CRUD screen, slug routing, permissions, and translations. For a new build, testing the package is the wrong goal; test your own pages model and routing instead.
- What should I use instead of idavoll/page-module?
- For a greenfield Laravel app, create a pages table with translatable title, slug, and body fields and add a Filament or Nova resource for authoring. That is typically one to two days of work and removes the EOL framework, unknown license, and CMS coupling. If you need a CMS, choose a maintained Laravel CMS rather than reviving AsgardCMS.
- How do I migrate away from idavoll/page-module?
- Treat it as a content extraction project: snapshot the pages and page_translations tables, map one row per page per locale, and reimplement the frontend route with a slug resolver. Preserve slugs verbatim and keep a redirect map because that is the part with SEO consequences. Do not shim the AsgardCMS repository interface into a modern app; reimplement the small public surface directly.
Weaver
How can I help you explore Laravel packages today?