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

jonnow
Community profile jonnow Level 2
Job title here
Location here
7 BADGES
Level 2

Level 2

Learn more
Joined the community 10-06-2017 5:24:08 PM
Offline
Top badges earned by jonnow
Customize the badges you want to showcase on your profile
Re: Ignoring ordered property jcr:content/metadata/dc:title of type STRINGS for path /content/dam/sample.pdf as multivalued ordered property not supported
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
JaideepBrar​No, OOTB dc:title for files like pdf when imported are stored as String[]And there is no easy way to change it to String unless you write a custom script.Anyone got solution for this?

Views

2.5K

Like

1

Replies

0
Re: AEM-6.4 | Page property | Image drag drop issues
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Yes I can see they have added this in 6.4 SP and 6.5, but why would they not offer the same asset picker button for dialog components like fileupload? Instead the component is hardcoded to be tied with the page thumbnail which seems like a wasted opportunity.Right now, if you opened a component dialog with the left rail closed, or if you switch to full screen mode, you cannot drag an asset into a fileupload dialog!

Views

7.2K

Likes

0

Replies

0
Re: AEM 6.3.2 package manager file names replaced with random UUID
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
You need to add a name and group to that xml.

Views

2.0K

Likes

0

Replies

0
Re: Dispatcher CORS configuration - gap in documentation
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Hey pretty much, except you don't need step 2.Caching the headers does nothing here.

Views

10.3K

Like

1

Replies

0
Re: Dispatcher CORS configuration - gap in documentation
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Hi DorianHallward, I got it to work by adding this config to apache. Basically, if the request has origin from any of your whitelist domains, it will rewrite the header on the spot to allow that origin. The domain regex should match what you have in com.adobe.granite.cors.impl.CORSPolicyImpl.xml. SetEnvIfNoCase Origin "https?://.*\.(origin1.com|origin2.com|origin3.com)$" ACAO=$0 Header set Access-Control-Allow-Origin %{ACAO}e env=ACAO

Views

10.3K

Likes

2

Replies

2
Re: Dispatcher CORS configuration - gap in documentation
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
I am facing the exact same issue. There is a css that is used by multiple domains and CORS policy is requires on font files. Works when serving the font file from publisher but not after it gets cached on dispatcher.Followed the same docs advising to add origin header cache on the dispatcher.Rather useless because it will only cache the first origin header and causes all other subsequent origins to be blocked.Is this a limitation of the dispatcher?

Views

10.3K

Likes

0

Replies

3
Re: Is it possible to setup HTTP2 with AEM6.3?
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Do staff just blindly copy Adobe help links? That article does not help the original poster at all.Try here instead:https://httpd.apache.org/docs/2.4/howto/http2.html

Views

838

Like

1

Replies

0
Re: AEM 6.3.2 package manager file names replaced with random UUID
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Resolved: It seems there was an undocumented change in 6.3.2 where if a package name and group are not defined in the vault/properties.xml, it will give the package a random name and path.

Views

2.0K

Likes

0

Replies

2
AEM 6.3.2 package manager file names replaced with random UUID
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Since updating to 6.3.2, newly uploaded packages are given a random name and path such as "pack_9596c422-dbeb-4ae3-8d41-69cf96181ef6.zip" rather than using the file name of the zip file. Very easy to reproduce: just go into package manager and upload a package.We use a lot of curl scripts to manage and replicate packages and needless to say, they are all broken.Is this a bug? Is there a workaround?

Views

2.3K

Likes

0

Replies

3
Re: Upgrade to AEM 6.3 : Closed unclosed ResourceResolver ;Unclosed ResourceResolver was created
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
This is an issue and is listed as fixed in the latest fix pack release notes. Ticket was listed as CQ-4209018 which isn't even the same as the one raised by the adobe rep in this thread. Makes me wonder do adobe support check open tickets before giving advice. Adobe Experience Manager Help | Release Notes: AEM 6.3 Cumulative Fix Pack

Views

3.7K

Likes

0

Replies

0
Re: Upgrade to AEM 6.3 : Closed unclosed ResourceResolver ;Unclosed ResourceResolver was created
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Thank you Feike for raising the ticket.Would be great if anyone can suggest a temporary solution (eg, disabling the SiteCatalystReportRunner) until this is resolved.

Views

3.7K

Likes

0

Replies

0
Re: Upgrade to AEM 6.3 : Closed unclosed ResourceResolver ;Unclosed ResourceResolver was created
Avatar
Give Back 10
Level 2
jonnow
Level 2

Likes

5 likes

Total Posts

12 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 5
View profile
jonnow
- Adobe Experience Manager
Hi Feike, not sure why this was marked correct but suppress the log does not fix anything. There seems to be a potential memory leak in SiteCatalyst report runner.

Views

3.7K

Likes

0

Replies

0