Weave Code
Pn Press Laravel Package
pnscripts/pn-press
PN Press is a lightweight Laravel/PHP package for managing press releases and publication content. It offers straightforward configuration and integration, making it easy to add press-style posts and content handling to your application.
PN Scripts Press: blog CMS built with Laravel and Filament, by PN Scripts
Frequently asked questions about Pn Press
- How do I install pnscripts/pn-press in a Laravel application?
- Install the package via Composer and run the documented Artisan and migration steps from the README. PN Press follows Laravel conventions such as Composer distribution, Artisan commands, and package migrations. It is built with Laravel and Filament, so confirm those dependencies are available in your application. Check the README for the exact install sequence before running it in production.
- Does PN Press support multilingual pages, posts, and menus?
- Yes, the technical evaluation describes PN Press as a Laravel CMS with multilingual pages, posts, categories, and menus. Version 1.1 includes a language migration and adds a rollback guard when multilingual content exists. Test language operations and rollback behavior against representative data in staging before using them in production.
- Which Laravel and PHP versions does pnscripts/pn-press require?
- The package requires PHP 8.4 or newer according to the evaluation, which is a relatively aggressive runtime requirement. The supported Laravel and database versions should be confirmed in the README and Composer constraints before installing. Validate PHP 8.4 availability in local, CI, and production environments.
- How do I create the first admin account in PN Press?
- Use the press:admin Artisan command, which removes the need to rely on demo seed data for initial admin setup. The command is interactive and prompts for the password without displaying it. It can create a new admin and can also assign a role to an existing user. This provides a supported bootstrap path for installations that do not use demo fixtures.
- Can press:admin run non-interactively for CI or automated provisioning?
- The evaluation states that press:admin is interactive by design, with a prompted password that is never displayed. It is not confirmed whether a non-interactive mode exists for CI or provisioning workflows. Treat automated admin creation as needing validation and check the command options in the README. Human-run admin creation is the documented safe path based on the available assessment.
- What happens if I roll back the 1.1 language migration when multilingual content exists?
- PN Press includes a rollback guard for the 1.1 language migration, particularly on MySQL where partial failure previously risked leaving the schema broken. The new behavior refuses the rollback when multilingual content exists instead of proceeding with a half-applied change. Test in staging that the refusal occurs before any schema changes take effect. The supported procedure for intentionally removing a language after content exists is not documented in the assessment.
- Are PN Press demo seeds safe to run in production?
- The evaluation notes that press:admin removes the need to rely on demo fixtures for admin bootstrap. It is not explicitly confirmed whether demo seeds are guarded or excluded automatically in production. Review the seeder code and README before running seeds against production data. Prefer the supported press:admin command instead of demo seed data for production setup.
- How does role-based admin access work in PN Press?
- PN Press provides role-based admin access alongside its Laravel and Filament CMS features. The press:admin command can assign a role to an existing user as well as create a new admin. The evaluation asks whether the role model uses fixed roles or extensible permissions, so confirm the permission model in the documentation. Test role assignments in staging before relying on them in production.
- Does PN Press support MySQL, and are there database-specific migration risks?
- The evaluation specifically calls out MySQL migration behavior, including a prior risk of partial failure during the 1.1 language migration rollback. The new rollback guard improves safety, but cross-database parity should be confirmed for your target database. Test migrations and rollbacks against a production-like MySQL schema with multilingual content present. Check the README for the documented database support matrix.
- What is the upgrade path from pn-press 1.1.0 to 1.1.1?
- Treat 1.1.1 as a patch upgrade from 1.1.0 but validate it as an operational change because rollback behavior and admin bootstrap changed. Update Composer constraints, back up staging or production databases and media, then run migrations in staging against production-like data. Verify press:admin for both creating an admin and assigning a role, and test rollback refusal with multilingual content. Roll to production during a controlled window after updating deployment runbooks.
Weaver
How can I help you explore Laravel packages today?