Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

aliaksandr_hvozdzeu
Community profile aliaksandr_hvozdzeu Level 3
AEM Developer
Minsk
15 BADGES
Level 3

Level 3

Learn more
Joined the community 30-10-2020 4:18:52 AM
Online
Top badges earned by aliaksandr_hvozdzeu
Customize the badges you want to showcase on your profile
Re: Component deletion triggers error message
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Thanks all for your help. I fixed this issue. The problem was that in our class we were receiving an invalid resource from a request to delete a component.It was enough to change fromResource resource = request.getResource();toResource resource = context.getRequest().getResource();in extended ContentHandlerBasedTransformer

Views

85

Like

1

Replies

0
Re: Component deletion triggers error message
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
No I didn't. But this issue triggired on all custom components.

Views

101

Like

1

Replies

0
Re: Component deletion triggers error message
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
One note. I see 500 request error in the POST delete request. 

Views

128

Like

1

Replies

0
Re: Component deletion triggers error message
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
 

Views

129

Like

1

Replies

0
Component deletion triggers error message
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
HelloCould you please tell me with such an error that appeared after applying the service package +6.5.4?When deleting a component in author we're getting an error message (see attached image). The component also stays on the page until we do a manual refresh of the page. Deleting a component deletes it from the page without triggering a error message and without requiring a page refresh. Steps to reproduce:Add a component to the pageDelete itNotice the error message at the top of the pageNotice...

Views

197

Likes

0

Replies

7
Re: javax.jcr.InvalidItemStateException when when I remov...
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
I am performing a component removal on a web server on the author. Steps to reproduce:Add a component to the pageDelete itNotice the error message at the top of the pageNotice the component isn't deletedRefresh the pageNotice the component is deleted.But in the CRX can see that the component has been removed.However, if I do this on a local Instance, I don't see such an error.

Views

212

Like

1

Replies

0
Re: javax.jcr.InvalidItemStateException when when I remov...
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
No, nothing like that. This message appears for any component and appeared after the version update from 6.5.6 to 6.5.8.

Views

219

Like

1

Replies

0
javax.jcr.InvalidItemStateException when when I remove the component.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Hello.Guys, please tell me. What could be causing this error?I add a component to a page and when I remove it I get an error.To work further I have to reload the page.There is an error in the logs:All bundles are active. AEM version 6.5.8Very grateful in advance.

Views

267

Likes

0

Replies

5
Re: An error occurred while saving any configuration.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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.

Views

270

Like

1

Replies

1
Re: An error occurred while saving any configuration.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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

Views

398

Likes

0

Replies

0
Re: An error occurred while saving any configuration.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Any ideas?

Views

418

Likes

0

Replies

0
Re: An error occurred while saving any configuration.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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

Views

357

Likes

0

Replies

0
An error occurred while saving any configuration.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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

Views

482

Likes

0

Replies

8
Re: AEM 6.5 view payload
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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.

Views

183

Likes

0

Replies

0
Re: AEM 6.5 view payload
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Thanks, I can find filter which processes this requests. Thanks.

Views

223

Likes

0

Replies

0
AEM 6.5 view payload
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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.

Views

255

Likes

0

Replies

3
Re: Incorrect component operation after the AEM version u...
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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?

Views

374

Likes

0

Replies

0
Re: Incorrect component operation after the AEM version u...
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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) { /...

Views

419

Likes

0

Replies

0
Re: Incorrect component operation after the AEM version u...
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
I am getting the following

Views

373

Likes

0

Replies

0
Incorrect component operation after the AEM version upgrade
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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...

Views

500

Likes

0

Replies

6
Re: Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Any ideas? I don't know where to look anymore.

Views

541

Likes

0

Replies

0
Re: Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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

Views

651

Likes

0

Replies

0
Re: Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Yes, I did that, but it did not help. Could something affect this component from outside? For example javascript?

Views

662

Likes

0

Replies

0
Re: Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Thanks a lot, but it didn't help (

Views

688

Likes

0

Replies

0
Re: Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Very strange. What do you think, why might it not work?  

Views

472

Likes

0

Replies

0
Re: Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Hide / open this field does not work. And this field should change.

Views

514

Likes

0

Replies

0
Re: Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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...

Views

541

Likes

0

Replies

0
Problems with the component after the AEM upgrade.
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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...

Views

886

Likes

0

Replies

13
Re: Image component is not showing save button
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- Adobe Experience Manager
Of course! Incorrect property. My inattention. Thank you very much.

Views

321

Likes

0

Replies

0
Re: Image component is not showing save button
Avatar
Validate 1
Level 3
aliaksandr_hvozdzeu
Level 3

Likes

8 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
aliaksandr_hvozdzeu
- 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.

Views

363

Likes

0

Replies

0
Likes given to
Likes from