The latest Adobe Cloud 6.5 has discontinued the classic UI interface for editors/authors. I would like to know if this can still be enabled because many users in our organization are comfortable and like the classic UI more than Touch UI. Most of our authors/editors feel touch UI is not user friendly. This is not something I get this report from users, they have been saying this for past 4 years.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @GopiTh,
Classic UI is not available in AEMaaCS. You can still find it in AEM SDK, so local version of AEMaaCS, but this is only due to fact AEM SDK is not fully reflecting AEMaaCS.
There is no way to enable Classic UI on AEMaaCS.
Here is documentation that clearly indicates which features are deprecated in AEMaaCS, and which have been removed. As you may see Classic UI is first item on the removed features list.
Hi @GopiTh,
Yes, AEM 6.5 and above officially deprecated the Classic UI, and starting with version 6.4, it’s no longer enabled by default - but it’s still possible to enable and use it if needed.
Here’s how:
Adobe confirms that access to the Classic UI remains available but is disabled by default in AEM 6.5. It can be re-enabled via configuration.
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/operati...
The Touch UI is now the standard interface and Adobe has deprecated Classic UI since AEM 6.4. They no longer enhance it, but legacy access is still supported for fallback and migration scenarios.
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/touch-ui-feat...
How to re-enable Classic UI for your users
1. OSGi Configuration (AuthoringUIMode service)
You can configure the default UI per instance using Root Mapping and the AuthoringUIMode OSGi service.
This controls which UI users see upon login or startup.
2. User Preferences
Individual authors can set their preferred UI-Classic or Touch-in their user preferences, subject to system settings.
3. Session Overrides and URL Access
Users can switch to Classic UI in their current session via configured navigation links (e.g., a monitor icon) or manually by visiting a Classic UI URL like:
Similarly, the Touch UI is accessed via URLs like /sites.html or /editor.html.
Cookies, user preferences, or OSGi settings determine whether the Classic or Touch UI is presented when opening a page or console.
Views
Replies
Total Likes
Hi @GopiTh,
Classic UI is not available in AEMaaCS. You can still find it in AEM SDK, so local version of AEMaaCS, but this is only due to fact AEM SDK is not fully reflecting AEMaaCS.
There is no way to enable Classic UI on AEMaaCS.
Here is documentation that clearly indicates which features are deprecated in AEMaaCS, and which have been removed. As you may see Classic UI is first item on the removed features list.
Views
Likes
Replies
Views
Likes
Replies