Apostrophe 3.26.1: hotfix for reliable editing in Chrome

[boutell]

Hello folks,

We've released a hotfix for an ApostropheCMS 3.x problem that Chrome users have reported with increasing frequency in recent days. This problem didn't happen to everyone, or on every page refresh. But we suspect a recent update to Chrome made it more common. It was also more frequent on slow connections.

Here's the bug: some users were unable to click buttons in the admin bar, such as "Images" or "Files." When doing so, the browser console would show a message indicating that #apos-modal was not found.

This issue has been fixed in apostrophe 3.26.1.

To upgrade your Apostrophe 3.x project and fix this issue, just type npm update or npm update apostrophe.

If you have locked your dependencies to a specific version of Apostrophe 3.x (if your package.json entry for apostrophe does not start with ^), then you will need to manually increase it and type npm install.

Thanks to the community members who reported the issue, then worked with us to test the fix.

For the technically minded: Apostrophe's code for starting up the editor assumed the entire DOM would be loaded if the initialization code was deferred until "next tick" with a setTimeout call. This is usually, but not always true. The new code waits for the DOMContentLoaded event.