We’ve had several apostrophe-workflow releases in the past few days as part of an intense testing process with an enterprise client. So to avoid overwhelming you, here are the changes in a single wrap-up post:
2.1.5:
- Do not park pages when running the add-missing-locales task, this prevents duplication and the appearance of an empty site.
If this has happened to you already, this task can be used as a one-time fix:
node app apostrophe-workflow:remove-numbered-parked-pages
2.1.4:
- Performance and accuracy improvements to the mechanism that decides whether to display the “submit” and “commit” buttons, eliminating false positives and reducing the amount of server work required.
- Added the
apostrophe-workflow:resolve-join-idstask, which can be used to resolve join ids pointing to the wrong locale. This should never happen, but did happen prior to certain recent fixes re: joins in array fields. It should be a one-time fix but can safely be run more than once. - Performance and accuracy improvements to the mechanism that decides whether to display the “submit” and “commit” buttons, eliminating false positives and reducing the amount of server work required.
- Attempts to force-export a nested widget whose parent does not exist in the receiving locale should fail; however this was not producing a clear error message in certain cases and it was also possible to be left with the modal still on the page. Fixed.
2.1.3:
- If an object that is modified in the exported commit does not exist at all in the draft being patched, don’t crash; just disregard it.
- Always show live content in live mode.
- Update the submit and commit buttons only at page load and after actual changes to areas. This significantly reduces unnecessary server load due to polling.
- Refactored to ensure the invitation to export after a commit, etc. works for contextual pieces that eventually refresh the page on save.
- Eliminated false positive change detections caused by the
advisoryLockproperty.