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

arturl43391132
arturl43391132
Offline

Badges

Badges
23

Accepted Solutions

Accepted Solutions
10

Likes Received

Likes Received
22

Posts

Posts
71

Discussions

Discussions
5

Questions

Questions
66

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by arturl43391132
Customize the badges you want to showcase on your profile
Re: 403 forbidden on the request /bin/wcm/contentfinder/asset/view.html/content/dam/... - Adobe Experience Manager 09-12-2021
Hi @Ravi_Pampana,Thanks for your reply. The situation is that unfortunately I don't have permissions to check error.log. In addition this is the author instance. But anyway I'll forward it to our DevOps team who has direct access to it and they will check. Thanks.

Views

128

Like

1

Replies

0
403 forbidden on the request /bin/wcm/contentfinder/asset/view.html/content/dam/... - Adobe Experience Manager 08-12-2021
Hello AEM Community! We're facing the strange issue - 403 Forbidden only in one instance when we open assets menu in the Toggle Side Panel:What can be the problem with permissions and how to solve it? Any ideas? Thx a lot in advance.

Views

176

Likes

0

Replies

2
Show different content for anonymous and authenticated users - Adobe Experience Manager 18-10-2021
Hello AEM Community, AEM - 6.5 Could you please share ideas / best practises how to implement the following solution on AEM pages: We need a component with 2 parsyses - "preview content" and "exclusive content". "preview content" should be visible for all users."exclusive content" should be hidden from anonymous users and instead of it they should see "sign-in" form. And authenticated users should see exclusive content fully. Users are not associated with aem, but with another service where they...

Views

176

Likes

0

Replies

4
Re: UI for /etc/importers/polling.html doesn't work - Adobe Experience Manager 31-03-2021
Hi @vanegi. Thanks for your answer.

Views

375

Like

1

Replies

0
Re: UI for /etc/importers/polling.html doesn't work - Adobe Experience Manager 05-01-2021
Hi @shelly-goel, Thanks for your answer. It seems that you're right.

Views

490

Like

1

Replies

0
Re: UI for /etc/importers/polling.html doesn't work - Adobe Experience Manager 05-01-2021
Hi @Ankur_Khare, Thanks for your answer. And do you see any errors in the console? Can you perform any actions in this menu? Thanks.

Views

490

Like

1

Replies

0
UI for /etc/importers/polling.html doesn't work - Adobe Experience Manager 28-12-2020
Hello AEM Community, We have a strange trouble with UI for /etc/importers/polling.html:As you can see, there is a blank screen. But importers exist under this path: So there is no possibility to manage importers, add new and so on. Do you have any ideas what the problem can be? AEM 6.5. Thanks.

Views

645

Likes

0

Replies

6
Components aren't allowed to add, drag / drop them in one targeting audience but allowed in other audiences and even in default - Adobe Experience Manager 09-12-2020
Hello Adobe Community,AEM 6.5 We have a strange problem regarding targeting on the page. We have default audince and custom named, e.g. Custom Audience.The problem is that components aren't allowed to insert in targetparsys, drag and drop them, but everything is okay in default audience.Custom audience:Default audience:As you can see there is no "+" on dialog.And at the same time on other pages different audiences work good. Could you please say what the problem can be? Thanks in advance.

Views

258

Likes

0

Replies

0
Re: Allowed components in design mode 6.5 for static temp... - Adobe Experience Manager 09-12-2020
But anyway the answer of @Kiran_Vedantam was useful, we just returned these 2 allows under /etc/designs.

Views

808

Likes

0

Replies

0
Re: Allowed components in design mode 6.5 for static temp... - Adobe Experience Manager 09-12-2020
Hi @Mariia_Lukianet. Thanks for your answer. Of course we updated cq:designPath-s of our pages, but they have value - /apps/settings/wcm/designs/{projectName}. Under default node we have just 2 nodes which allows 2 components for 2 templates.

Views

811

Likes

0

Replies

0