Skip to content

Releases: clay/amphora

v6.7.6-beta.2

24 Aug 16:46
Compare
Choose a tag to compare
v6.7.6-beta.2 Pre-release
Pre-release
6.7.6-beta.2

v6.7.6-beta.1

24 Aug 16:46
Compare
Choose a tag to compare
v6.7.6-beta.1 Pre-release
Pre-release
6.7.6-beta.1

Bugfix: Renderer Models

16 Aug 20:06
Compare
Choose a tag to compare

Fixed a bug where renderer models were not being called properly (#592)

Bugfix: Wait For V7 To Bootstrap Layouts

16 Aug 17:15
Compare
Choose a tag to compare

Layouts should not be bootstrapped until v7

Future Preparation

16 Aug 17:13
aea9155
Compare
Choose a tag to compare

Bugfixes

  • Uris can now point to special characters (#591)
  • Automatically add the site's path into redirects (#557)

New Features

  • Convert files service to use amphora-fs (#582)
  • Claycli now handles bootstrapping (#585)
  • Schema service consolidated for future layout feature (#589)
  • Better logging for scheduler (#590)

Feature: Pub/Sub Event Bus With Redis

18 Jun 14:41
Compare
Choose a tag to compare

Features:

v7.0.0-beta.2

18 Jun 14:40
Compare
Choose a tag to compare
v7.0.0-beta.2 Pre-release
Pre-release
7.0.0-beta.2

Feature: Publish Dynamic Pages

04 Jun 19:01
Compare
Choose a tag to compare

Feature:

Allows dynamic pages to be published as long as the _dynamic property is set to true on the page data as documented here

Bugfix:

  • Fixes a bug where rendering dynamic pages pulled from the editable instance of the pagei

Feature: Call publishLayout hook when publishing layouts

30 May 18:13
Compare
Choose a tag to compare
  • Layouts are denoted with a root-level _layout: true property in their schemas
  • When publishing components, amphora will check the schema to determine if they are layouts
  • When publishing a layout, amphora will call the publishLayout plugin hook
  • This is used by amphora-search to populate and update the layouts index

Feature: Routing & Component Error Responses

21 May 20:32
Compare
Choose a tag to compare

Features

  • (#544) Components can now affect the error response sent to the client, allowing components to 404 a page rather than simply send a 500. To use, define a status property on the error thrown from a component. For example:
module.exports.render = (ref, data, locals) => {
    var err = new Error('no results!');
    err.status = 404;
    throw err;
}