since ‎01-06-2015
‎10-12-2019
weba78885530
Level 2
Re: AEM 6.4 supports Open JDK
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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?

Views

4.6K

Likes

0

Replies

1
Re: No able to add Spinset picture in the Classic UI
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
Just following up to see if you found anything from the internal team?Thanks for looking in to this.

Views

867

Likes

0

Replies

1
Re: No able to add Spinset picture in the Classic UI
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
Correct, in the Touch UI it works fine.

Views

867

Likes

0

Replies

0
No able to add Spinset picture in the Classic UI
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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

Views

952

Likes

0

Replies

4
Re: ACS Commons Error Page Handling Issues On Dispatcher
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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

Views

2.2K

Likes

0

Replies

1
Re: ACS Commons Error Page Handling Issues On Dispatcher
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
Please see attached log files.Thanks

Views

2.2K

Likes

0

Replies

0
Re: ACS Commons Error Page Handling Issues On Dispatcher
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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.

Views

2.2K

Likes

0

Replies

0
Re: ACS Commons Error Page Handling Issues On Dispatcher
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
The first request does trigger the 404 correctly, but 2nd one does not. I attached the debug level logs from the dispatcher.Thanks

Views

2.2K

Likes

0

Replies

5
Re: ACS Commons Error Page Handling Issues On Dispatcher
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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?

Views

2.2K

Likes

0

Replies

0
ACS Commons Error Page Handling Issues On Dispatcher
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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 ...

Views

3.0K

Likes

0

Replies

13
Re: AEM 6.1 SP1 in place upgrade to 6.2
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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...

Views

365

Likes

0

Replies

0
Re: AEM 6.1 SP1 in place upgrade to 6.2
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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.

Views

4.1K

Like

1

Replies

2
Re: AEM 6.1 SP1 in place upgrade to 6.2
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
Not sure if this is what you meant by the left rail menu. I don't believe this is the new 6.2 Menu. Please see attached.

Views

4.1K

Like

1

Replies

4
Re: AEM 6.1 SP1 in place upgrade to 6.2
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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

Views

4.1K

Like

1

Replies

6
Re: AEM 6.1 SP1 in place upgrade to 6.2
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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_...

Views

4.1K

Like

1

Replies

0
AEM 6.1 SP1 in place upgrade to 6.2
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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

Views

5.0K

Likes

0

Replies

10
Re: Receiving 500 Error and not able to author alt tags or update images
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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...

Views

1.2K

Likes

0

Replies

0
Re: Receiving 500 Error and not able to author alt tags or update images
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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...

Views

1.2K

Likes

0

Replies

0
Re: Receiving 500 Error and not able to author alt tags or update images
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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.

Views

1.2K

Likes

0

Replies

0
Receiving 500 Error and not able to author alt tags or update images
Avatar

weba78885530

weba78885530
- Adobe Experience Manager
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....

Views

1.7K

Like

1

Replies

5
Likes from