[Resolved] Conditional Block – check for form submittal using either: null or ''

[Author]

Posts

[GamX]

Hello, I'm using Conditional Blocks in the advanced editor to check for whether the user has submitted a user form or not. As per previous Toolset guidance, I was using these search parameters:

To show content if user has not yet submitted a form: ( '[wpv-search-term param="_success"]' eq '' )
To show content if user has submitted a form: ( '[wpv-search-term param="_success"]' ne '' )

This worked when I was using Toolset Views, but since I upgraded to Toolset Blocks, I get an error message in the RH column under where it gives a summary of the conditions specified in the editor:

If I use either of the above statements, I get this error message: "Incomplete condition"

In spite of this error, on the user end the view is as expected. But because my condition isn't listed in the summary, it's hard to troubleshoot without going into every single block to check my code.

HOWEVER...
If I instead use this statement:
( '[wpv-search-term param="_success"]' eq null )
I get this message: "Search term is equal to null."

Or if I use this statement:
( '[wpv-search-term param="_success"]' ne null )
I get this message: "Search term is not equal to null."

Because I just randomly tried this without knowing if it was a correct approach, can you please confirm that this approach is okay for use in the Advanced Editor? I don't want to run into any other problems.

Thanks!

[Waqar Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)]

Hi,

Thank you for contacting us and I'd be happy to assist.

To add conditional checks based on the value of a URL parameter '_success', I'll recommend using these expressions:

To check if the value is empty:

( empty( '[wpv-search-term param="_success"]') ) 

To check if the value is not empty:

( NOT(empty( '[wpv-search-term param="_success"]')) ) 

I hope this helps and please let me know if you need any further assistance around this.

regards,
Waqar

[GamX]

Hi thanks for the reply... the first statement above seems to work:
( empty( '[wpv-search-term param="_success"]') )

However, when I plug in the second statement into the conditional block's advanced editor and click the "Accept" button, it strips out the "NOT" so instead of this:
( NOT(empty( '[wpv-search-term param="_success"]')) )

It converts itself to this after I click "Accept":
( empty( '[wpv-search-term param="_success"]') )

[Waqar Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)]

Thanks for writing back.

You can slightly update the conditional check for the 'not empty' case so that the 'NOT' is outside the brackets:

NOT( (empty( '[wpv-search-term param="_success"]')) ) 

This should do the trick.

[GamX]

Hi... I tried the revised NOT statement...
NOT( (empty( '[wpv-search-term param="_success"]')) )

...but when I click the "Accept" button in the Advanced Editor, now I get the following error message (in the yellow highlighted area above the code):
"Please, complete all the conditions or remove them."

[GamX]

Hello, after more testing, the revised NOT statement is now yielding the same effects as before.

This is now the only content in the Advanced Editor of the Conditional Block:
NOT( (empty( '[wpv-search-term param="_success"]')) )

But when I click the "Accept" button, it changes the statement to this:
( empty( '[wpv-search-term param="_success"]') )

Ideally I want to combine other conditions using AND/OR with this empty or not empty condition, but I need to get this simple statement working first. Grateful for any help to resolve this!

[Waqar Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)]

I've tested these conditions again, but could't reproduce this behaviour, as can be seen in this screencast:
hidden link

I'm sharing the exact conditional statements that I've used in my tests:

Empty:

  ( empty( '[wpv-search-term   param="_success"]') ) 

Not Empty:

 NOT ( empty( '[wpv-search-term   param="_success"]') ) 

In case the issue still persists, you're welcome to share temporary admin login details, along with the link to an example page with these conditional blocks.

Note: Your next reply will be private and please make a complete backup copy, before sharing the access details.

[GamX]

SUMMARY of what works and what doesn't, including submission of a specific form (ID 3100)

Each of these conditional statements works as expected:
( empty( '[wpv-search-term param="_success"]') )
( empty( '[wpv-search-term param="_success"]') AND ( '[types usermeta="1-1-user-field" output="raw" current_user="true"][/types]' eq '1' ) )
( ( '[wpv-search-term param="_success"]' eq '3100_1' ) )
NOT ( empty( '[wpv-search-term param="_success"]') )
( NOT ( empty( '[wpv-search-term param="_success"]') ) )
( ( NOT ( empty( '[wpv-search-term param="_success"]') ) ) AND ( '[types usermeta="1-1-user-field" output="raw" current_user="true"][/types]' eq '1' ) )
( NOT ( empty( '[wpv-search-term param="_success"]') ) AND ( '[types usermeta="1-1-user-field" output="raw" current_user="true"][/types]' eq '1' ) )

In Advanced Editor, the following result in an error in yellow highlighted area: “Please, complete all the conditions or remove them":
( NOT(empty( '[wpv-search-term param="_success"]’) ) )
NOT( (empty( '[wpv-search-term param="_success"]’) ) )
( '[wpv-search-term param="_success"]' = ‘3100_1’ )

Renders as expected on front end, but when conditional block is selected in the Gutenberg Block Editor, the note in RH column says: “incomplete condition”:
( ( '[wpv-search-term param="_success"]' eq '' ) )
( ( '[wpv-search-term param="_success"]' ne '' ) )