Learn more about the development of Acrolinx for AEM.
Notice
Looking for the latest release notes for Acrolinx for AEM as a Cloud Service (AEMaaCS)? You can find them under Acrolinx for AEMaaCs - Release Notes.
Released 31 October 2023
This release, we've improved the way Acrolinx highlighting works for different component and page properties. We've also fixed a bug.
We recommend that you use:
-
Acrolinx Platform 2022.02 or later
-
AEM version 6.5.18
-
AEM Guides versions 4.3.x
-
A new Content Profile — to take advantage of these improvements, you'll need the latest AEM Content Profile.
-
Fewer False Flags - To reduce false issues, we’ve improved the way we extract content. These improvements also make it easier to configure Content Profiles.
-
Acrolinx Highlights More Content - We’ve made a few improvements under the hood to improve highlighting in the Sidebar.
Notice
Acrolinx won't highlight Page Properties components that are hidden behind tabs or aren't visible to the user.
Released 18 July 2023
With this service release, we've fixed a bug in AEMaaCS where the Sidebar button wasn’t showing. This was a result of the upgrade to the newest AEM Cloud SDK API.
Released 7 June 2023
This service release fixes a bug in AEMaaCS where the Acrolinx menu icon wasn’t available in a user’s local environment. This meant that the user couldn’t launch the Acrolinx Sidebar.
Released 16 February 2023
This release has a new improvement that allows you to extract more information from custom components. It's also packed with fresh bug fixes.
This version of Acrolinx for AEM works with:
-
Acrolinx Platform 2021.09 or later (AEM on-prem)
-
Acrolinx Platform 2022.10 or later (AEMaaCS)
We developed and tested this version of Acrolinx for Adobe Experience Manager with:
-
AEM On-premise:
-
AEM version 6.5
-
AEM Guides versions 4.0
-
-
AEMaaCS:
-
Guides version 2022.5.x - 2022.10.x, 2023.3.x
-
We've added additional information to the extracted content in AEM. If the component being extracted is visible on the page, an additional attribute visible="true" will be sent along to the platform, otherwise we’ll set visible="false".
Based on this attribute, it would be possible to exclude or mark cards as read only. This avoids the confusion of getting card suggestions for issues that aren’t visible on the page.
We recommend creating and using custom components in via Adobe’s suggested methods.
If you used custom paths to show or hide Acrolinx, you may have gotten a 404 error that prevented all text from being extracted. We've fixed this issue — Acrolinx looks out for custom prefixes before the standard URL.
You might have noticed that Acrolinx resources wouldn't save in the configuration. We've fixed that issue in this release.
Notice
We've changed the Persistent ID. If you used regex to limit access, you'll need to add it again.
To add the regex again, do the following:
-
Go to
system/console/configMgr. -
Open Acrolinx Allowed Resources.
-
Copy the regex if other than
.*. Store it somewhere safe (for example, in notes). If you don’t have a customized regex, you can simply update to a new version of Acrolinx Integration. -
Update to the new version of Acrolinx and reopen Acrolinx Allowed Resources.
-
Paste the regex that you saved in Step 3.
When you installed Acrolinx without having AEM Guides installed, the digital asset management (DAM) list view would fail to load. We've removed the dependency on the Guides package so you won’t run into this issue again.
There was an issue where the Acrolinx Sidebar wasn't loading consistently when writers accessed AEM Guides. When the Acrolinx Sidebar didn't load, AEM Guides appeared blank. This was due to Guides loading a very large JS file. We’ve taken care of this issue in this release.