I'm trying to insert a Beaver Builder posts module at the bottom of a single CPT content template to create a so called "related posts" box. The problem is, when I do it, the content template breaks and the template loses all it's field connections and you can't preview the different posts when inside the builder. When you save, it saves the template name instead of the post title and all dynamic fields are left empty. (hidden link)
Though, when trying the same thing on an older installation of the site it works fine. (Toolset Types 2.2.16, Toolset Views 2.4.1, Toolset CRED 1.9.2). Is there a bug in the updates or is this "nested loop" thing not allowed anymore? (hidden link)
Since this kind of module won't give me exactly what I want. It will not show me related posts, only all the posts sorted in different ways, is there a way to do it conditionally by the posts current (custom) taxonomy terms? By conditional shortcodes "around the module"? Or by making a view to insert in some way? What do you recommend? Can you please help me in the best direction?
I know my questions should be sent in a separate forum message, but they depend somewhat to the eventual solution of my problem report, but if you want me to, just tell me.
Hi can you try the following troubleshooting steps first?
- Temporarily deactivate all plugins except Types, Views, BB and Ultimate Addons for BB, then activate a default theme like Twenty Seventeen. Test again.
- If the problem was resolved, reactivate your theme, then plugins one by one until the conflict is revealed
- If the problem was not resolved, I will make a clone of your site and take a closer look.
Let me know what you find.
No, still the same problem after trying your suggestions.
Concerning a "real" related posts box it seems like it will work with a view. Been away from Toolset for a while. Had forgotten things, but will replace the posts module with a view. So I think I don't need an explanation of that.
But it's ok if you clone the site and try to fix the original problem.
Okay I was able to replicate this problem on my own local environment with the Ultimate Addons for BB plugin. It seems to be a conflict with the Views plugin, so I have escalated this to my 2nd tier support for further investigation. In the meantime, if you need assistance building a list like this in Views let me know.
I'm doing some ticket cleanup here in the forums and wanted to note that our Compatibility team is now waiting for feedback from the Ultimate Addon plugin authors to resolve this issue.
Hello, I've been informed the permanent solution for this problem will be included in the next release of UABB. I don't have a timeline for that release, but you may be able to find more information on the UABB site https://www.ultimatebeaver.com
Hi, can you confirm the problem is solved in the latest UABB release?
Hi Christian,
as I wrote in the thread I solved this with a view instead of a posts module but I just checked again on another dev site after upgrading and deactivating other plugins and switching to Twenty Sixteen. When I put a posts module in a content template for a single post built with BB the problem is still there. I'm not sure why you think the UABB plugin has anything to do with the problem, BB has it's own posts module, so you can build the template without UABB. I deactivated that one as well. Same result.
Okay sorry for the misunderstanding, I have corrected the ticket internally and we will continue to investigate the issue with the BB Posts module in a Content Template.
A note from my 2nd tier team:
To fix this, BB needs to apply the same fix as was applied here for UABB.
In /bb-plugin/modules/post-grid/includes/frontend.php, begin of file and end of file:
// Save the current post, so that it can be restored later (see the end of this file).
global $post;
$initial_current_post = $post;
wp_reset_postdata();
// Restore the original current post.
//
// Note that wp_reset_postdata() isn't enough because it resets the current post by using the main
// query, but it doesn't take into account the possibility that it might have been overridden by a
// third-party plugin in the meantime.
//
// Specifically, this used to cause problems with Toolset Views, when its Content Templates were used.
$post = $initial_current_post;
setup_postdata( $initial_current_post );
We've written an email to the Beaver Builder plugin developers about this, and suggest you raise the concern with their support team as well. This will help get the solution implemented. From our end, there's not much we can do other than suggest a change in their software.
We have received word from BB that this issue will be resolved in their next release. Thanks for your patience and persistence!
This should have been resolved by now. Please check with the latest version of Beaver Builder.
No, sorry. Tried both BB and UABB posts modules. Still no solution to the problem.
Then we were given incorrect information, or there was a miscommunication among my team. I'll try to find out.
Our records indicate this issue should have been resolved by Beaver Builder by now. Please let me know if that is not the case.
