Pro publishes one file:
That creates config/commentify-pro.php. Values under core are copied onto config('commentify') at boot so the free package keeps reading the keys it already knows.
Do not also keep a published config/commentify.php unless you installed core first and have not merged yet. If that file exists, the overlay is skipped and core has no effect until you delete it.
core
Mirrors the free package’s config/commentify.php.
GET /commentify/api/v1/ui exposes the flags and translated labels to the SDKs, so toggling sorting or reporting here changes Livewire, React, and Vue together.
Theme and CSS
- Tailwind v4: include
@custom-variant dark (&:where(.dark, .dark *)); in your CSS (Livewire Flux already does).
- Bootstrap 5: dark mode uses
data-bs-theme="dark".
- Publish views only if you must customize them. Published views override package views and will not pick up later markup changes automatically.
See Usage. Empty by default until the installer or you fill it.
api
guest_comments => false keeps guests on Livewire but locks the JSON API. Pair guard and middleware or every browser write is an unauthenticated 401. Full detail: Authentication and API.
per_page on list endpoints is capped at 50. Cursor pagination (?cursor=) is available for newest and oldest sorts.
spam
Worst verdict wins: deny > review > allow. See Spam pipeline.
guests
notifications
See Notifications.
See Image uploads. If bucket is set, Pro registers a commentify-media disk cloned from filesystems.disks.{disk} with that bucket.
realtime
See Realtime.
webhooks
See Webhooks.
badges
See Badges and pins.
toxicity
Add 'toxicity' to spam.checkers as well. See AI toxicity.
gdpr
See GDPR.
Environment variables
The free Filament Commentify Settings page can toggle many core flags without editing the file. Guest commenting (allow_guests) stays in config.