When we upgraded from views 2.0 to 2.1, infinite scrolling broke on our production site in that it no longer interprets the shortcodes in our Loop Output section. I've rolled back to 2.0 on our production site, but you can see the problem on our sandbox where we have 2.1 installed.
Compare the infinite scrolling on these two pages:
hidden link hidden link
The attached screenshot shows you how we invoke our view directly via PHP using the render_view() code, as well as how we've setup the view itself.
# Duplicator instruction
+ From WordPress plugin page, look for "Duplicator" and install it
+ Once installed, you get a new main menu "Duplicator"
+ Chose "Packages"
+ Click on the first button you find in the toolbar on the right ("Create Package")
+ Give it a name or leave it as is
+ Click on "Create Package Set"
+ Wait until the package is ready
+ Click on "Installer", then on "Package": the first one is just a php script, the second one is a zip file containing everything you need
+ Send me both files (you probably want to use DropBox, Google Drive, or similar services, as the snapshot file will be quite big)
+ Send me wp-admin access-details
I have set the next reply to private which means only you and I have access to it.
Hello, is there any news on this issue? We're not super comfortable having downgraded from 2.1 to 2.0. I'm worried that such a major downgrade could cause problems with our existing views. We'd like to get back to using 2.1 as soon as there's a solution for this problem.
This issue is being handled directly by one of our developers and one of our compatibility team.
The current situation:
- Our development team put their hands on the issue and they found that:
- This is a compatibility issue between the Toolset plugin and the Divi page builder
- There is some work we need to do from our side and other work from the Divi team side
- In the meaning time, we are going to contact the DIVI team to handle the issue together
This is a part of the development team response:
"The Page builder should provide either frontend AJAX support or a way for us to whitelist our frontend AJAX calls for some formatting shortcodes to get registered. Otherwise, we can do nothing since we do follow good practices for AJAX."
Please wait and I will get back once I get any updates.
Has the development team addressed whether or not it's possible just to roll back the specific change that was made between 2.0 and 2.1 that would fix this problem for the time being?
These Divi shortcodes were working great in 2.0. Is it not possible to revert the part of the code that led to the conflict?
Thanks for the additional information. I'm nervous about having our production website locked into 2.0 until a *collaborative* fix can be accomplished between Elegant Themes (Divi) and Toolset. I'm guessing that could take quite a while, if ever.