I have a website where the site structure is
/content/mysite/us/en/page.html. I have the following sling mapping set
up so the site can be served without /content/ in the path at
https://example.com/mysite/us/en/page.html: The problem is, when I
view the site without the /content/ path in the URL, all the links on
the page still contain /content/ in them. How do I implement the feature
so that /content/ is automatically removed from all link element
attributes when the URL does not contain /co...
I have an AEM project where a certain component uses the following Java
class: /core/src/main/java/com/mysite/core/util/MyClass.java. I also
have a different site that uses a separate AEM Project Archetype. I
would like to use MyClass.java in the core module of the second site,
however I'm not sure how to go about adding the dependency. Is there any
documentation on this?
I have a scenario regarding translations and I'm not sure what the best
practices for handling it is. Here is the scenario: 1. We have a page in
English2. We create a translated Language Copy of the English page in
French3. The translated French page is later edited to add
France-specific content to an existing Text Component after the page was
translated4. We decide to change some content on the English page in
that same Text Component5. The page gets re-translated into French to
include the ne...
Hi,I was actually referring to rollout inheritance, not the actual node
type inheritance. So if I rollout a page from one path to a different
path on the site, the entire page is copied under a different path in
the JCR. If I'm looking at the rolled out page's nodes in CRX, are there
any properties that tell me which page it's inheriting its content from?
If I have a page or component that is inheriting its settings from
another page or component, how do I see which node it's inheriting from?
A graph-like holistic view of all page inheritance would also be useful.
Does a tool like that exist?I'm in AEM 6.4.2.
The dropdown is now correctly populating in my published instance. I
believe the issue was related to the webserver cache. I'm still not sure
why the pathfinder does not allow me to select the node itself, but
filling out the path manually and uploading the node to the published
server via a content package to activate seems to work.
These are the steps I am taking:1. Author the page with the form
component from the authoring server2. Manually type in
/content/countries into the 'List' field because the pathfinder cannot
find that node in the JCR3. View the page in authoring mode and see that
the dropdown list correctly populates with the data from the child nodes
under /content/countries4. Publish the page5. View the page in the
published environment and see that the dropdown field does not show at
all (I think the dropdown...
Bump. I still haven't been able to get the dropdown list to populate in
a published environment. Here is what my dialog fields look
like:/content/countries is a node in my JCR with child nodes that look
like this:Is there something I'm missing?
In the Form Options component dialog, I am using the dialog field called
Source and I have it set to 'List'. After selecting List, a new path
field shows up which should allow me to select a path in my JCR where
I've created nodes to represent dropdown items, but the nodes do not
show up so I have to manually enter the path. Entering the path manually
successfully populates the dropdown list in authoring mode, but not in
published mode. I am not sure if the issues related to the nodes not
The Core Form Options component has a dialog field called Source which
allows you to select a list of nodes from the path browser to make up
the options in a dropdown list.I have a node of jcr:primaryType =
nt:unstructured with multiple child nodes of the same type that have
String properties for text and value. When I try to select the parent
node from the dialog, it does not show up in the path finder. I am able
to manually enter the path to the parent node in the dialog field, and