That looks good thanks. I'm a little disappointed I could find any Adobe
basic Authoring videos for our business users. It'd be a nice way to
ease them into the new interface, but those docs will do nicely.
We're finally going to switch our AEM Author community from Classic to
Touch. Can any one recommend a video online that show covers the basics
of AEM authoring in Touch? Note most of them won't have an Adobe Id (I
don't know how much that matter for accessing resources on this site).
Sorry to resurrect this a year later, but I have to wonder if there has
been any progress on this issue. It seems odd that we can convert all
our other custom components but if we've created custom form actions we
have to scrap everything just so that it works on Touch.
Thanks, but system/console/osgi-installer just tell me that the config
was installed from jcrinstall:/apps/system/config, which I kind of knew
anyway. It doesn't explain how the config appeared in
/apps/system/config (we didn't put it there, it wasn't there on our
AEM6.3 instance, in just appeared after this instances was upgraded to
AEM6.5) nor why even after I delete the entries in /apps/system/config
they come back after a restart.But I guess if this isn't a common issue
with the AEM6.5 upgra...
We have AEM website hosted by Adobe MS that is being upgraded from
AEM6.3 to AEM6.5 ("upgrade in place").Every since the upgrade mystery
configurations (four of each)
in turn creates OSGI configs. When we restart an instance we get spammed
with errors *ERROR* [Apache...
Assuming one were using oob Lucene search for a website, does anyone
know if AEM provides a way to display popular queries? By that I mean
something that can provide business users with information on the lines
of "in the past week 720 people searched for 'cat food', 31 people
searched for 'baseball'..."I went through the doc and while I can see
standard options like Stopwords and such, I don't see anything about
historic search stats. There is obviously the popular queries in
Do category names for clientlibs need to be unique across all the
projects on the same instance?Say you have multiple sites hosted on the
same AEM instance, each with its own apps folder.apps/foo/text/clientlib
category cat_textapps/bar/text/clientlib category cat_textWhat we found
is that foo page we ended up loading the css for both foo and bar
projects.If is easy enough to make each category unique, but it seems
very wrong AEM would assume you'd want to take the styles from different
What we are using is based on the OOB jsp search component. Looking at
I can see the OOB query translates to
cq:Page)[(jcr:contains(., 'gas') or jcr:contains(@jcr:title, 'gas') or
jcr:contains(@jcr:description, 'gas'))] |
dam:Asset)[(jcr:contains(., 'gas') or jcr:contains(@jcr:title, 'gas') or
We've implemented the simple OOB search on an AEM6.3 instance. The
search returns the results as expected but I keep getting an Info
message in the logs suggesting we create an index. That would be fine
expect that query the log seems to be executing doesn't seem to reflect
the search we've set up. The search code looks something like this
(simplified for the purpose of the example): Search mySearch = new
log entries look so...
Has anyone here run a CQ.5 to AEM6.x migration with MSM content before?
We have a site on CQ5.5 We plan to migrate the site to a fresh AEM6.1
(new servers). It is a simple with no custom Java code, and as such plan
to migrate was to take packages from the CQ5.5 instance and install on
the AEM6.1 instance via package manger. While this seemed to work in
most instances we hit a problem with the Multi-Site Management (MSM)
feature.The existing site uses MSM. The site has been running for years
We are experiencing and odd issue on a new site in development in which
content cached from Publish is causing an error in Author.We using the
Adobe Managed Service for hosting. On their boxes the Dispatcher server
is shared between Author and Publish but I still would not expect Author
to be checking content cached by Publish.The error in Author is a pop up
that states: "Your request could not be completed because you have been
signed off". The user is automatically signed back in (the Log In s...