Same here, though I did not think to try removing the “if” logic.
Rolling back definitely fixes the issue. Other Pods that don’t disappear are either a) using “wpbb post:pods_display” etc code (without the if) or b) using Pods templates to display.
Thanks for the report, looking into this to see what might have caused this issue.
Finally tracked down a way to reproduce this. Will get to work on a solution tomorrow.
Just lost half day debugging to understand what was breaking my website
Lucky I found it on staging
Reverse to 133 fixed the pb
Similar experience on relational data. I have a customer working on a site with several CPTs with quite a few fields in each CPT. He reported that fields were missing here and there in the frontend. This has happend within the last few weeks without any of us having edited the pages. So I suspect some update in December has changed something fundamental.
I’m using BB Pro + BB Theme + Themer + Pods Beaver Themer Add on.
I haven’t dug into all of the cases, but let me focus on one that is different from the above, since it is involving fields from a relationship CPT:
On one CPT “Regent” I have a Pods relationship to “Books”.
I’m presenting a list of related books on the single record of a particular Egyptian king/regent.
<div class="uabb-blog-post-section">
[wpbb post:pods_display field='ophav']
([wpbb post:custom_field key='aarstal'])
[wpbb post:custom_field key='titel_kilde']
[wpbb post:custom_field key='udgiver']</div>
The shortcode [wpbb post:pods_display field=’ophav’] fails to show up.
If I change it to [wpbb post:custom_field key=’ophav’] it works fine.
I’m using UUABs Advanced Posts module presenting the related records with “Grid”, but I have just reproduced the issue with BBs own posts module. Same situation.
-
This reply was modified 5 months, 1 week ago by
biberkopf.
-
This reply was modified 5 months, 1 week ago by biberkopf.
-
This reply was modified 5 months, 1 week ago by biberkopf.
I’m having the same problem with these fields not showing up since updating to 1.3.4. I just went back to the previous version and all is displaying correctly again.
I wanted to reach out and confirm we do have a fix for this but it’s going through some extra testing to be sure it’s not causing another breakage. Thanks for your
Pods Beaver Themer Add-On fix: https://github.com/pods-framework/pods-beaver-builder-themer-add-on/pull/112 (ZIP: https://github.com/pods-framework/pods-beaver-builder-themer-add-on/archive/release/1.3.5.zip)
Pods fix: https://github.com/pods-framework/pods/pull/5912 (ZIP: https://github.com/pods-framework/pods/archive/release/2.7.26.zip)
You will need both updates to get around this. The releases should both go out tomorrow.
Sounds good. Thanks for the fixes. I’ll report back shortly after the release.
Hi,
I’m sorry that happened to begin with :/ that’s on me! Sadly it took longer than I thought for a proper solution as we encounterd some edge cases on the way!
We did test it and it should be released soon – thanks for your support and understanding!
Happy New Year
Bernhard
Hi Scott and Bernard:
I feel very confident with you on the case.
Thanx for your thoroughness and dedication!
And a happy new year to you.
🙂
/j
Quick update – short delay – waiting on a fix for an unrelated issue in Pods so that both releases go out as Pods Beaver Themer depends on Pods 2.7.26 for one part of the fix.
Thanks for your patience!
The update seems to have solved my problem. Thanx a lot. 🙂
-
This reply was modified 5 months ago by biberkopf.
