The following are release notes for the latest versions of the ACE components.
The following are release notes for the latest versions of the ACE components.
When upgrading from ACE < 1.22 to ACE 1.22 or later for an existing environment, make sure to change the configured name of the Kafka Connect connector in order to not run into issues with non backwards compatible configuration stored in Kafka. Please see documentation linked above for more information.
The following are release notes for the latest versions of the ACE components.
The following are release notes for the latest versions of the ACE components.
The ARM version of the ACE Image service container will not be able to deliver images as WEBP.
With the upgrade of kafka-connect-couchbase for ACE 1.22.0, the Kafka Connect configuration (couch-kafka.json) has changed.
(1) Instead of configuration like this (default from ACE 1.21.0):
{
"name": "couch-kafka-connector-aceEvents",
"config": {
"connector.class": "com.couchbase.connect.kafka.CouchbaseSourceConnector",
"tasks.max": "1",
"connection.cluster_address": "ace-couch",
"topic.name": "aceEvents",
"connection.bucket": "cmbucket",
"connection.username": "cmuser",
"connection.password": "cmpasswd",
"connection.timeout.ms": "2000",
"use_snapshots": false,
"dcp.message.converter.class": "com.atex.ace.indexing.connector.converter.CouchbaseEventConverter",
"event.filter.class": "com.atex.ace.indexing.connector.filter.AceKafkaFilter"
}
}
(2) The configuration should now look like this (default from ACE 1.22.0):
{
"name": "couch-kafka-connector-aceEvents",
"config": {
"name": "couch-kafka-connector-aceEvents",
"connector.class": "com.couchbase.connect.kafka.CouchbaseSourceConnector",
"tasks.max": "1",
"value.converter.schemas.enable": "true",
"value.converter": "org.apache.kafka.connect.json.JsonConverter",
"couchbase.bucket": "cmbucket",
"couchbase.username": "cmuser",
"couchbase.password": "cmpasswd",
"couchbase.seed.nodes": "ace-couch",
"couchbase.stream.from": "SAVED_OFFSET_OR_NOW",
"connection.timeout.ms": "2000",
"use_snapshots": false,
"couchbase.compression": "ENABLED",
"couchbase.source.handler": "com.atex.ace.indexing.connector.converter.CouchbaseEventConverter",
"couchbase.event.filter": "com.atex.ace.indexing.connector.filter.AceKafkaFilter",
"couchbase.topic": "aceEvents"
}
}
(3) The ACE Kafka Connect service now use the environment variable KAFKA for Kafka bootstrapping instead of the previous ZOOKEEPER. For ACE 1.22 you however still need to supply both variables.
(4) Since ACE 1.22 Kafka Connect is not backwards compatible with the one from < 1.22, completely new Kafka topics should be used when upgrading to ACE 1.22. Otherwise you risk Kafka Connect running the incorrect connectors.
(5) The Kafka topics used by the ACE Kafka Connect service (see documentation) must as of ACE 1.22 use a cleanup policy set to compact.
(7) Also make sure that the ace-kafka-connect.properties configuration file does not include the following property:
offset.storage.file.filename=/tmp/koffsets
Please see the ACE installation documentation for more information.
The following are release notes for the latest versions of the ACE components.
The following are release notes for the latest versions of the ACE components.
The following are release notes for the latest versions of the ACE components.
The following are release notes for the latest versions of the ACE components.
The following are release notes for the latest versions of the ACE components.
ignoreMissingVersions in
http://ace.atex.com/doc/ace-core/reference/service-configuration/#indexer.
code.json:
"ContentCloning": {
"contentTypes": ["articleContent"]
}
http://ace.atex.com/doc/ace-core/reference/callback-api/#on-content-init-on-content-clone
for info on how to configure the callback that can be used to initialize the cloned content.
The following are release notes for the latest versions of the ACE components.
The content service request redirects are now done to revision instead of version (AD-285). Therefore, there will be a potential window of inconsistency when the services are upgraded. The file delivery service and image service will require the content service to be in the upgraded version to work properly.
The following are release notes for the latest versions of the ACE components.
ACE Core Content Service configuration has a new configuration property searchAttributes listing the LDAP fields that will be used for user search. If the property loginNameAttribute has been overridden, this field also needs to be set.
login:
ldap:
# loginNameAttribute is the LDAP attribute where a user's login name is stored.
loginNameAttribute: uid
# A list of approved user attributes that will be used when searching for
# users in LDAP. An empty list of search attributes will disable free text search.
searchAttributes:
- uid
ACE Core now supports using AWS Cognito for authentication.
Please see the documentation for more information.
The ACE Core user search for LDAP can now be configured to search in more than the primary field.
Please see the documentation for more information.
The ACE Core user search endpoint will now return more complete data, including the source of the users found.
ACE should now be more restrictive with its version cleanup. A maximum of 4 old versions (split between data and info versions) are removed per content update.
The ACE UI now contains support for authentication with AWS Cognito into ACE.
The ACE UI now contains updated support for the extended user search introduced with ACE Admin UI 1.5.0.
The ACE UI now contains support for the customizable content entry rendering introduced with ACE Content Developer 1.13.
The ACE UI now contains the new widget aceUISlugEditor.
Please see the documentation for more information.
The ACE UI now contains the new widget aceUIRadioGroup.
Please see the documentation for more information.
Entity IDs created for new entities created by the aceUIMetadataEntities widget now contain a randomized suffix to enable re-use of entity names.
A bug has been fixed in the aceUIMetadataEntities widget where error messages would not be displayed correctly.
The ACE Content Developer application can now handle authentication against AWS Cognito into ACE.
Please see the configuration documentation for more information.
The data displayed in the various kinds of content entries in the ACE Content Developer application can now be customized.
Please see the documentation for more information.
The ACE Admin UI application can now handle authentication against AWS Cognito into ACE.
The ACE Admin UI application user search has receieved some major updates. In addition to some graphical updates and usability changes, it will now also display the source of the users found (which can as of ACE 1.12 include AWS Cognito).
ACE Web now defines the standard ACE aspect aceSlugInfo, containing web slug content data.
Please see the documentation for more information.
The following are release notes for the latest versions of the ACE components.
All ACE service health checks are now running on the service port (8080 by default). Any deployment configuration targetting the health checks needs to be updated.
All ACE service prometheus metrics reporting endpoints are now running on the service port (8080 by default). Any promethus configuration targeting the metrics endpoints needs to be updated.
The HTTP client used in the ACE services is now RFC 6265 compliant ('lax') for cookie expire dates.
The ACE services and components can now read authentication details from environment variables in addition to mounted files. Please see the service example configurations in the documentation for more information.
Performing content searches from inside ACE content pipelines should no longer return deleted (hidden) content.
The ACE Taxonomy structure output should no longer include deleted (hidden) content.
The ACE service version endpoint ('/' path) output now includes the name of the service in addition to the version information.
All ACE service health checks are now running on the service port instead of the administration port which makes it easier to use in some cloud deployments.
ACE should now be more robust in the cases where the content hanger fails to write during a content create / update.
A bug has been fixed where the Content Service would fail internally when delivering content metadata where the info version is missing. NOTE: a missing info version is not something that should ever happen and should be considered a separate bug if ever encountered.
A bug has been fixed where ACE would not be able to re-index the search indexes in the case where the backing Couchbase bucket name contained '.' characters.
The ACE service health checks will now be able to handle cases where the Content Service network name is not resolvable.
The ACE Taxonomy Service health check should now correctly return the correct health result.
A bug has been fixed where the ACE internal Content Event consumer component could fail during stop if not started.
The Content Developer configuration JSON now handle environment variable substitution. Please see the documentation for more information.
Please see the documentation for more information.
You can now delete (hide) content using the Admin UI application the same way as in the Content Developer.
The Admin UI configuration JSON now handle environment variable substitution.
Please see the Content Developer documentation for more information.
The following are release notes for the latest versions of the ACE components.
The network ports used in the ACE service Docker containers have changed. Instead of each service using service specific ports internally (like 8081 and 9081 for the Content Service), all services now listen on port 8080 as well as 9080 in their respective containers.
Any port mappings against the network ports used in the ACE service containers needs to be updated to reflect these changes. Such mappings might include docker-compose.yml definitions, customized ACE service configurations as well as proxy mappings.
With the changes to the ACE 1.10 Indexer to allow for it to handle more than one collection, the configuration has also changed. Instead of being split into configuration properties collection and content, you now use the property collections. Example, before and after for identical functionality:
solr:
collection: public
content:
views:
- acePublic
collections:
- collectionName: public
views: [acePublic]
variant: aceIndexing
Starting with ACE 1.10, the File Delivery Service needs to have the ACE authentication token mapped like the other ACE services.
ACE 1.10 introduces a new concept: Content structures, which can be used to let applications such as the Content Developer display and navigate project content hierarchies.
Please see the documentation for more information.
Just like the regular Content Service content endpoints, the workspace endpoint now support passing the "atLeastRevision" parameter. This can be used to ensure the content data returned is of the same or newer revision than the one passed.
Please see the documentation for more information.
The ACE Indexer application can now be configured to index more than one collection.
The ACE File Service now support uploading files using chunked content encoding without having to specify the HTTP Content-Length header.
Please see the documentation for more information.
The ACE File Service can now be configured to only allow upload of files with sizes up to the configured value.
Please see the documentation for more information.
Workspace images fetched through the Image Service should now correctly handle cases where the supplied token is invalid or expired.
The Content view service should now respond with 200 OK (no effect) instead of an error in cases where the content isn't present on the view it's being removed from.
ACE user passport data read through the Userdata Service will now always include the "loginName" property regardless of whether the passport content aspect data contains it or not.
The ACE UI Content service now has support for requesting specific revisions of content and content metadata using the 'atLeastRevision' ACE content parameter.
The ACE UI library now contains support for ACE 1.10 Content structures.
A bug has been fixed where the ACE UI authorization service would not correctly use the security contexts of the user.
The ACE UI Content Event Service (used by the inboxes in the Content Developer application) can now handle being loaded over HTTPS, which will result in using the wss protocol instead of ws.
The Content Developer application should now work correctly against a Content Service cluster, and should no longer require a dedicated Content Service instance.
The Content Developer application now supports ACE 1.10 Content structures and will - when configured - display a content structure overview in its left hand side navigational pane.
A bug has been fixed where the Content Developer content editor would fail to display field validation messages.
A bug has been fixed where the Content Developer inboxes would make the entire viewport scroll in Google Chrome version 76 and newer.
The Content Developer inboxes can now be configured to be disabled using the 'disabled' flag instead of being disabled when configured with empty configuration.
The unpublish button (shown in the content information pane) should no longer be displayed for users lacking the required permissions.
Pressing escape with the recent content dialog present should no longer interfere with background components such as the content editor.
A bug has been fixed where the Content Developer inboxes would in some cases display duplicate content entries.
The Content Developer inboxes now defaults to allowing entries for content in cases where the user has no editor contexts instead of disallowing them.
The Content Developer workflow inbox should now be more consistent in its usage of the 'No entries...' label.
You can now add and edit ACE user passport data for users in the Admin UI application.
The Admin UI application should no longer use the same browser local storage key as the Content Developer application, which could previously result in both applications displaying recent content dialog entries for content types they could not handle.
A bug has been fixed where the Admin UI application would not correctly handle missing i18n configuration strings.
The following are release notes for the latest versions of the ACE components.
ACE now has support for content workflow.
Please see the documentation for more information.
ACE now has support for user contexts.
Please see the documentation for more information.
It is now possible to selectively re-index content based on aliases rather than only performing full re-index operations.
Please see the re-indexing documentation for more information.
The Content service should now respond with better error messages in cases of 404 (Not Found) responses from workspaces and from views.
ACE will now delete old content info versions as well as old view information whenever the limit for these values have been reached. Previously only data versions were deleted.
All responses from ACE services will now include a header called 'Ace-Response-Origin' with a value indicating which exact service instance the response is originating from.
The ACE Image service is now property validating user-supplied input parameters (such as width, etc) and will reply with HTTP status 400 (Bad Request) instead of 404 (Not Found) for bad input.
The Taxonomy service should now respond with HTTP status 400 (Bad Request) for completion requests on non-dimensions.
ACE UI now has support for ACE workflow.
Please see ACE workflow for more information.
ACE callbacks of type 'OnContentInit' will now receive an additional input parameter: user data. The user data is the full user data content for the currently logged in user, if such exists.
Please see ACE user contexts for more information.
The Content Developer now has support for ACE workflow.
Please see ACE workflow for more information.
The Content Developer now has its own online documentation.
please see the documentation.
The Content Developer inbox automatically filter entries based on user contexts.
Please see ACE user contexts for more information.
A bug has been fixed where the search result area in the full search view would not scroll independently of the left-side faceting fields panel.
The following are release notes for the latest versions of the ACE components.
The ACE Indexer service should now once again correctly be able to perform retries when failing batches. In addition, VERSION_NOT_FOUND (specific version not found) statuses are now considered retry-able.
It is now possible to configure the ACE Java Client with a set of default parameter key / value pairs which will be sent as query parameters in every content read request against the ACE Content service.
Please see the documentation for more information.
It is now possible to set request-specific (thread-specific) parameters for the ACE Java Client which will be sent as query parameters in every content read request against the ACE Content service.
Please see the documentation for more information.
The following are release notes for the latest versions of the ACE components.
ACE type and configuration content bootstrapping has been improved to be more robust.
A bug has been fixed where the Taxonomy Service auto-completion endpoint could previously return incorrect entity IDs for entities in enumerable dimensions.
A bug has been fixed where the creation and modification dates of an ACE content could in some circumstances be reversed in content updates, leading to somewhat confusing data.
A bug has been fixed where an ACE upgrade could fail if the aceCallbacksConfig type had been extended with new properties.
A bug has been fixed where the ACE permission service could fail with a NullPointerException for roles with missing permission data.
CODE and ACE UI now support declaring 'aside' columns in presentation templates. See http://ace.atex.com/doc/releases/ace-ui/v1.8.0/templates-reference/overview/#template-layouts for more information.
ACE UI widgets can now access their respective template data binding names. See http://ace.atex.com/doc/releases/ace-ui/v1.8.0/templates-reference/overview/#reference for more information.
CODE and ACE UI has been updated for better usability. Among other things, tab ordering, color contrasts and highlighting of selected elements have been improved.
The Categorization widget has been adjusted to work with the new auto-completion format from the ACE 1.8.2 Taxonomy service.
A bug has been fixed where the aceUIFileUploader widget could in some situations crash when cancelling the file selection dialog.
A bug has been fixed where ACE UI would be unable to link to other content in the editor unless the current user had *-permissions on the given type.
The aceUIFileUploader widget now correctly handle drag-and-drop of folders.
The Clipboard Service should now correctly return empty data in the cases where the clipboard doesn't yet exist.
It should no longer be possible to click through the error overlays in the aceUIFileUploader and aceUIImageEditor widgets.
The CODE quick search drop-down should no longer display behind the error overlays of the aceUIFileUploader and aceUIImageEditor widgets.
CODE and ACE UI now support declaring 'aside' columns in presentation templates. See http://ace.atex.com/doc/releases/ace-ui/v1.8.0/templates-reference/overview/#template-layouts for more information.
ACE UI widgets can now access their respective template data binding names. See http://ace.atex.com/doc/releases/ace-ui/v1.8.0/templates-reference/overview/#reference for more information.
The ImageService getImageUrl function can now (optionally) be asked to not include the current user token in the produced image url.
CODE autosave previewable check now takes field validation into consideration, only performing the check if all required fields have data.
CODE and ACE UI has been updated for better usability. Among other things, tab ordering, color contrasts and highlighting of selected elements have been improved.
A small number of localization issues have been fixed where UI elements did not display as intended.
A bug has been fixed where the CODE content editor could end up in a disabled state if the conflict dialog was concelled.
A bug has been fixed where CODE keyboard shortcuts would interfere with the filtering input in the recent content dialog.
Recent content data cached in browser local storage no longer include the ACE authentication token, meaning you should not longer get issues with broken images because of expired sessions.
The CODE quick search drop-down should no longer display behind the error overlays of the aceUIFileUploader and aceUIImageEditor widgets.
The following are release notes for the latest versions of the ACE components.
The single-file import functionality of the importer has been improved to be much more efficient and only package resources directly linked to the file being imported. This should result in a much faster import.
A bug has been fixed where the Indexer could in some circumstances end up indexing slightly older content information (such as view information).
A bug has been fixed where the Indexer could in some circumstances end up indexing slightly older content information (such as view information).
The following are release notes for the latest versions of the ACE components.
ACE Core now comes with support for UI Localization, making it possible display and adapt the ACE UI applications for any number of different locales. Please see the UI Localization documentation for more information.
The ACE UI and the Content Developer now support template layouts, making it possible to arrange the template fields in a much more flexible manner. Please see the template layouts documentation for more information.
The ACE UI framework and widgets are now prepared for localization, making it possible to translate them into other languages. Please see the UI Localization documentation for more information.
This version of the Content Developer requires version 1.8.0 of ACE Core due to the UI Localization support now used.
The ACE UI and the Content Developer now support template layouts, making it possible to arrange the template fields in a much more flexible manner. Please see the template layouts documentation for more information.
The Content Developer is now prepared for localization, making it possible to translate it into other languages. Please see the UI Localization documentation for more information.
The Content Developer Docker image is now much smaller than previously, making it easier to download and transfer.
The loading spinner used by the content editor view should now only show if the loading takes longer than 100 milliseconds.
A bug has been fixed where the content editor view was not scrolling correctly.
The Content Developer Atex logo as well as the fav-icon has been updated.
Dependencies on ACE and ACE UI has been updated in order to be up to date.
Dependencies on ACE has been updated to the most recent version (1.8.0).
Dependencies on ACE and the ACE Java Client has been updated to the most recent versions (1.8.0 and 1.5.0, respectively).
The following are release notes for the latest versions of the ACE components.
A bug has been fixed where the Content Service would in some circumstances report content as non-existing when requested by the Indexer. This could lead to some content not being properly indexed in the search indexes.
The following are release notes for the latest versions of the ACE components.
Please note that ACE 1.7.0 introduce a new piece of important Content Service configuration: Kafka host configuration for the eventConsumer and eventPublisher components. Unless configured correctly (working Kafka hosts), ACE will fail to start.
Please see the full Content Service configuration for details.
ACE Core now include the services and functionality required to operate the content activity inbox in the Content Developer application. Please see below for more information.
Fixes and improvements required for widgets to enable content links to be opened directly in the application.
The Content Developer now include a content activity inbox pane which will show content being updated in the installation. The inbox updates live based on the new functionality released as part of ACE Core 1.7.0.
A bug has been fixed where the content editor failed to correctly display errors received from the Content Service.
The following are release notes for the latest versions of the ACE components.
Cache evictions from the ACE Core in-memory alias cache should now be much more efficient. This will be seen most clearly in the performance of CREATE operations and UPDATE operations which create new aliases (creates always create at least one main alias).
The ACE File Delivery Service no longer fetch the content data for calls where the end result should be a redirect to a versioned resource.
The ACE Core documentation should now make it clear that the ACE Kafka Connect environment variable ACE_COUCH is on a connection-string format that can accomodate multiple Couchbase endpoints. Please see the ACE Kafka Connect documentation for more information.
The ACE Core architecture documentation now mentions HTTP caching and where such should be placed for the benefit of the ACE services.
You should no longer always have to clear the browser cache after re-installing ACE in a local developer installation. Previously, you could get browser-cached resources (domain objects, widgets and / or templates) from a previous installation, which confused ACE UI and the Content Developer.
A bug which made it impossible to use the aceUIFileUploader widget in a template has been fixed.
The position of the mouse cursor should no longer lead to entries being auto-selected in the search and recent content modal windows unless you move it.
The Content Developer error view will now display more error information in the case of errors.
The following are release notes for the latest versions of the ACE components.
ACE now has support for Content states - specifically the hidden content state, which will make a content behave as if it had been deleted from the ACE installation but actually isn't. Please see the Content States documentation for more information.
The default user authentication session time in ACE has been increased to be 12 hours instead of the previous 6 hours, meaning users should not be logged out in the middle of a normal work day.
The default client connection settings has been improved to be more in line with currently documented best practices.
ACE type registry objects should now be cached in-memory for the lifetime of a service or until the definition content they were based on are updated.
A bug has been fixed where the User data service read user data definitions over HTTP from the Content Service using a non-configurable service location. The User data service is now instead reading the user data definitions using the actual content service it's deployed within, and is no longer using HTTP at all.
A bug has been fixed where the ACE type service did not include content types by default.
The service configuration 'loginService' has been removed from all services and should be removed from any custom configuration. As long as this configuration is still present, ACE services will fail to start.
ACE UI services and widgets now has support for the ACE 1.6.0 Content states feature.
ACE Content Developer now has support for the ACE 1.6.0 Content states feature.
The following are release notes for the latest versions of the ACE components.
ACE will now properly use cached type definitions instead of having to fetch them from the data storage every time. This should significantly reduce the amount of time spent communicating with the data storage.
A bug in the Search Service where the circuit breaker could never close has been fixed. Previously, once the circuit breaker (Hystrix) was open, it would never actually close due to how the Search Service handled it's content in-lining of search result data.
A bug that prevented the ACE Java Client from de-serializing data from the aceCategorization aspect has been fixed.
ACE Web now depends on ACE Core 1.5.1.
ACE Web now depends on ACE Core 1.5.1 as well as ACE Java Client 1.3.1.
The following are release notes for the latest versions of the ACE components.
The Image Service now always include HTTP cache control headers in HTTP redirect responses, and will by default explicitly forbid caching of the response (Cache-Control: no-cache, no-transform). The value of the cache header is configurable. Please see the 'redirectMaxAge' property of the Image Service configuration for more information.
It's now possible to rebuild ACE search indexes by content type, meaning that you won't have to rebuild the entire index when you only need to re-index one or a couple of different content types. Please see the re-indexing documentation for more information.
It is now possible to un-index a content type, meaning removing all documents for that content type from the search index and ensuring the type is not indexed in the future. Please see the un-indexing documentation for more information.
ACE services no longer use a specific system user (previously: ace-reader) to communicate internally, but instead use the ACE token system. This means you no longer have to maintain the 'ace-reader' user in your authentication provider.
IMPORTANT: As a consequence of this change, the indexer re-indexer services will now require the token properties file to be mounted the same way the rest of the services use it. Please see the documentation for examples.
The Indexer containers will now log intermittent progress reports for re-indexing sessions. Please see the re-indexing documentation for more information.
ACE authentication is now stricter concerning case sensitivity of usernames. Even if the authentication provider used (such as LDAP) might be case insensitive, ACE is not. In addition to a username / password combination needing to be cleared by the authentication provider, ACE now also requires that the user logging in has been assigned a user roles definition. Please see the re-indexing documentation and the authentication documentation for more information.
A documented but non-working feature of the Image Service - to return image data directly on alias requests instead of HTTP re-directing - has been removed since it didn't fit with how the rest of ACE works architecturally.
The ACE UI now ships with deliverables needed by the ACE Admin application.
Search hit items in the full search view is now openable in new browser tabs / windows the same way as you would normally open any other link.
Using the browser 'Back' button to move back to the search view should now result in a search result that includes any previous facetting.
The content types being shown in the recent content list will now be the human-friendly versions.
ACE Admin version 1 (1.0.1) released. This is the first ACE Admin version.
Additional HTTP-related configuration parameters - maximum number of HTTP redirects as well as additional timeout settings - have been added to the Java Client configuration. Please see the documentation for more information.
The Java Client in-memory cache will now automatically evict content items being deleted (permanently removed) in the backend system. Previously it only evicted items on update.
ACE Web now depends on ACE Core 1.2.0.