since ‎04-10-2018
‎12-03-2020
yellar5366253
Level 2
Instead of tinkering with the AEM platform, you can as a...
Avatar

BrianKasingli

MVP

BrianKasingli
- Adobe Experience Manager
Instead of tinkering with the AEM platform, you can as a test, try tinkering with the basePage template. Within your basePage template, you can add HTML and CSS like so: .extra-author-buttons { position: absolute; top: 50px; left; 50px; background-color: red; } </script> <div class="extra-author-buttons"> <a href="${currentPage.path + '?groupName=groupone'">View Group One</a> <a href="${currentPage.path + '?groupName=grouptwo'">View Group Two</a> </div> </sly> Hope this helps.</sly> Hope this helps.

Views

2.3K

Like

1

Replies

0
Re: Pathfield search not working properly on AEM 6.3
Avatar

JeroenDruwe

JeroenDruwe
- Adobe Experience Manager
Is there a solution, also experiencing the same on 6.4

Views

5.0K

Likes

0

Replies

0
Re: Migration from 6.2 to 6.4- AEM 6.4 Upgrade - Paste button displayed twice in toolbar of Sites after copying a page
Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008
- Adobe Experience Manager
This is not typical AEM behavior. Can you please describe your customizations in more detail. I suspect that something done is responsible here.

Views

641

Likes

0

Replies

0
Re: Migration project 6.2 to 6.4 : Name of the renditions are displyed twice like example name.name.png
Avatar

Gaurav-Behl

MVP

Total Posts

1.1K

Likes

226

Correct Answer

281
Gaurav-Behl
- Adobe Experience Manager
I think that the double filename is generated from the custom step of updateasset workflow where you add suffix to the generated renditions.Could you check filename mentioned in the custom step of DAM Update Asset workflow where you've configured suffixes like 'large', 'small' etc. ?something similar to --

Views

1.1K

Like

1

Replies

0
Re: jcr: content nodes don't want to display when browse and search using pathfiled in touch ui dialog
Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
- Adobe Experience Manager
Hello Everyone,The product team is currently working on this issue. The internal reference number is GRANITE-15894 and GRANITE-26358.This has been classified as an enhancement to the product.Regards,Vishu

Views

1.2K

Like

1

Replies

0
Re: Template related tabs Are not visible migrating site 6.2 to 6.4
Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

999

Correct Answer

829
Arun_Patidar
- Adobe Experience Manager
Hi,Can you just inherit from basic page? like below I created demo-page component and inherited the other dialogs from basicpage and created new tab for socialmedia2. if you don't need to do dialog modification don't create q:dialog node for page component.

Views

3.6K

Likes

2

Replies

0
Re: Migration project error
Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K
Jörg_Hoh
- Adobe Experience Manager
Please redo this test and then lookup the request in the "Recent Requests" overview (/system/console/requests); it gives you this information and much more. From the above messages it's not clear to what is not found. The resource itself is accessible (otherwise you should see early that the path is resolved to a NonExistingResource); so I assume that this message is rather caused by some rendering scripts not being present, which can also result in a 404. But the above mentioned view should be ...

Views

1.5K

Likes

0

Replies

0
Re: Migration Error while upgrading to AEM 6.2 from 6.4
Avatar

cquser1

cquser1
- Adobe Experience Manager
Hi Manoj,Do you have any jira /daycare ticket number that was provided to you w.r.t this issue.

Views

6.5K

Likes

0

Replies

0
Re: Deprecated API
Avatar

yellar5366253

yellar5366253
- Adobe Experience Manager
Thanks Peter for your immediate response.

Views

2.3K

Likes

0

Replies

0
Re: Project migration activity
Avatar

PuzanovsP

MVP

PuzanovsP
- Adobe Experience Manager
Dear Yellar,Have a look at AEM Archetype Starter project for 6.4 and ensure you include all of the clientlibs needed to initialize authoring UI also, check that your project has not changed default authoring UI in 6.2. Additionally, please look how Core components work to load Authoring UI Elements[0][0] aem-core-wcm-components/headlibs.html at master · Adobe-Marketing-Cloud/aem-core-wcm-components · GitHub Regards,Peter

Views

3.0K

Likes

0

Replies

0