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

bkowalk11
bkowalk11
Offline

Badges

Badges
10

Accepted Solutions

Accepted Solutions
2

Likes

Likes
7

Posts

Posts
9

Discussions

Discussions
2

Questions

Questions
7

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by bkowalk11
Customize the badges you want to showcase on your profile
Re: AEM process spiking after running version comparison
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
We're on AEM 6.4. And correct, they all seem to be INFO or unrelated WARN level messages. Noticed a traversal warning on line 20 here (this is the log at the very start of the error happening). Does that help with any clues? Here's that line separated out so you don't have to hunt:06.12.2019 14:41:00.258 *WARN* [Thread-108] org.apache.jackrabbit.oak.plugins.index.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select e.[jcr:path] as [jcr:path], e.[jcr:score] as [jcr:score]...

Views

3.0K

Likes

0

Replies

0
Re: 403 error when saving in crx/de
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
Wanted to add an update here in case anyone else sees the same thing. This was actually because we recently moved our AEM instances behind CloudFlare so that we can block any malicious traffic. The CloudFlare WAF has a function in place for XSS that blocks POST requests that include a tag. We disabled that function and all is well. Hopefully that helps some random person out there!

Views

602

Likes

0

Replies

0
AEM process spiking after running version comparison
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
Hoping someone has seen this before.If we try to explore doing a revert by doing a past version preview on any page in our system, we see a massive server spike for several hours as the logs fill with messages like this, for every single page on the server. Not even just child pages - just seems that clicking "preview" on any version of anything causes the server to suddenly rethink its entire life Makes the version preview feature entirely fail for us, obviously... even if we let it run through...

Views

3.1K

Likes

0

Replies

5
Re: 403 error when saving in crx/de
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
Well, never mind. Looks like the issue only shows up when we're using AEM author through a dispatcher instance. Not sure what on the dispatcher is stripping out those scripts, but it doesn't look like this is an AEM problem. Never mind! Closing my question. Thanks!

Views

594

Likes

0

Replies

0
Re: 403 error when saving in crx/de
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
I'm in AEM 6.4.0

Views

601

Likes

0

Replies

0
403 error when saving in crx/de
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
As part of debugging, I'll sometimes make a quick change to a component HTL file in CRX/DE. Lately, however, whenever I try to save an HTL file that includes a tag anywhere in it, I get back the error "Could not save changes. Received 403 () for saving changes in workspace crx.default. Unknown error (Error Code: 403)".I've noticed, further, that I can't add an HTML file to the DAM that has a <script> tag in it, or create that type of file anywhere on the system in CRX/DE and try to save. Seems like anywhere on the system, if I'm uploading HTML with JS in it, AEM gets angry. I can only deploy these types of files in packages right now. Remove the script tags from the files, and all of the above cases are solved. But this doesn't help our broken workflow for files that need scripts in them. Which is... you know... somewhat often... Has anyone seen this behavior before? Is there a security rule somewhere that somehow got switched on?Thanks in advance!

Views

972

Likes

0

Replies

5
Re: AEM 6.3 Touch UI RTE not showing all features for all users
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
I think it could probably happen similarly to any of the config nodes.Seems to have been an issue with the permissions set with our contentimport when we moved to 6.3. We’ve found a few other weird permissionsissues, so we just keep this in mind when checking things now.Good luck!On Tue, Nov 21, 2017 at 5:53 AM dixitp96985602

Views

1.1K

Likes

0

Replies

0
Re: AEM 6.3 Touch UI RTE not showing all features for all users
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
Super strange solution that Daycare helped us find - if you browse all the way down our /apps/ tree in crxde until you get to the actual rtePlugins node from up above and then switch to the permissions tab and explicitly grant read access to the content-authors group, it fixes the issue. Seems to be an issue with AEM not carrying the content-authors access to the parent /apps/ folder down to that specific node. Not sure of the cause yet, but we were able to reproduce on a vanilla instance in we....

Views

1.1K

Likes

3

Replies

0
AEM 6.3 Touch UI RTE not showing all features for all users
Avatar
Give Back 5
Level 2
bkowalk11
Level 2

Likes

7 likes

Total Posts

9 posts

Correct reply

2 solutions
Top badges earned
Give Back 5
Ignite 3
Give Back 3
Validate 1
Ignite 1
View profile
bkowalk11
- Adobe Experience Manager
Our text component's RTE has a few extra style options and source mode enabled. When I log into the system as an administrator, they display fine. When our authors (content-authors group with full read/write/replicate access to the content folder, among other things) log in, though, they're not able to see the additional buttons. The RTE only displays in its default layout. I've tried unlocking read access to the whole tree and even that doesn't seem to fix it... nothing short of adding them to ...

Views

4.0K

Likes

4

Replies

6