alt text field is not working in cloud env 6.5 | Community
Skip to main content
New Participant
May 15, 2022
Solved

alt text field is not working in cloud env 6.5

  • May 15, 2022
  • 3 replies
  • 1398 views

Hi,

 

I have created a header banner component in that when I select background type image alt text is required when we submit dialog it as to show error message but it is submitting without error. 

Note: Same code is working on 6.5 env when we push the code in cloud env validation is not working.

 

Please can anyone help with this?

 

@14414417 @kautuk_sahni 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SantoshSai

Hi @naveen_27_05 

 

Yes, as per stated in above link and issue was already raised to Adobe.

 

Thanks!

3 replies

Jagadeesh_Prakash
New Participant
May 16, 2022

@nave_27  Is this OOTB component that you are referring to? Can you please make sure you are using coral reference in your dialog 

New Participant
May 16, 2022

Hi Jagadeesh,

 

no I am not referring any OOTB component and I am not using any coral reference in the dialog.

 

Thanks.

 

Regards,

Naveen.

 

 

 

 

MayurSatav
New Participant
May 16, 2022

Hi @nave_27 ,

 

If it is working in on-premise versions and not on the cloud then it is a bug. You can raise an adobe support ticket or simply extend the component. Hide the existing field for alt text and add a new field explicitly for the same.

SantoshSai
New Participant
May 16, 2022

Dear @nave_27 

I found similar issue here saying product issue, https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-as-cloud-mandatory-fields-not-working-when-there-are/td-p/438905

worth checking above link might helps.

 

Regards,

Santosh

 

Santosh Sai
New Participant
May 16, 2022

Hi Santosh,

 

I have seen the link. I think it's an product issue.

 

Thank you.

 

SantoshSai
SantoshSaiAccepted solution
New Participant
May 16, 2022

Hi @naveen_27_05 

 

Yes, as per stated in above link and issue was already raised to Adobe.

 

Thanks!

Santosh Sai