aliaksandr_hvozdzeu

Adobe Experience Manager

Adobe Campaign Classic

Adobe Campaign Standard

Adobe Experience Platform

Adobe Analytics

Adobe Audience Manager

Adobe Target

Adobe Experience Cloud

Adobe I/O Cloud Extensibility

Adobe Advertising Cloud

Marketo

Magento

Adobe Creative Cloud

Adobe Document Cloud

Workfront, an Adobe company

since

‎18-03-2021

Level 1

Re: An error occurred while saving any configuration. - Adobe Experience Manager

I found the reason. The configuration was saved under a dedicated path when installing aem.And when adding a new configuration an error appeared.Removing the new configuration and adding the org.apache.felix.proxy.load.balancer.connection.enable true property helped to resolve this issue.Thanks all.

Re: An error occurred while saving any configuration. - Adobe Experience Manager

A bit more information. This error appeared after switching to HTTPS and closing the Felix console. The transition was made according to the instructions: https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/ssl-by-default.html

213

Re: An error occurred while saving any configuration. - Adobe Experience Manager

Any ideas?

233

Re: An error occurred while saving any configuration. - Adobe Experience Manager

There are no errors in the logs and all bundles are active. I cannot understand why it is loaded as HTTP if AEM works throw HTTPS

193

An error occurred while saving any configuration. - Adobe Experience Manager

Good day. Please help me figure out the error. When saving any configuration, I get an error (like in the picture). In this case, the configuration is saved, but the error is still there. What could be the reason? Also, I got this error in the consoleThank you very much in advance! PS AEM 6.5.6 version

297

Re: AEM 6.5 view payload - Adobe Experience Manager

Also, how I understand, View Payload works only for "physical" files like image, html etc. And path which presented in image below is wrong.

Re: AEM 6.5 view payload - Adobe Experience Manager

Thanks, I can find filter which processes this requests. Thanks.

130

AEM 6.5 view payload - Adobe Experience Manager

Hello In AEM 6.5 in the history of workflows, it became possible to view the payload. The problem is that after the image is loaded into the AEM assets, the images are rendered automatically. I can't see the payload if there is (/jcr:content/metadata/) in the path and I get a 403 error.Can you please suggest what is the reason or share useful links. Thank you very much in advance.

162

Re: Incorrect component operation after the AEM version u... - Adobe Experience Manager

Hello, I found an interesting point.In SP 6.5.6 file by path /libs/cq/gui/components/authoring/dialog/dropdownshowhide/clientlibs/dropdownshowhide/js/dropdownshowhide.js was updated and have a new method: Coral.commons.ready(function () { showHideHandler($(".cq-dialog-dropdown-showhide", e.target)); });If I leave only showHideHandler($(".cq-dialog-dropdown-showhide", e.target)); my component works as expected. What could have caused this?

172

Re: Incorrect component operation after the AEM version u... - Adobe Experience Manager

I followed your advice, but it didn’t work. I still have this problem. Can you double-check my code please. (function(document, $) { 'use strict'; // When dialog gets injected $(document).on('dialog-data-ready', function(e) { $('.cmp-box--editor coral-select.cq-dialog-dropdown-showhide', e.target).each(function(i, element) { // Show or hide touch UI Dialog components var target = $(element).data('cqDialogDropdownShowhideTarget'); if (target) { Coral.commons.ready(element, function(component) { /...

217

Re: Incorrect component operation after the AEM version u... - Adobe Experience Manager

I am getting the following

183

Incorrect component operation after the AEM version upgrade - Adobe Experience Manager

I ran into a specific issue in a component after upgrading from 6.3 to 6.5.6. The component has after which 1 of 3 options is selected, and depending on which value is selected, another field should be displayed. At 6.3 there are no problems with this, after the upgrade to 6.5 the field is no longer displayed. All this in the component dialog box. The component has not changed. I noticed that the style has "hide" and it should disappear, but it doesn't. We have AEM version 6.5.6. I installed 6.5...

294

Re: Problems with the component after the AEM upgrade. - Adobe Experience Manager

Any ideas? I don't know where to look anymore.

273

Re: Problems with the component after the AEM upgrade. - Adobe Experience Manager

I'm sorry, I misled you. We have AEM version 6.5.6. I installed 6.5 myself and tested it and the component works. Then I installed service pack 6.5.6 and the component stopped working. This is a problem in the service pack. But I don’t understand why. 6.5.66.5

383

Re: Problems with the component after the AEM upgrade. - Adobe Experience Manager

Yes, I did that, but it did not help. Could something affect this component from outside? For example javascript?

394

Re: Problems with the component after the AEM upgrade. - Adobe Experience Manager

Thanks a lot, but it didn't help (

418

Re: Problems with the component after the AEM upgrade. - Adobe Experience Manager

Very strange. What do you think, why might it not work?

214

Re: Problems with the component after the AEM upgrade. - Adobe Experience Manager

Hide / open this field does not work. And this field should change.

256

Re: Problems with the component after the AEM upgrade. - Adobe Experience Manager

Hi, Perhaps a javascript is used for this, which handles this. (function(document, $) {'use strict';// When dialog gets injected$(document).on('foundation-contentloaded', function(e) {$('.cmp-box--editor coral-select.cq-dialog-dropdown-showhide', e.target).each(function(i, element) {// Show or hide touch UI Dialog componentsvar target = $(element).data('cqDialogDropdownShowhideTarget');if (target) {Coral.commons.ready(element, function(component) {// If there is already an inital value make sure...

283

Problems with the component after the AEM upgrade. - Adobe Experience Manager

Hey. I ran into a specific issue in a component after upgrading from 6.3 to 6.5. The component has after which 1 of 3 options is selected, and depending on which value is selected, another field should be displayed. At 6.3 there are no problems with this, after the upgrade to 6.5 the field is no longer displayed. All this in the component dialog box. The component has not changed. I noticed that the style has "hide" and it should disappear, but it doesn't. Please help with any information as pos...

596

Re: Image component is not showing save button - Adobe Experience Manager

Of course! Incorrect property. My inattention. Thank you very much.

166

Re: Image component is not showing save button - Adobe Experience Manager

This only happens with this component. There is also a component identical to this, it differs only in 1 property - component group, but version 2 works correctly.

197

Re: Image component is not showing save button - Adobe Experience Manager

I remember the ability to drag and drop images. I am interested in the moment why the buttons are not displayed. Why did it become so? cq dialog xml.

212

Image component is not showing save button - Adobe Experience Manager

Hey. After upgrading the version from 6.3 to 6.5, buttons no longer displayed in the component dialog window.And they have the "hidden" attribute in HTML. It's a customer component. What could be the reason?

291

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences