This support ticket is created vor 7 Jahre, 2 Monate. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
Oh dear. Thanks for trying. Can you confirm that on the home page you had a large slider at the top and "featured properties" automatically scrolling at the bottom, both using ajax? Did the site overall seem to use an acceptable level of memory?
Ok thanks I have created a package, but it's 1.4GB, and will take me about an hour to download to my desktop and then probably much longer to upload to Dropbox. Can I give you WordPress admin login so that you can download it directly from there? Thanks.
Sorry Shane I forgot to add that the other reason I previously sent you a backup from a couple of weeks ago is that I took out the second Ajax view from the live site because of the errors. This package was taken from the live site so you would need to add a short code for the featured properties view to either the home page or prestige page ( both of which have sliders) in order to see the problem, if indeed it exists on your server, which I doubt or you should have already seen it with the original backup.
Ok following your instructions it seems that the Featured Properties view was already there. See Screenshot
However there were still no errors on the page. I assure that what you are seeing should not affect your sites performance and could be due to a varying amount of other things such as server configurations, php versions, folder permissions etc.
I have re-enabled the second Ajax view on the homepage and immediately I see the return of the 500 errors accompanied by huge spikes in virtual memory on the server. BUT – a lightbulb moment – if I disable "preload next and previous pages" for the view, it appears that the problem goes away. I don't know if this sheds any light on the issue or not, but it may be able to help somebody else in the future.
