Hi, really appreciate your follow up on this. I actually implemented it
more or less like what you have described.Instead of extending the
Experience Fragment component, I built a new component that I call
'Reference' component which is able to dynamically calculate the path of
my header and footer based on the language root. By doing this, my
header can be a regular component on any page or an Experience Fragment.
I found no advantage to using Experience Fragments so to speak other
than being a...
I actually watched it. I found the link from one of your posts in reply
to a similar question. Unfortunately, that session did not address the
implementation aspect of this. It only talks about setting up the site
structure based on the languages, countries and business model of an
organization. It does not get into any implementation details.
HelloI searched long and hard everywhere but did not find a satisfactory
answer to this. I'm using AEM 6.5 Editable Templates to build a site
that will be translated to multiple languages.What are some common
techniques for creating a common Header & Footer that can be edited by
content authors? The we-retail & wknd implementations seem extremely
simple and not representative of real-world use cases.Below are some use
cases I can think of.1. Extra content in menu drop-downs in
Navigation.2. Huge...
Thanks for your help so far. To answer some of your questions, I'm using
apache on CentOS and AEM 6.4.3. I have all of my virtual hosts
configured as required, configured dispatcher, etc. Everything is
working as expected. My question is only about URL shortening using
resource maps in /etc/map/http.Somehow the hundreds of blog posts on the
topic including the one suggested above don't seem to work for me. It
took me a while to figure out that outbound URLs are rewritten based on
first match in ...
HelloI'm fairly new to AEM, so bear with me if I'm not using the right
terminology.Using Dispatcher with Multiple Domains I followed the steps
outlined in the link referenced above. I used Approach-1, where AEM
rewrites the URLs rather than setting up apache rewrites. Lot of the
stuff works. I do see pages being cached, etc. What I'm struggling with
are the resource maps that need to be setup for URL shorterning.I'm kind
of lost on what exactly needs to be done in /etc/map/http. I tried
several ...
