This thread is resolved. Here is a description of the problem and solution.
Problem: I have a conditional that is not working as expected on all posts.
Solution: Change the conditional to test for a taxonomy term instead of a custom field in this case.
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 |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 3 replies, has 2 voices.
Last updated by 4 years, 1 month ago.
Assisted by: Christian Cox.
Okay I can see your conditional used the following criteria:
NOT ( empty( '[wpv-post-field name="illustrator" ]') )
This conditional was looking for the contents of a custom field with the slug "illustrator", but I don't see that custom field visible in the post editor. I see a taxonomy called Illustrator, that includes a term indicating the specific Illustrator. Perhaps this worked on some posts because there was previously a custom field used to hold the Illustrator's name? That field could still be in the database, which is why it works for some posts but not others. The conditional logic should be adjusted if you're trying to test whether or not a taxonomy term exists, instead of a custom field value. I've made that adjustment as you can see in the screenshot here, and it seems to be working now on the two posts you shared. Can you do a quick review and see if this is more like you expected?
