Current resource is used - which cannot work if a component is included from a template in /conf/ instead of /content/
WCON-75
Extensions: Support versioned page in side-by-side view
WCON-49
semicolon in TEXT_MULTIFIELD breaks Configuration
WCON-19
API suggests a text area widget is available
WCON-76
CAConfig Editor: Local Storage Caching prevents displaying new parameters correctly
WCON-74
Allow to remove a CAC
WCON-73
Migrate front-end editor components to CoralUI 3 and remove dependency on CoralUI 2
WCON-72
Configuration Editor: Validate decimal separator for double params
WCON-71
Allow scheduled activation of CACs
WCON-70
Allow to publish individual CAC entries
WCON-69
Editor binds click actions of first item in collection to every item
WCON-65
Multiple editor reloads on a collection configuration breaks the editor
WCON-64
Allow to replicate the configuration from the editor
WCON-62
Collections of Collections break the editor
WCON-60
Allow unlimited configuration of the AbsoluteParentContextPathStrategy
WCON-59
AEM Page Persistence Strategy: delete configurations if configuration editor is removed
WCON-58
Configuration Editor does not replicate current pagge
WCON-57
add a resourcetype to pages created by PagePersistenceStrategy
WCON-56
wrong coordinates to Configuration editor
WCON-55
ConfigSampleSub[] can't be found in ConfigSampleNested
WCON-54
Editor pages should not open on publish and should set hideInNav=true by default
WCON-52
Extend custom ContextPathStrategy to allow a CAC editor page outside the main content tree
WCON-51
Leverage wcm.io extensions custompathstrategy in sample-app
WCON-50
CAConfig Editor: Ship with own AngularJS version
WCON-47
Reference Provider: Return only cq:Page nodes, handle collection items correctly
WCON-45
AEM Page Persistence Strategy: Use Page for configuration collection root resource
WCON-44
AEM Page Persistence Strategy: use PageManager API to delete configuration pages
WCON-43
Context-Aware Configuration Referencer Provider
WCON-42
Allow to define a multifield pathbrowser
WCON-41
Problem with multi nested List of configuraiton.
WCON-39
Allow to activate configuration pages to publish instances
WCON-38
RootTemplateContextPathStrategy: Allow to match all hierarchy pages against configured template paths
WCON-37
Config Editor do not set cq:lastModified
WCON-36
Configuration editor: Disable add/save buttons when no context path detected
WCON-35
Rich text area property with richt text editor in modal popup
WCON-32
TextArea Field
WCON-31
Inherited collection items for configuration collections with collection inheritance are not stored properly
WCON-30
Some CQ properties are displayed in configuration
WCON-29
create a default value for an array of subconfigs
WCON-28
A problem with list of subconfigs
WCON-27
Config Editor: Default values are not displayed
WCON-26
Show proper error message when write access to repository is denied.
WCON-25
Pathbrowser support for Context-Aware Configuration Editor
WCON-24
Context-Aware Config Editor: Control Collection and Property inheritance
WCON-23
Context-Aware Config Editor: Inherit and Override Field Handling
WCON-22
Context-Aware Configuration Editor HTTP API
WCON-21
Context-Aware Configuration Editor GUI
WCON-20
wcm.io Configuration V2 based on Sling Context-Aware Configuration
WCON-18
Support Nested Context-Aware Configurations
WCON-17
Editor does not display overridden default configuration values
WCON-16
issue 1 of 76

Current resource is used - which cannot work if a component is included from a template in /conf/ instead of /content/

Description

I realize this might not be the correct project to send this issue in, but the generic Sling Context-Aware Configuration is also not a good place, since this is really an AEM-specific problem.

Whenever one puts a component in an editable template, that component gets placed in /conf/. When creating a page from that template, it could be that the component node is not copied to /content/, this can have various reasons (i.e. component being locked in the template, ...).

Here is where the problem occurs: When creating a ConfigurationBuilder, you'd normally use the resource, which can point to /conf. This results in CAConfig not being able to find the configuration.

Another similar problem occurs when using ${caconfig} in Sightly, it will also use the /conf path, instead of the /content path.

I have solved this problem a few times in my components by using ${currentPage} instead of ${resource}, but this more feels like a hack than an actual solution. + this still does not allow me to use ${caconfig} in HTL files.

I have thought about providing a context path strategy to also allow context paths to be found in /conf/ folders, but I quickly realized that things like the language are missing, i.e. I would be unable to build the correct context path in all cases.

So I feel this should be fixed maybe even in AEM itself, or additional tooling could be provided such as ${pageCaconfig} in HTL and indeed a guideline to use the currentPage instead of the resource when creating a ConfigurationBuilder.

Status

Assignee

Unassigned

Reporter

Henry Kuijpers

Labels

None

Components

Affects versions

Priority

Critical
Configure