I have seen many site having short path and not having .HTML extention.
Short path is based on Resource resolver configuration. Wanted to know
how the extension is stripped? Suppose when AEM is serving
/content/geometrixx/en/company/discover_geometrixx.html it gets
converted www.geometrixx.com/en/company/discover_geometrixx. Here
/content/geometrixx/en is mapped to /en. SO it shorten the path. How it
removes the exntion while serving the page from Publish box to Actual
website. In Webserver cach...
I have link checker enabled with Striping extention. It has also below
rewrite element:a:hrefarea:hrefform:actionWith above all content pages
which I access directly are getting stripped and no .HTML extension is
coming but when I setup vanity it shows URL with .HTML extension. Do I
need to handle Vanity separatly? -Ujjval
Take example of any DAM image. say www.abc.com/content/dam/xyz.jpb when
we open up this path it opens image. Where as same path with query
parameter www.abc.com/content/dam/xyz.jpb?123 downlaods the image. This
happens in Desktop but in Mobile it is fine.
I wanted to know are there any pre-build RTE plugin or extentions
available other than Out of the Box basic version comes.I am aware that
there are options available for customizing RTE but wanted to know if
there are pre-build examples available? Looking for some prebuild text
formating options similar to options available in PhotoShop. My Client
wanted to avoid Custom solution and wanted to see what AEM offers other
than Out of the Box Basic RTE.
@Jörg Hoh I am seeing below error when I activate a page which is having
Vanity URL associaed with it. THis errors I see in Replication log of
Author itself where I have added aliaUpdate=true. Thought to share this
with you before raising Adobe ticket.Source
with it : /content/XXX/holiday27.03.2018 13:30:44 - INFO -
------------------------------------------------27.03.2018 13:30:44 -
INFO - 10-59-2-69-24611 ...
before we close this thread I have few questions to you....1) What is
the expected behaviour of aliasUpdate flag? Were you expecting that flag
to invoke invalidate script for vanity URL as well?2) What we are trying
to achieve is not a custom solution. AEM OOTB provides Vanity and that
can be achieved without having REDIRECT. In this case dispatcher creates
cache. What is AEM's solution for clearing this dispatcher cache?
The screenshot shared above of Author box Dispatcher is wrong I guess.
We should not have Dispatcher configured at all right? We jsut need
Replication Agents. Below changes I have done:- I have disabled
Dispatcher Flush agent in Author box. Added aliasUpdate property to my
publish replication agent in Author box. Anything else in Author or