Upgrade to 1.0.0-rc838

Concerns: pushword/admin-block-editor, pushword/page-scanner

Contents

The Upload button opens your file dialog instead of the media form

On an image or attachment block, Upload used to open the media form in a modal iframe: pick a file, fill the form, submit, come back. It now opens the device's file dialog and uploads what you pick straight away — the same request a file dropped on the block already made. Select still opens the media library.

Nothing to do, unless you ship your own copy of editorjs_widget.html.twig: the onUploadFile callback of the image and attaches tools must become window.editorJsHelper.onUploadInline, and editorJsHelper.onUploadFile is gone (onUploadImage, which the gallery and embed tools still use, is untouched).

Both blocks also gained a button to drop the media they hold, so changing a picture no longer means deleting the block and building a new one.

Blocks group under a div wrapper

The block editor gains a Group block: an opening marker carrying an anchor and CSS classes, closed by an end marker inserted with it. Everything in between is wrapped in a <div> on the front — the markdown stays flat (a <div …> line and a </div> line), so nothing changes server-side and existing wrappers written by hand in markdown now show up as group markers in the editor. Deleting either marker removes the other; the wrapped blocks stay.

Nothing to do, unless you ship your own copy of editorjs_widget.html.twig — add the two tools to see the block:

groupStart: { name: "groupStart", className: "GroupStart" },
groupEnd: { name: "groupEnd", className: "GroupEnd" },

The link tool's Obfusquer switch is now a rel select: obfuscate, nofollow, nofollow sponsored, nofollow ugc. Existing links keep the rel they carry — one the list does not offer is kept as an entry of its own rather than dropped.

The list is availableRels next to availableDesigns in the tool's config, so a site that overrides editorjs_widget.html.twig can declare its own:

link: {
    name: "link",
    className: "Hyperlink",
    config: {
        availableDesigns: { /* … */ },
        availableRels: { Obfusquer: 'obfuscate', me: 'me' },
    }
},

obfuscate stays exclusive: HtmlObfuscateLink matches rel="obfuscate" exactly, so it cannot be combined with a real rel.

An external link can fail two ways, and they are not the same problem: a URL that answers something unexpected (link-status) versus one that does not answer at all — DNS, timeout, TLS (link-unreachable). Both shipped under one link-external code in rc835, so silencing a flaky host also silenced every 404.

If your errors_to_ignore names link-external, it no longer matches anything. Replace it with whichever half you meant, or with link-* to keep both:

pushword_page_scanner:
  errors_to_ignore:
    - 'link-unreachable'   # the host is down, not your link

Same for a `` comment in a page.

This is the one code change there will be: ScanErrorCodeTest now pins the whole set, so a rename fails the build rather than silently un-ignoring findings on every site relying on it.

The external-URL cache is keyed by result shape, so the first scan after upgrading rechecks every external link once, then goes back to being cached.