ACS Commons 6.15.4 – Unable to Edit Pages via editor.html (Old 4.x Functionality Missing)

​@ramaem12 

• No, ACS Commons Dispatcher Flush / Adobe League pages becoming read‑only in editor.html after upgrading to 6.15.4 is not documented as "expected" behavior.
• There is no Adobe‑supported toggle to "bring back" the old page‑based editing model. From Adobe's side your supported options are:
  • run a version of ACS Commons where the behavior matches your requirements, or
  • customize / fork ACS Commons at your own risk.

Because ACS AEM Commons is an open‑source project, any fine‑grained behavior change in 6.15.4 (like locking those utility pages) is defined and supported by the ACS project itself, not by Adobe product support.

Hi ​@ramaem12,

I was trying to reproduce the issue, but everything works fine, and I have no problem to edit pages using ACS Commons 6.15.4. I have checked it on AEM 6.5 with SP23 and AEM 6.5 LTS with SP2 (6.6.2)

Could you try below options:

• Use different browser, and/or incognito mode.
• Use Content Tree to edit component

  

   

• Upgrade to ACS Commons 6.16.0
• Make sure you do not have any customization in your code that could affect ACS Commons 

​@ramaem12 -

This is expected behavior with ACS Commons 6.x, not a defect. In 4.x, some utilities under /etc/acs-commons could be accessed via editor.html and behaved like editable pages. In newer versions, these have been refactored into administrative tools rather than authorable content, which is why they now appear read-only in the editor.

This also aligns with the broader direction of AEM, where /etc-based, page-driven configurations are being phased out in favor of structured configurations and dedicated consoles.

There isn’t a supported way to retain the legacy editing model in 6.x—so the practical approach is to adopt the newer usage pattern or stay on an older ACS Commons version, which isn’t ideal from a long-term support and compatibility standpoint.

Hey ​@ramaem12 , This is expected behavior in ACS Commons 6.x. The project underwent a major architectural shift starting with version 5.x, moving many features away from the classic page-based (editor.html) authoring model to a Granite UI console-based approach (tools/operations consoles).

Why This Changed:

• ACS Commons 5.x+ aligned with modern AEM patterns, replacing custom 

  /etc/acs-commons/*

   pages with Granite UI admin consoles accessible under Tools in AEM.

• Features like Dispatcher Flush, Bulk Workflow Manager, and others were migrated to 

  /apps/acs-commons/content/

   console paths (accessed via 

  Tools > ACS Commons

   in the AEM navigation).

• The old editable pages under 

  /etc/acs-commons/

   are no longer supported in 6.x.

Your Options

1. Use the new console-based UI (recommended)

   • Navigate to AEM Start > Tools > ACS AEM Commons to find Dispatcher Flush and other features.

   • The URL pattern is typically: 

     /apps/acs-commons/content/dispatcher-flush.html

      (accessed through the Tools menu, not editor.html).

2. Check the ACS Commons documentation for each feature's new access path:

   • ACS Commons Feature Docs

   • Each feature page documents the new console location.

3. Pin to an older version (not recommended long-term)

   • You could stay on ACS Commons 4.x, but you'd miss security fixes, AEM compatibility updates, and new features. This is especially problematic since your project targets AEM 6.5 LTS / AEM as a Cloud Service (per your README), which expects newer ACS Commons versions.

4. Custom overlay (advanced, unsupported)

   • You could theoretically overlay the old page components back, but this is fragile, unsupported by the ACS Commons team, and will break on future upgrades.