Skip Navigation

[Resolved] Better to use “eq” or “==” ? And better to use “empty()” or “eq (empty str)” ?

This thread is resolved. Here is a description of the problem and solution.

Problem:

Using [wpv-conditional] shortcode, I am curious if it is better (or matters) to use eq/neq or use ==/!= ?

Also, is there a difference between using empty($wpcf-field-name) or using $wpcf-field-name eq "" ?

Solution:

I suggest you use eq/ne in your [wpv-conditional] shortcodes.

Using empty($wpcf-field-name) or using $wpcf-field-name eq "" are same result, you can use one of them.

Relevant Documentation:

https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-conditional

https://toolset.com/documentation/user-guides/conditional-html-output-in-views/checking-fields-and-other-elements-for-emptynon-empty-values/

This support ticket is created 5 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 3 replies, has 2 voices.

Last updated by Luo Yang 5 years, 11 months ago.

Assisted by: Luo Yang.

Author
Posts
#1160135

Tell us what you are trying to do?
Test for an empty field.

Is there any documentation that you are following?
Views documentation.

I am curious if it is better (or matters) to use eq/neq or use ==/!= ?
Also, is there a difference between using empty($wpcf-field-name) or using $wpcf-field-name eq "" ?

Thanks!
Jeff

#1160483

Dear Jeff,

I assume we are talking about [wpv-conditional] shortcode, see our document:
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-conditional

= or eq ... != or ne

So I suggest you use eq/ne in your [wpv-conditional] shortcodes

Q2) is there a difference between using empty($wpcf-field-name) or using $wpcf-field-name eq "",
They are same result, you can use one of them, see our document:
https://toolset.com/documentation/user-guides/conditional-html-output-in-views/checking-fields-and-other-elements-for-emptynon-empty-values/
There are several ways of testing a field (or a shortcode) for empty/non-empty value:

#1160524

My issue is resolved now. Thank you!

#1160955

You are welcome.