Conditional logic based on Pods fields seems to have changed

  • For a long time we have been using Beaver Themer + Pods with conditional logic to control the visibility of rows, columns or modules, e.g. “show this row if field X is set” or “show this module if field X is not set”.

    This seems to have stopped working recently.

    Now, we’re having to do workarounds, such as creating a extra checkbox field and using “equals 1” in the conditional logic to control visibility, or “contains https://” for a URL field that should only be displayed if it has a value.

    Not sure if it’s a Pods problem, a Themer problem, or a problem in this plugin. Happy to repost to BB or Pods if its not related to this plugin.

Viewing 6 replies - 1 through 6 (of 6 total)

  • Thanks for posting this. I’ve been meaning to post the same problem because I’m experiencing the same issue. And I’m doing the same workaround that you are ??

    Plugin Contributor Bernhard Gronau

    (@quasel)

    Hi,

    can you test if downgrading pods / bt removes the issue? maybe that’s the quickest way to find the culprit in your cases ??

    I’ll investigate on my end, but most likely it shouldn’t come from pods as that’s a Beaver Themer function that’s just checking custom fields…

    Plugin Contributor Bernhard Gronau

    (@quasel)

    @millionleaves @normsash

    Just did a few quick tests and it worked fine for me.
    Can you provide a bit more context? Like type of field/condition used?

    Did you try to disable everything else?

    @millionleaves @normsash @quasel

    Just wanted to add that I’ve been having this issue too.

    I’m currently working on a site for a client. As an example, for a button module that is connected to a website field, the “is set” part of a rule is not working for the visibility of the button. Using the same field connection and “is set” rule, the visibility of a text module also isn’t working.

    On the other hand, using the “is set” rule for a relationship field is working for visibility in various modules like buttons, headings, and posts.

    I rolled back a couple versions of this plugin and that didn’t solve it. I also de-activated this plugin and bought/activated Page Builder Toolkit from SKC/DEV and it seems to be the same issue.

    I’ve been able to get around the issue by using “contains” in the rule.

    I hope this additional info helps a bit, let me know if I can clarify.

    Maybe it was a change in Pods or Themer that caused this. Did anyone find out more or figure this out?

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    I’ll take a look at this in the coming week, thanks for chiming in with further details. Hopefully I can reproduce the issue but feel free to reach out on our Slack to help me if you’d like.

    Hi guys, has this been resolved? Currently can’t get pods conditional logic to work on a client’s site. Trying to make a module hidden if the a field in the pods “Custom Taxonomy” is empty, but just doesn’t work.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Conditional logic based on Pods fields seems to have changed’ is closed to new replies.