Will OpenJDK ever be supported and what happens if we were to use
OpenJDK? Due to Oracle's licensing changes are all AEM user's required
to purchase Oracle Java licensing?
In AEM 6.2 SP1 CFP12 we created a spinset in the touch UI, but we're not
able to add this component in the Classic UI. I can see it under the
browse tab, but adding it does not indicate that component as a Dynamic
Media. When I add it in the touch UI I can see the Spinset in the page
fine from the Classic UI.We're trying to add the spinset as a Dynamic
Media: serverurl" :
"https://crowndev-h.assetsadobe.com/is/image/".Thanks
So I may have found what was causing the issue. We have in place
/etc/map to shorten the links by removing /content. Is there a way to
rewrite /etc/map to not cause a conflict?I attached a picture that might
be helpful.Thanks
We're currently using ACS Commons 2.8.0. I'm currently testing 2.10.0 in
another environment, but I'm not having much luck with the latest
version it seemed to have broken the Author and Publisher 404, looking
at the logs it tries to resolve the "System error page"
/content/error.html rather than the one under
/content/en-us/error/404.All request protocols are HTTP.
I'm pretty sure Directory Browsing is enabled I went through the
httpd.conf and set Options to FollowSymLinks and Indexes. The Directory
settings under the Virtual Host I'm testing already had this set.Is
there a way I can verify for sure this is working on the Dispatcher?
I was wondering if someone could explain why ACS Commons Error Handler
is not functioning properly on the Dispatcher?Here are some of the tests
I have done:Accessing the publisher with the following URL's it will
resolve the en-us specific 404 page
properly:http://publisher:4503/content/en-us/nopagehttp://publisher:4503/content/en-us/products/nopage.htmlWhen
I access the dispatcher with the URL's below it does not resolve the
page with the custom 404, but instead with a blank page (Console does
...
Thanks I was able to get this upgraded by running the current
AEM_6.1_Quickstart.jar. Which populated the quickstart.properties file.
After that I just ran the AEM_6.2_Quickstart.jar. Before starting the
preparation steps, make sure you run the source instance first by
executing it with the java -jar aem-quickstart.jar command. This is
required in order to make sure that the quickstart.properties file is
generated properly. If it is missing, the upgrade will not
work.Alternatively, you can check...
I attached the error logs to the attachment. There are other error logs
in this tail that are not relevant. Maybe this will give you a better
idea of whats going on. In this environment I do have some exclusions
set up to not index certain directories for the Lucene Index.
I've attached another screenshot of me starting the
AEM_6.2_Quickstart.jar but when I check the version it still shows 6.1
SP1. Will I need to perform a clean install and migrate all the content
manually?Thanks
I copied the AEM_6.2_Quickstart.jar to the same directory as the
AEM_6.1_Quickstart.jar , stopped AEM, ran the start command java -jar
AEM_6.2_Quickstart.jar -r author,crx3,crx3tar,nosamplecontent. I'm not
able to to doubleclick since I'm running on red hat 6 cli.The initial
AEM 6.1 installation I performed that doing the unpack. Not sure if this
has anything to do with the upgrade process?I know the jar file is
correct because if I unpack jar file in a new directory it works: java
-jar AEM_6.2_...
Are there specific documents to run an in place upgrade from AEM 6.1 SP1
to 6.2? I did not have success when trying to unpack AEM 6.2 quickstart
over the 6.1 crx-quickstart directory. Please advise.Thank you
Any suggestions on this?Not sure if having multiple layers of live
copies could cause this error? The error does seem to go away when I
"revert inheritance" or turn inheritance back on, and I go back to
cancel inheritance again. It almost seems the the "cq:LiveSyncCancelled"
setting in crx/de is stuck before I did the changes above. 10.11.2016
03:40:51.227 *ERROR* [127.0.0.1 [1478767251219] POST
/content/staging-emea-german/jcr:content/mainpar/column_9/column3/imagecomponent
HTTP/1.1] org.apache...
Kautuk, We're running AEM 6.1 SP1. I have also tested our content and
image component in SP2 and result the same problem.The problem seems to
revolve around the image component. So I go to cancel the inheritance of
the image component properties, change alt image name, reload the page
(using Classic UI), the inheritance will revert back to locked. The
changed tagging will still remain what I changed it too, so the problem
occurs when we go to rollout from the blueprint and the alt image name
get...
Thanks for the replyBackup restore unfortunately is not an option. The
issue happens when the author goes to edit the "Image Alternative Text".
I look in crx/de and I do see the jcr:mixinTypes: cq:LiveRelationship,
cq:LiveSyncCancelled.Here are some screenshots to help.
Our authors are not able to edit alt tags or update images. Here are the
errors from the logs below:31.10.2016 13:09:31.094 *ERROR* [127.0.0.1
[1477933771090] POST
/content/sample/jcr:content/mainpar/column_1/column1/imagecomponent_44c0
HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation
Exception during response
processing.javax.jcr.nodetype.NoSuchNodeTypeException: Node type
cq:LiveRelationship,cq:LiveSyncCancelled does not exist at
org.apache.jackrabbit.oak.util.TreeUtil....
