Warp
← Warp Documents questions

Warp Documents changelog

Update with composer update qalainau/filament-warp-documents, then run php artisan filament:assets.

1.1.0 Nov 23, 2026

Added

  • Replace or remove the standard resources and pages: documentResource(), documentTypeResource(), folderResource(), myWorkPage(), masterListPage() and readMatrixPage() (each with a getXxx()). Pass false to remove, or a subclass to replace; the URL and route name stay the same, and the authenticated file, rendition and print routes are unchanged.

Fixed

  • Japanese overdue cell in the read matrix: an overdue cell read 期限切れ(2025年10月28日 まで) with a half-width space and an odd "until". It now reads 期限切れ(期限:2025年10月28日), like the other languages.

  • The current version could go missing on MariaDB 11: with two or more approved versions of the same document, eager loading the current version sometimes returned nothing on MariaDB 11, so a reading task disappeared from My document tasks (and other lists that load many documents at once) now and then. The current version is now chosen without the grouped join that MariaDB's optimizer got wrong; it is the same version as before (the newest approved one in effect today, the higher ID on the same day).

  • Printing a controlled copy now also requires your policy's update (like collecting one); someone your policy allows only to view a document no longer sees Print controlled copy.

  • The master list and the read matrix now ask your policy's viewAny (the page) and view (each document), and My document tasks leaves out documents your policy hides.

  • "Today" follows the panel's time zone: the current revision, the effective date, review-overdue and expired flags, reading and review reminders, the master list and CSV file names, and the printed-on date in the stamp were decided with the app's UTC date. With the panel set to e.g. America/New_York, they flipped to the next day during the UTC night. They now use the panel's time zone (FilamentTimezone).

  • Page access rules on a replaced page: when the app replaced a standard page or resource with a subclass (xxxPage()/xxxResource()), canAccessUsing() and canWriteUsing() received the subclass as $page, so a rule such as $page !== Projects::class did not match and a page the app had closed still opened (HTTP 200). $page is now always the plugin's own standard class, whatever the app swaps in. A rule that compared $page with the app's own subclass must compare with the standard class instead.

1.0.4 Nov 20, 2026

Fixed

  • Console error warpDocuments is not defined: on pages where Livewire re-renders a document page inside another Alpine component, the browser console could show warpDocuments is not defined before the component's script had arrived. Empty components are now registered up front, and the real ones replace them as soon as they load. No visible change.

1.0.3 Nov 19, 2026

Fixed

  • Opening or downloading the file (or the PDF rendition) of a version whose file is no longer on the disk answered a server error (500). It now answers "Not found" (404), and no download is recorded.

1.0.2 Nov 18, 2026

Security

  • The related documents shown by RelatedDocuments, the rows of DocumentsRelationManager, and the documents you can link there now also ask the view ability of your own document policy, in addition to the plugin's own reader rules. A document your policy keeps from a person is no longer listed for them, no longer offered when linking, and cannot be linked by sending its id to the Link action directly. Without a policy nothing changes. The list of documents you can link still shows up to 50 matches, even when many of the first ones are refused by your policy.

1.0.1 Nov 18, 2026

Security

  • A person in one team could read the name of anyone in another team. The document page and My document tasks had a public Livewire method userName($id) that the browser could call with any user id, and WarpDocuments::userName() did not look at the team. The method is no longer callable from the browser, and in a panel with Filament tenancy a name is shown only for people who can enter the current team (canAccessTenant()); anyone else shows as blank. Panels without tenancy are unchanged.
  • The same fix closes pageHtml() and fileUrl() on the document page and fileUrl() on Compare revisions: the browser could call them with the id of any revision (Livewire looks the model up from the id), and pageHtml() returned the content of a revision of another document, including a draft the person may not read. They are no longer callable from the browser (your own views that extend these pages can still use them from Blade).
  • “Mark as reviewed” now needs the update ability of your own document policy as well as being the owner or a manager. An owner whom your policy keeps read-only no longer sees the button, and calling the action directly (or Lifecycle::markReviewed()) is refused, so reviewed_at no longer changes.
  • Every other action that changes a document — check out, check in (save draft), cancel check-out, submit, withdraw, make obsolete, delete, recall a controlled copy, remind readers, add missing readers — now also needs the update ability of your own document policy, in addition to being the owner or a manager. For an owner your policy keeps read-only, the buttons are hidden and calling them directly is refused. Approve, send back, acknowledge and print a controlled copy are unchanged: they depend on being an approver or a reader, not on editing the document.

Fixed

  • Working out who may read a restricted document (on the document page's reader tab, for instance) no longer lazy-loads the document type when it was not loaded yet.
  • The documents list no longer throws a lazy-loading error (500) in apps that call Model::preventLazyLoading() when a document sits in a nested folder: the folder path is now built without lazy-loading the parent folders.
  • Filament's global search no longer throws a lazy-loading error (500) in apps that call Model::preventLazyLoading() when two or more documents match: the document type is now loaded together with the results.
  • My document work ("to read" and "copies to recall" tabs) no longer loads each revision's document and type one by one, which raised an error in apps that call Model::preventLazyLoading() or Model::shouldBeStrict().

1.0.0 Nov 16, 2026

Added

  • First release of Warp Documents: document control for Filament v5 panels.
  • Documents with a number, type, folder and owner, kept as revisions. A revision is a file (PDF, Word, Excel, images or anything else) or a page written in the panel. A new revision is a draft that only its author and approvers see; the current revision stays in use until the new one is approved.
  • Check-out and check-in, so two people do not revise the same document at once.
  • Built-in approval: approvers by person or group, one after another or all at once, send back and resubmit. Nobody approves their own revision. Optional password signatures (->signatures()).
  • Approval through Warp Flow (->flowApprovals('documents') with ApprovableVersion), when Warp Flow is installed. Without Warp Flow the built-in approval is used.
  • Effective dates, and a SUPERSEDED or OBSOLETE watermark on old revisions. Documents can be made obsolete.
  • Readers (everyone, groups or people) confirm “I have read and understood” each new revision; minor corrections need no new confirmation. Due dates, progress and reminders. An optional comprehension check asks a few multiple-choice questions before confirming (Lifecycle::acknowledge() takes the answers).
  • Periodic reviews from the document type, expiry dates for certificates and licences, and a daily warp-documents:remind command (->reminders()).
  • Redline compare: pages show removed words struck through and added words underlined; files side by side with their details.
  • Controlled copies: “Print controlled copy” stamps the PDF with its copy number, holder, printer and date and keeps a register. When a new revision takes effect, the old copies are listed for collection. ->copyCheck() adds a QR code that opens a public page saying whether that paper is still current.
  • Word, Excel and PowerPoint files shown as PDF (->convertToPdf() with LibreOfficeConverter, GotenbergConverter or your own closure, optionally on a queue).
  • Search inside files (->fullTextSearch()): find a document by a word that is only in its Word, Excel, PowerPoint, OpenDocument, text, RTF or PDF file, on any of the four databases. php artisan warp-documents:process-files processes files that are already stored.
  • Master list, exportable to Excel and printable, and a read matrix of people × documents (who has read the current revision, who has not, who is overdue) with CSV and Excel export. Domain\ReadMatrix::build() gives the same from code.
  • Import the documents you already use from a register (Excel or CSV) and a ZIP, or by dropping many files, with a check of every row before anything is saved (->imports(), Lifecycle::import()).
  • Links to your own records: HasDocuments on a model and DocumentsRelationManager show the current revision of each linked document, listing only documents the person may see.
  • My document tasks page and DocumentTasksWidget for what is waiting for the signed-in person.
  • Permissions: who may see each document, canManageUsing(), canCreateUsing(), canImportUsing(), canViewReadMatrixUsing(), your app's model policies, and canAccessUsing() / canWriteUsing() to decide per page from your app's roles.
  • Append-only audit trail of every change, approval, confirmation and printed copy, and events for your own code.
  • Filament multi-tenancy, and English, Japanese, German, French, Spanish, Italian, Brazilian Portuguese, Korean and Simplified and Traditional Chinese.

Filament + AI coding tips, by email

How to fit Warp plugins into your own app and pair them with Claude Code or Cursor: prompts that work, mistakes AI makes, real examples. Once or twice a month. Unsubscribe anytime.

Ask us anything about Warp

No email address or sign-up needed.

We read every question and answer here on the site, usually within a day. Others see your question after we have checked it.

What's stopping you from using Warp's plugins?

One question. We read every answer, and it decides what we build next. It is not shown on the site.

What's stopping you from using Warp's plugins?