Warp
← Warp Markup questions

Warp Markup changelog

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

1.6.1 Nov 20, 2026

Fixed

  • Console error warpMarkup is not defined: on pages where Livewire re-renders a Markup drawing page inside another Alpine component, the browser console could show warpMarkup 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.6.0 Nov 19, 2026

Added

  • MarkupImage draws each letter with the first font that has it: the main font, then the bundled font, then fallback fonts. Without any setting it finds CJK fonts installed on the server (for example Noto Sans CJK from apt install fonts-noto-cjk, the same package the server PDFs of the findings report use), so Japanese, Chinese and Korean notes, text and stamps are drawn — also mixed in one note. Set the fallback fonts yourself with MarkupImage::fallbackFonts([...]) or the fallbackFonts option ([] for none).

Fixed

  • MarkupImage drew Japanese, Chinese and Korean letters as boxes without saying anything. A letter that no font has, a font PHP's GD cannot read (such as Hiragino Sans on macOS) and a variable font (drawn Thin) now each write a warning to the Laravel log that says how to fix it.
  • README: .ttc font collections can be used (their first font); the markups in the marked-up PDF are a picture over each page, so their text cannot be searched.

1.5.0 Nov 15, 2026

Added

  • A page made from MarkupPage can be made view only per role by overriding canWrite(): every way to draw, edit findings, comment, sign off or manage drawings is hidden and refused, combined with canEdit() and the other rules with "and". See "Restricting pages per role" in the README.

1.4.0 Nov 13, 2026

Added

  • MarkupField::imageFrom('photos'): draw on the first image of a FileUpload in the same form — also on a photo that was just uploaded and is not saved yet. While there is no photo, the field says Add a photo first. Then you can draw on it here. instead of showing an error.
  • MarkupField::embed(): the field's HTML for a screen that is not a Livewire form. Warp Offline uses it to show the field in its offline form, so arrows and pins can be drawn on a photo without a signal.
  • MarkupImage: draws what was drawn with MarkupField into the photo on the server (PHP's GD), for prints, emails and thumbnails. MarkupImage::render($photo, $shapes) returns the picture (JPEG, PNG or WebP), dataUri() a data:image/... URI for Warp Print's Field::image() or an email, and fromDisk() reads the photo from a disk. Options: maxWidth (make a large photo smaller first; the marks stay on the same spot), notes (list the pin notes under the picture), font, format, quality and maxPixels. Phone photos are turned by their EXIF orientation first, as the browser shows them. GD is suggested, not required. A Latin font (Liberation Sans Bold, SIL Open Font License 1.1) is bundled for the text.

Fixed

  • MarkupField: the pin tool of the field was named "Finding — click where the problem is", the name of the drawing workspace's tool. A form field has no findings, so it is now "Pin — click the image to add a numbered note" (new translation key field.pin_tool, in all 10 languages).

1.3.2 Nov 12, 2026

Changed

  • Now requires Filament 5.8.3 or later (was 5.0). Older 5.x versions have known security advisories (Composer 2.9 and later refuses to install them), and the plugin cannot be tested on them. The tests now also run on the lowest supported versions before each release.

1.3.1 Nov 10, 2026

Security

  • MarkupField / MarkupEntry: image stamps are dropped from the field's shapes when saving and showing, so a record can no longer make people who open it load an image from an outside URL. The field has no image stamp tool, so nothing drawn with it is lost.

1.3.0 Nov 10, 2026

Fixed

  • Summary: the weekly chart had "up to 7" between the first and the last date. The largest week and 0 are now a scale on the left, on a dotted top line and the bottom line. The translation key summary.max is gone.
  • Summary: the lines are named for what they count ("Not yet resolved at week end", "Found that week", "Resolved that week") instead of "Open", which is also a status, and the new findings are a blue dashed line instead of red next to the orange one.
  • On a phone (40rem wide or less) the workspace without height() is at least 85% of the screen high, so the drawing keeps about 430px under the wrapped top bar instead of about 200px. The bar of a drawing tool or a selected markup is one row at the top of the drawing that scrolls sideways, instead of wrapping over the whole drawing. This row and the tool row show a shadow at the end where more is hidden. The page menu uses a row of its own, so the page name is not cut.
  • Summary: the assignee names are plain text instead of orange links. Each row has "Show in list" (also Unassigned), and a person has "Make a link to their findings…" (it opens the window that makes the link) with a link icon instead of "Portal" with a share icon. The Unassigned row says "No one to send a link to". On a phone the buttons are on a row under the numbers, so the table is not cut on the right, and the close button stays next to the title.
  • Summary: the dates of the weekly chart are written the way the language does ("Nov 9, 2026", "2026年11月9日", "9. Nov 2026") instead of "11/9/2026".
  • On a phone, every tool has a short name under its icon (tooltips do not show on touch screens), and Compare, Export and Drawings in the top bar show their names. Text hidden on a phone stays the name of its button for screen readers. New translation keys: tools.short.*, summary.show, share.no_portal.
  • Japanese: a revision is "B 版" instead of "第 B 版", and the chart is "直近 12 週".
  • Summary: the cards say which statuses they count ("Open + In progress", "Fixed + Verified"), the number columns of the tables line up, the title and the close button stay at the top while the window scrolls, and the legend sample of "Found that week" is dashed like its line.
  • Tools: two columns, left to right and top to bottom, with Undo and Redo side by side in the last row, and a little shorter buttons. The tools used to fill as many columns as the height allowed, so they moved between columns with the screen height and the language, and Redo stood alone at the top of a third column. The column scrolls when it does not fit. The shadow at the end of the phone tool row is lighter.
  • Findings panel: the filters and the list scroll as one, so the first findings show right under the filters, and "Add a finding" stays at the bottom instead of being cut in half. The note about findings on other revisions is under the list, two lines until you click it.
  • Without height(), the workspace on a wide screen is at least 640px high instead of 480px (it still fills the screen below it when there is more room), so the findings panel shows findings under the filters.
  • The page menu is up to 20rem wide instead of 14rem, so "1 / 2 · A-101 · 1F floor plan" is not cut on a wide screen.

Added

  • Findings: above the list, the number of findings of this drawing that are only on another revision ("Not in this list: 2 findings that are only on Rev. A …"), and a tooltip on the tab ("Findings pinned on this revision of the drawing"). This explains why a list of all findings of a record shows more than the tab: a new revision usually takes over only the open findings. warpMarkupFindings() also returns elsewhere (count, revisions), from the new Markup::findingsOnOtherRevisions(). New translation keys findings.count_help and findings.other_revisions.

1.2.1 Nov 7, 2026

Changed

  • README "Drawings of one record": for() alone keeps projects apart — a finding of another project is gone on the page, also through ?finding= or a direct call — so the example no longer adds a condition to findings(), and the section explains what that condition is for (hiding findings within the project). It also shows how to register the page and link to it from the resource's table and edit page.
  • README "Testing": a new part "Testing drawings of one record, locks and permissions" (a resource page tested with its record, drawings made with 'owner' => $project, statusLock and canDelete, assertActionHidden() for Delete), warpMarkupDrawings() in the list of Livewire methods, and every key warpMarkupFinding() returns (canEdit, canDelete, canComment, statusLock and the rest).
  • Laravel Boost guidelines and skill: the same points (for() needs no findings() condition; statusLock, canDelete and warpMarkupDrawings() in tests).

1.2.0 Nov 6, 2026

Added

  • A JavaScript API for browser tests (Playwright and others) on the workspace and the form field: pointOnDrawing({ x, y, relative }) (where a point of the page is on the screen), pinsOnScreen() (the pins with their finding, title, status and the point to click) and whenIdle() (waits until loading and saving have finished). See Browser tests (JavaScript).

1.1.1 Nov 6, 2026

Changed

  • README: a new section "Testing" lists every Filament action of the workspace (warpMarkupCreateFinding, warpMarkupEditFinding, warpMarkupDeleteFinding, warpMarkupBulkEditFindings, warpMarkupShareFindings, warpMarkupCreateDrawing, warpMarkupEditDrawing, warpMarkupDeleteDrawing, warpMarkupCreateRevision, warpMarkupDeleteRevision, warpMarkupUploadDrawings, warpMarkupPinTypes) with what it does, its arguments and its form fields, a full Pest example with callAction() / mountAction(), and the Livewire methods behind the status buttons, comments and the findings list.

1.1.0 Nov 6, 2026

Added

  • Instructions for AI coding assistants (Claude Code, Cursor, Codex) through Laravel Boost: a guideline that Boost adds to CLAUDE.md and AGENTS.md, and the warp-markup-development skill for building workspaces and testing them. Select qalainau/filament-warp-markup in php artisan boost:install, or add it to "packages" in boost.json. See AI coding assistants (Laravel Boost).

  • php artisan warp:assign-tenant "App\Models\Team" 1 (with --dry-run): for apps that add tenancy later, gives the drawings, pin types and share links saved without a tenant to one team, so the team panel shows them. Revisions, pages and markups move with their drawing. Every row without a tenant moves, in one transaction.

  • README: Adding tenancy to an app that already has drawings and Testing with tenancy (opening a team's page in a test, and what another team's IDs do: they are treated like deleted ones, not as an error).

1.0.0 Nov 5, 2026

Added

  • First release: drawing workspace (PDF and images), markup tools, findings as your own records, revisions with carry-over and comparison, export and findings report, form field.
  • Areas (rooms): a zone tool draws named areas; findings know the area they are in (list, search, filter, report, CSV), zones('room') fills an attribute of new findings, and Color by count colors areas by their open findings.
  • Links between drawings: a link tool opens another drawing or page, Back returns, and Find links turns sheet numbers in a PDF page's text into links. Page names come from the sheet number in each PDF page's title block, and new revisions keep them.
  • Quantities: a count tool, a Quantities tab (counts, total lengths and areas, area of each named area) and a CSV of all pages.
  • Change many findings at once (status, assignee, due date), from the list or by selecting pins on the drawing.
  • beforeStatusChange() and statusLocked(): rules for status changes, for example a photo before Fixed or an approval with Warp Flow before Verified.
  • stamps(): your own stamps, with {date} and {user}, or images.
  • Photos: mark up a comment photo (the drawing shows on the thumbnail and in the report), and compare a photo with the first one.
  • Compare: align two revisions with two points, and Cloud the changes draws revision clouds around what changed.
  • Export the findings as CSV (Excel) or BCF 2.1 (BIM tools).
  • shareLinks(): share chosen findings with people without an account; they reply with comments, photos and “Fixed”. Links expire and can be revoked.
  • FindingsDigest and php artisan warp-markup:digest: each assignee gets one message a day with their overdue findings.
  • Multi-tenancy: new findings belong to the current tenant (BelongsTo, MorphTo or BelongsToMany), findings are filtered by tenant, files are stored in a folder per tenant, and scopeToTenant(false | relationship:) turns scoping off or names the relationship. The owner and tenant of a drawing are stored as text, so integer, UUID and ULID keys all work.
  • Upload a whole drawing set at once: files whose name or sheet number matches a drawing (A-101_rev-C.pdf) become its new revision, with a preview before uploading.
  • findingTemplates(): common issues that fill the finding form — picked before dropping a pin or at the top of the form, with values the form does not have and a due date in days.
  • checklists(): walk a checklist on the drawing or room by room (OK, Failed, N/A), make a pinned finding from a failed item, finish and reopen; results as CSV and in the findings report.
  • layers(): put markups on layers, move them between layers, and hide layers per person.
  • pinTypes(): a pin list (symbol + name) that people edit on screen. Pins show the chosen symbol instead of the number, a one-off symbol can be typed, and the symbol of a placed pin can be changed. The finding list, details, report, share page and CSV show the symbol. Also on MarkupField. MarkupPinType::createDefaults() adds starting rows.
  • A summary by status, assignee, area, drawing and summaryGroups(), with the open findings week by week.
  • Portal links: a share link that always shows everything assigned to one person or company (Shares::syncPortals() for changes made outside the workspace).
  • signOff(): a hand-written sign-off at handover, stored with the statement and the counts, and printed in the findings report.
  • Search the text of every page of a PDF drawing; matches are outlined on the drawing.
  • assistant(): optional AI (Claude, or your own MarkupAssistant / ReadsTitleBlocks) that suggests the common issue and title from a photo and reads title blocks.
  • Revisions::createDrawing() from code: the drawing belongs to the current tenant unless you pass 'tenant' (or 'tenant' => null for none), and unknown keys such as owner_type are refused instead of being ignored.
  • German, French, Spanish, Italian, Brazilian Portuguese, Korean and Chinese (simplified and traditional) translations, next to English and Japanese. The messages for an unsupported file, an unreadable image and a share link without findings are translated too.

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?