On lien caché, we upgraded from Toolset Views v3.2.2.1 to the latest 3.3.5 version, and the Testimonails page (lien caché) began responding with a HTTP 502 Gateway Timeout error.
Link to a page where the issue can be seen:
lien caché
All pages on the site are also now very slow.
I expected to see:
When loading the home page with Views v3.2.2.1, the Query Monitor Plugin shows:
0.92s load time
42,306kb peak memory usage
24 database queries
Instead, I got:
But after upgrading to version 3.3.5, the Query Monitor plugin shows this when loading the home page:
28.65s load time
191.992kb peak memory usage
571 database queries
ie a 28 second load time occurs after upgrading, and there are almost 24 times the number of database queries.
You can replicate this by logging into the site, and going to lien caché and installing your views v3.5.5 zip file. For now, the site has been rolled back to views v3.2.2.1 so that you can upgrade it and see the timeout issue start for yourself.
Hello. Thank you for contacting the Toolset support.
Thank you for sharing all those details.
Based on debug information you shared, I see you are using outdated WordPress version. We always recommend running your site with the latest stable release plugin version. Can you please update WordPress to latest official released version: 5.6
=> https://wordpress.org/download/
After updating WordPress to latest version, Do you see any difference? If no:
- Can you please send me admin access details and I would be happy to review whats going wrong with your setup.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
I just added and activated the Toolset Views version 3.3.5 and when I visit the "testimonials" page:
=> lien caché
I see HTTP ERROR 500. Can you please check the server logs and share with me.
Also, can you please try to host the test site on another server (non-wpEngine) and see if you see the same things happening. I wonder why its not working, something must be blocked from server as the Toolset Views version 3.3.5 is the current version and if its not working then our forum will be full of tickets and that is not the case and Toolset Views version 3.3.5 is the stable version with not many bugs reported especially 500 HTTP error.
[Mon Jan 18 13:29:26.620544 2021] [php7:error] [pid 3993] [client 103.156.207.32:24824] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 32768 bytes) in Unknown on line 0, referer: https://toolset.com/
[Mon Jan 18 13:29:49.929151 2021] [php7:error] [pid 3993] [client 103.156.207.32:24988] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /nas/content/live/pumpengstage/wp-includes/functions.php on line 6455, referer: https://toolset.com/
[Mon Jan 18 13:29:49.931113 2021] [php7:error] [pid 3993] [client 103.156.207.32:24988] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 49152 bytes) in /nas/content/live/pumpengstage/wp-includes/functions.php on line 4755, referer: https://toolset.com/
So the error you're seeing is a memory exhausted error, which causes a HTTP 500 error.
It's a symptom of some kind of performance issue and/or infinite loop.
Unfortunately, your suggestion to try another web host doesn't seem like a response that shows you've look at this in any great detail. It seems like a simple/quick way to "pass" the responsibility back to us to investigate.
Having said that, I have followed your suggestion and downloaded the site to another hosting environment. I'm now hosting a copy of the site locally on my own PHP 7.4 environment and the performance problem exists.
You can download the site here too if it helps: lien caché
It's easy to replicate by upgrading views to the latest version.
here's a stack trace I got from my local environment in case it helps:
Thank you for sharing your site copy. I've installed and configured your site on my local server and yes, I can confirm that the "testimonial" page works as expected with views version 3.2.2.1 but as soon as I update the views to latest version 3.3.5, I can see "testimonial" page is not working and see the memory error.
Please allow me to escalate this issue to our next level support and I will get in touch with you as soon as I have any news or findings.
However - I see you added the view using view's shortcode to "Text" module of beaver builder and there is nothing fancy you added using BeaverBuilder to the "testimonial" page, if you want, the workaround is to use the Blocks instead of BeaverBuilder and I can see with Blocks the testimonial page works even with views version 3.3.5.
I got the news from our next level support that - the problem happens because the output of the View uses a content template which is designed using BeaverBuilder and that template includes the post body shortcode:
This is the view that uses the content template for view's loop that is desiged using BeaverBuidler:
=> lien caché
And if you edit the loop item content template, you will notice that you have added the following shortcode to display the post content:
[wpv-post-body view_template="None"]
If you remove the above shortcode from the loop item content template you desired using BB, the page loads fine as expected.
As a temporary solution, we do not suggest you to use post body shortcode within view's loop content template or discard use of BB with loop item content template.
However, we will escalate the issue to our devs to know why its working with Views v3.2.2.1 and not with Views v3.3.5.
That shortcode has worked fine for years, and now it’s a problem in the latest views version so I’d really like to find out if this can be solved in a new views release.
In the meantime, is there a recommended way to output the post body/content when using a beaver builder based content template in a view?
Could we please know when this fix will be added to a public release? also is this hotfix only for views version 3.3.5 or can we apply it to views version 3.4.2
At the moment we have 41 sites that are running toolset views which we can't update automatically.
