All Versions
Latest Version
Avg Release Cycle
12 days
Latest Release
573 days ago

Changelog History
Page 24

  • v2.34.3 Changes

    August 31, 2017

    โœ… Unit tests passing.

    โœ… Regression tests passing.

    ๐Ÿ›  A bug was fixed that prevented nested area editing. The bug appeared in version 2.34.0.

    Note that editing an area on the page has never been possible when it is part of the schema of an array field. That is not a new issue. It is being tracked and discussed. Today's fix was for a regression that impacted all nested areas.

  • v2.34.2 Changes

    August 29, 2017

    โœ… All tests passing.

    ๐Ÿ›  Fixed a bug that generated an error message regarding conflict resolution when attempting to edit an area inside a piece editor dialog box.

  • v2.34.1 Changes

    August 28, 2017

    โœ… All tests passing.

    ๐Ÿ›  Fixed an issue impacting unit test harness only. It didn't come up initially because it had to do with automatically creating test/node_modules, which existed our dev environment.

    โœ… No code changes outside of tests.

  • v2.34.0 Changes

    August 28, 2017

    โœ… All tests passing.

    • โš  Conflict resolution has been added to Apostrophe. When two users attempt to edit the same document, whether "in context" on the page or via a dialog box, Apostrophe now makes the latecomer aware of the issue and gives them the option to take control of the document after warning that the first party could lose work.

    Since the first user may have simply abandoned their work, Apostrophe also indicates how long it has been since the first user last made a change.

    ๐Ÿ If the same user attempts to edit a document in two tabs or windows, something very similar happens, although the message is different.

    • ๐Ÿ›  In a related change, Apostrophe does not begin attempting to save an area on the page until the user interacts with it for the first time. This fixes many commonly reported frustrating situations in which one user is editing and the other is logged in but merely looking at the page, creating a ping-pong exchange of save requests.

    • โšก๏ธ Apostrophe's unit tests have been restructured so that a single test file can be run conveniently, via mocha test/docs.js, for instance, and there is no longer a need for us to update test/test.js every time a test is added. Also, the unit tests use the same apos.tasks.getReq and apos.tasks.getAnonReq methods that are used by real-life command line tasks, which provide a more faithful simulation of an Express request object and one we anticipate extending as needed.

  • v2.33.1 Changes

    August 16, 2017

    โœ… All tests passing.

    • ๐Ÿ›  Fixed potential crash in version pruning mechanism.
  • v2.33.0 Changes

    August 10, 2017

    โœ… All tests passing.

    • The login page can be disabled via the new localLogin option of the apostrophe-login module. Set it explicitly to false to disable the login URL completely.
    • ๐Ÿ”จ Refactoring: the apostrophe-login module now has an afterLogin method which takes care of invoking the loginAfterLogin callAll method on all modules that have one, and then redirecting appropriately. This code was factored out to make it easier to use in the new apostrophe-passport module, which allows the use of almost any Passport-based strategy, such as Facebook login, Google login, Github login, etc.
    • apos.users.ensureGroup now delivers the group to its callback as the second argument.

    ๐Ÿ‘ Thanks to Michelin for their support of this work.

  • v2.32.0 Changes

    August 08, 2017

    โœ… All tests passing.

    • ๐Ÿ›  Fixed an S3 asset bundle generation bug that caused .less files to be imported with the wrong file extension if the public folder did not yet exist at the time --create-bundle was used. Thanks to Michelin for their support of this work.

    • โœ… Also added an apostrophe-caches:clear task to aid in testing various functionality. You must specify the cache name since caches may or may not even be known to Apostrophe at task startup time based on whether and when code calls .get for each cache name.

  • v2.31.0 Changes

    August 07, 2017

    โœ… All tests passing.

    • ๐Ÿ‘€ The new testModule: true option causes Apostrophe to supply much of the boilerplate for a published npm apostrophe module that wants to test itself as part of an apostrophe instance, i.e. apostrophe-workflow, apostrophe-caches-redis, etc. See those modules for examples of usage. This is a feature for those writing their own npm modules that wish to unit test by initializing Apostrophe and loading the module in question.

    • ๐Ÿ›  Fixed caching bugs, notably the oembed cache, which is now operating properly. Oembed responses, such as YouTube iframe markup, are now cached for an hour as originally intended which improves frontend loading time.

    • Page type changes only refreshed the schema fields on the first change โ€”ย now they do it properly after every change.

    • Page type changes use the "busy" mechanism while refreshing the schema fields to prevent user interface race conditions and avoid user confusion.

    • trash is never offered as a schema field of the global doc (mainly a concern with apostrophe-workflow).

  • v2.30.0 Changes

    August 02, 2017

    โœ… All tests passing.

    It is now easier to set up Redis or another alternative session store:

    'apostrophe-express': {
      session: {
        secret: 'your-secret-here',
        store: {
          name: 'connect-redis',
          options: {
            // redis-specific options here

    ๐Ÿ”ง For bc, you can still pass a live instance of a store as the store option, but this way is easier; all you have to do is npm install --save your connect-compatible session store of choice and configure it.

    ๐Ÿ‘ Thanks to Michelin for their support of this work.

  • v2.29.2 Changes

    August 02, 2017

    โœ… All tests passing.

    • ๐Ÿ‘ Overrideable widgetControlGroups method takes (req, widget, options) allowing for better control when customizing these buttons.
    • The createControls option of the apostrophe-pages module is now respewcted properly.