Weave Code
Filagora Messages Laravel Package
filagora/filagora-messages
A Laravel and Filament package for adding private messaging to your application. It provides conversations, message threads, and a clean UI for sending and receiving messages between users, with straightforward installation and integration into existing Filament panels.
Private conversations between members, with folders, read state and trash, for Filagora.
Frequently asked questions about Filagora Messages
- What is filagora/filagora-messages used for?
- It is a Laravel package for adding private messaging to Filagora applications. It provides Eloquent-backed conversations and message threads, configurable migrations, and a clean Filament UI for sending and receiving messages between users. It is designed to be extended for custom messaging workflows.
- How do I install filagora/filagora-messages in a Laravel application?
- Install the package with Composer, then publish and run its core migrations. Smoke-test basic conversations and messages before adding optional features. If you need attachments, set up filagora/filagora-forums first, run the forums migrations, and then run the package attachments migration or the link command.
- What Laravel, PHP, and database versions does filagora/filagora-messages support?
- The release notes provided do not state exact Laravel, PHP, or database version constraints. Check the package composer.json and repository documentation for the supported matrix before adopting it. Because the package relies on Eloquent, migrations, and Artisan commands, test it against your target Laravel and database versions.
- Do I need filagora/filagora-forums to use filagora/filagora-messages?
- No. Core private messaging works without forums; the forums dependency is optional and only relevant when you want attachments. If attachments are in scope, require filagora/filagora-forums ^0.6 and plan the migration order carefully. Teams not using forums should treat attachments as an optional later phase.
- How do I add attachments to private messages?
- Install and migrate filagora/filagora-forums ^0.6 before running the package attachments migration. The package migration must run after the forums attachments table exists, or you can use filagora:messages:link-attachments to add the columns later. If an existing forums snapshot already has the extension columns, run filagora:adopt instead.
- Why does migration order matter for message attachments?
- Attachment metadata lives in the forums attachments table, including private message and conversation references. The package migration must therefore run after that table exists, or the link command must add the columns afterward. Getting the order wrong can cause missing-table or duplicate-column states, so test against a copy of your production schema.
- What does filagora:messages:link-attachments do?
- It is the fallback path for linking attachments when the package migration cannot run in the ideal order. The design is intended to recover from half-done states, but the provided notes do not fully document production backfill behavior. Back up the database and test the command on a production-like schema before using it.
- How does MessageAttachmentAccess control attachment access?
- MessageAttachmentAccess is the package component responsible for attachment authorization, so access correctness depends on how it is wired into your application. The notes do not specify exact policy or middleware hooks, so review the implementation and connect it to your app policies. Test send, reply, claim, and delete flows with multiple users and roles.
- What happens to orphaned attachments when a message is deleted?
- The package clears foreign keys rather than cascading deletes, which preserves attachment records. That means unclaimed or orphaned attachments need an explicit cleanup and retention policy. Plan storage lifecycle handling before production and test deletion behavior carefully.
- How should I test and roll out filagora/filagora-messages in production?
- Test on a copy of the production schema, especially if filagora/filagora-forums was customized or partially migrated. Verify conversations, replies, attachment claiming, access control, deletion behavior, and recovery from half-done migration states. Document an operational runbook covering migration order, rollback, and orphan cleanup before rollout.
Weaver
How can I help you explore Laravel packages today?