- The new
apostrophe-jobsmodule, part of the core of Apostrophe, provides a progress meter mechanism and the ability to stop long-running user-initiated operations, such as batch operations on pieces. See the jobs module documentation. You can also refer to the pieces module for examples if you wish to use this for your own long-running user-initiated operations. - Batch operations now have more robust support for “select everything.” A number of bugs related to multiple selection of pieces have been fixed in a refactoring that made this code much more maintainable and predictable.
- The option of pushing an asset of type
template, which never worked in 2.x and was never used by Apostrophe, has been removed for clarity. Our preference is for rendering assets on the server side dynamically when needed, rather than pushing many templates into the DOM on every page load. - An
.editorconfigfile has been added. Thanks to Fredrik Ekelund. - Parking a page only pushes permanent properties.
_defaultsand_childrenshould never have been in the database; they are of course still interpreted to decide what should happen, but the properties themselves did not belong in the database. (You may need to write a migration if they are already there and this is causing issues for you.) - Scrolling UI behavior of pieces improved; various other UI touch-ups. Thanks to Fredrik Ekelund.
-
newBrowserCallshelper forpushmodule can be used when you want JavaScript calls queued up withreq.browserCallto be executed in an AJAX update of just part of a page. - Fixed bugs affecting access to the published/unpublished batch operations and similar.
- the
apostrophe-workflowmodule has also been updated to take advantage of the above and to address a few minor issues.
