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

paul_bjorkstran
paul_bjorkstran
Offline

Badges

Badges
5

Accepted Solutions

Accepted Solutions
0

Likes

Likes
4

Posts

Posts
7

Discussions

Discussions
3

Questions

Questions
4

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by paul_bjorkstran
Customize the badges you want to showcase on your profile
Re: -- As I understand the release of 6.5.5 and 6.4.8.1 have...
Avatar
Give Back 5
Level 2
paul_bjorkstran
Level 2

Likes

4 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
paul_bjorkstran
- Adobe Experience Manager
FYI @aemmarc , a colleague has confirmed that 6.5.5 does not contain the fix. He needed to reapply the hotfix over 6.5.5.

Views

3.5K

Like

1

Replies

0
Re: -- As I understand the release of 6.5.5 and 6.4.8.1 have...
Avatar
Give Back 5
Level 2
paul_bjorkstran
Level 2

Likes

4 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
paul_bjorkstran
- Adobe Experience Manager
@aemmarc , if that is the case (which would be awesome, by the way!) it would be a good idea to get that details added to the SP release notes:https://docs.adobe.com/content/help/en/experience-manager-65/release-notes/service-pack/sp-release-notes.html Thanks for the information!

Views

5.6K

Like

1

Replies

0
Re: Package Manager suddenly stop working in Chrome or Chromium based browers? See Hotfix here
Avatar
Give Back 5
Level 2
paul_bjorkstran
Level 2

Likes

4 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
paul_bjorkstran
- Adobe Experience Manager
@aemmarc , do you know if the hotfix will be able to be applied over 6.5.5 (I ask since 6.5.5 came out today)?

Views

5.9K

Like

1

Replies

3
Re: Dispatcher | Last-Modified attribute missing in response header
Avatar
Give Back 5
Level 2
paul_bjorkstran
Level 2

Likes

4 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
paul_bjorkstran
- Adobe Experience Manager
Just a quick addendum for those who are searching for this. Since Dispatcher 4.1.11, response headers can now be cached by the dispatcher and served when requesting cached items. See https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html#caching-http-response-headers for more information.

Views

691

Like

1

Replies

0
Re: Enhancements to AEM to support restricted user permissions
Avatar
Give Back 5
Level 2
paul_bjorkstran
Level 2

Likes

4 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
paul_bjorkstran
- Adobe Experience Manager
This can be done with normal path-based ACLs, but you need to allow more than just access to cq:annotations.EDIT: I forgot to mention, the permissions below are on the /content node as allow with jcr:read & rep:write base permissions, and restrictions based on the lists below.You need to allow write for the following rep:globs/*/cq:annotations/*/cq:annotations/*You also need to allow write for the following rep:itemNamescq:lastModifiedcq:lastModifiedByI also added these rep:itemNames for good me...

Views

1.5K

Likes

0

Replies

0
Re: AEM 6.1 & Java 1.8 Bytecode Verification Error - Constructor must call super() or this() before return
Avatar
Give Back 5
Level 2
paul_bjorkstran
Level 2

Likes

4 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
paul_bjorkstran
- Adobe Experience Manager
I appreciate the help, Steve. Hopefully you are able to look further than the public dependencies in Adobe's Nexus repo. I tested against all 6.1 variants (6.1.0, 6.1.0-SP1, and 6.1.0-SP1-B0001) and all fail with the same verification error.Saying you are Java 8 compatible and not letting developers use Java 8 is like Microsoft saying "Excel runs on Windows 10, but if you want to use formulas, you need to use windows XP". I do understand that you can get the unobfuscated jar, but my current clie...

Views

577

Likes

0

Replies

0
Re: AEM 6.1 & Java 1.8 Bytecode Verification Error - Constructor must call super() or this() before return
Avatar
Give Back 5
Level 2
paul_bjorkstran
Level 2

Likes

4 likes

Total Posts

7 posts

Correct reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
paul_bjorkstran
- Adobe Experience Manager
smacdonald2008 wrote... [Workaround]:- As a test - try using JDK 7 - lets see if its a JDK issue. Let us know what happens. Please open a ticket on this. If there is a bug - you need to report this to support so it can move up the chain to Eng team so it can be fixed. https://helpx.adobe.com/marketing-cloud/contact-support.html TBH, that isn't really a reasonable approach. The documentation says that Java 8 is supported (https://docs.adobe.com/docs/en/aem/6-1/deploy/technical-requirements.html#J...

Views

577

Likes

0

Replies

0
Likes given to
Likes from