Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

I can't find my form:ready script so I can remove it

Avatar

Level 4

At one time, I thought I wanted to have a message box pop up when the form opened, but now I see how that feature can quickly become very annoying so I would like to remove it. Unfortunately, I can't find it. Wow. That sounds really stupid.  Anyway, I hope some kind person can tell me how to locate this scrip in the scrip viewer so I can delete it.

Form is attached. Thanks!

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

If you click on the form1 node in the hierarchy then select "Events with Scripts" then the editor will show you all of the scripts on your form (see the image bleow). I highlighted the section where that message is coded.

Paul

Capture.GIF

View solution in original post

4 Replies

Avatar

Correct answer by
Former Community Member

If you click on the form1 node in the hierarchy then select "Events with Scripts" then the editor will show you all of the scripts on your form (see the image bleow). I highlighted the section where that message is coded.

Paul

Capture.GIF

Avatar

Level 4

How do I delete it? I highlighted it, right clicked and 'cut' but it didn't go away. I can't seem to get rid of it by backspacing through it or anything either.

Avatar

Former Community Member

Just add a // to the beginning of the code. You cannot change the line above it as it is a descripter that tells you where the code

is. That turns it into a comment.

Paul

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----