- How do I install jeffersongoncalves/filament-knowledge-base in a Laravel app?
- Run composer require jeffersongoncalves/filament-knowledge-base, publish any package config and migrations, and register the plugin in your Filament panel provider. Confirm PHP, Laravel, Filament, and jeffersongoncalves/laravel-knowledge-base ^2.0 constraints in composer before rollout. Test installation in staging with representative private-disk assets and Trix attachments.
- Does filament-knowledge-base support Filament v3, v4, and v5?
- The package overview lists support for Filament v3, v4, and v5, but the 1.3.1 patch release is explicitly a Filament 3 backport. Treat Filament 3 as the documented path for that release and check the installed composer constraints before assuming v4 or v5 compatibility. Teams on older Filament versions should not assume compatibility without verification.
- Does this package require jeffersongoncalves/laravel-knowledge-base?
- Yes, it is designed to work with jeffersongoncalves/laravel-knowledge-base ^2.0. The core package owns article and asset records while this package provides Filament UI, asset-manager thumbnails, and editor attachment behavior. Confirm the exact core version constraint in composer before upgrading.
- How do private-disk knowledge base asset URLs work in this package?
- The package uses the core ArticleAssets::url() signed URL behavior instead of direct disk URLs for private-disk deployments. This improves support for private storage and reduces reader-facing broken-image risk when URLs are refreshed. Validate filesystem configuration and signed URL support in staging before production rollout.
- Do I still need to run storage:link for filament-knowledge-base?
- storage:link is only needed with core versions that link directly to the public disk. Newer core behavior that serves private-disk assets through signed URLs may not require it. Verify the installed laravel-knowledge-base version and test guest and user panel rendering before changing deployment steps.
- How should I upgrade to filament-knowledge-base 1.3.1 safely?
- Treat 1.3.1 as a patch upgrade from prior 1.3.x releases and confirm you are on core ^2.0 and Filament 3 before upgrading. Stage the upgrade with representative private-disk assets and Trix attachments, then test thumbnails, deleted-image omission, expired URL refresh, and UUID/path asset identity. Regression-test any custom code that manipulates asset URLs directly.
- What changed for Trix editor attachments in version 1.3.1?
- The release fixes private visibility for editor file attachments and refreshes expired stored URLs on form load, including Trix attachment data. This reduces broken attachment behavior for private-disk deployments. Test editor behavior carefully if a signed URL can expire mid-session.
- Will existing assets with disk-path identity still resolve after upgrading?
- Asset resolution now recognizes UUIDs in core-served URLs in addition to disk paths. Existing disk-path assets should continue to resolve when asset records are consistent, but custom code that assumed disk-path-only identity should be regression-tested. Check asset records for UUID and path consistency before production rollout.
- Is this package suitable for production knowledge bases and FAQs?
- It is suitable for Laravel applications using Filament that need admin, user, and guest knowledge base panels with categories, articles, and help docs. The 1.3.1 patch is low-risk feature-wise but has moderate behavioral risk around private storage, signed URL lifetimes, and editor refresh behavior. Test those areas in staging and monitor for broken images after deployment.
- What alternatives or limitations should I consider before using this package?
- This package is tightly coupled to Filament and the laravel-knowledge-base core, so it may not fit applications that do not use Filament. If you need a standalone knowledge base or custom CMS workflows, compare standalone Laravel packages or a custom implementation. Also confirm PHP, Laravel, Filament, and core version constraints and evaluate maintenance activity before adoption.