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

MikeXXXX
MikeXXXX
Offline

Badges

Badges
5

Accepted Solutions

Accepted Solutions
0

Likes

Likes
0

Posts

Posts
10

Discussions

Discussions
2

Questions

Questions
8

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by MikeXXXX
Customize the badges you want to showcase on your profile
Re: I have created a form and it has some input fields an...
Avatar
Ignite 5
Community Advisor
Asutosh_Jena_
Community Advisor

Likes

1,115 likes

Total Posts

1,107 posts

Correct reply

326 solutions
Top badges earned
Ignite 5
Give Back 700
Ignite 3
Give back 600
Give Back 500
View profile
Asutosh_Jena_
- Adobe Experience Manager
Hi @MikeXXXX This could be because of some jquery events which are written based on the form id or name or class which is causing the page to scroll down while clicking on any of the field.To drill down to the exact location of the code where it is coming from you need to remove the JS file that is associated with the component and see which line of code is causing the issue. Thanks!

Views

147

Like

1

Replies

0
Re: I am doing roll out from one page to another and whil...
Avatar
Give Back 800
Community Advisor
Vijayalakshmi_S
Community Advisor

Likes

810 likes

Total Posts

894 posts

Correct reply

292 solutions
Top badges earned
Give Back 800
Affirm 250
Give Back 700
Give back 600
Give Back 500
View profile
Vijayalakshmi_S
- Adobe Experience Manager
Hi @MikeXXXX,I suggest to try the followingCheck similar behavior in we-retail site pages if you have sample content in your instance.Create new logger in OSGI console -> Sling -> Log Support(http://localhost:4502/system/console/slinglog) for com.day.cq.wcm.msm.impl.RolloutManagerImpl and set the level as "DEBUG" -> Trigger rollout and observe the logs.

Views

118

Likes

2

Replies

0
Re: Unable to adapt resource to type com.day.cq.wcm.msm.i...
Avatar
Ignite 5
Community Advisor
Asutosh_Jena_
Community Advisor

Likes

1,115 likes

Total Posts

1,107 posts

Correct reply

326 solutions
Top badges earned
Ignite 5
Give Back 700
Ignite 3
Give back 600
Give Back 500
View profile
Asutosh_Jena_
- Adobe Experience Manager
You need to login with your adobe id and make sure you have the access to raise ticket with Adobe. If you do not have access, please see who else has access in your team to create the ticket. There must be someone who will be able to create ticket for each of the project within organization.

Views

181

Likes

0

Replies

0
Re: Touch UI - Modifying services' properties causes the...
Avatar
Ignite 5
Level 2
MikeXXXX
Level 2

Likes

0 likes

Total Posts

10 posts

Correct reply

0 solutions
Top badges earned
Ignite 5
Give Back 3
Ignite 3
Ignite 1
Give Back
View profile
MikeXXXX
- Adobe Experience Manager
So when I change the property in any service page in classic UI and then publish it the button on the page after publishing is enabled but if I do the same thing in touch UI the button gets disabled

Views

127

Likes

0

Replies

0
Re: When I am clicking on the rollout page it is redirect...
Avatar
Give Back 100
Community Advisor
Pawan_Gupta_
Community Advisor

Likes

153 likes

Total Posts

209 posts

Correct reply

87 solutions
Top badges earned
Give Back 100
Ignite 5
Ignite 3
Give Back 50
Give Back 25
View profile
Pawan_Gupta_
- Adobe Experience Manager
Hello, Did you check the blueprint/livecopy has been configured correctly for your site to rollout?? also, are you using standard rollout or customized it. please refer https://experienceleague.adobe.com/docs/experience-manager-64/administering/introduction/msm-sync.html?lang=en#installed-and-custom-rollout-configurations thanks!!

Views

148

Like

1

Replies

0
Re: when I change the property of page and then I publish...
Avatar
Springboard
Community Advisor
Kiran_Vedantam
Community Advisor

Likes

392 likes

Total Posts

359 posts

Correct reply

108 solutions
Top badges earned
Springboard
Give Back 5
Ignite 1
Affirm 50
Validate 1
View profile
Kiran_Vedantam
- Adobe Experience Manager
Hi @MikeXXXX, You can do the below things to debug:Check the error.logCheck console errorCheck if any mandatory field is not filled in the page propertiesGenerally, the tab which has a mandatory field gets highlightedCheck the font of the property - Ex: page name expects only small lettersHope this helps. Thanks,Kiran Vedantam.

Views

153

Like

1

Replies

0