This thread is resolved. Here is a description of the problem and solution.
Problem: I have a View included in an Ubermenu menu. When I apply random sort order, some of the page content disappears. Then if I refresh the page, the page content reappears. I am using Litespeed server, and this problem never happened on my previous nginx server.
Solution: I'm unable to replicate the problem locally on my own PHP environment, so it would seem that the issue is related to the Litespeed environment. Disabling random order is probably the best solution for now.
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.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 15 replies, has 2 voices.
Last updated by 6 years, 6 months ago.
Assisted by: Christian Cox.
Unfortunately I'm not able to replicate the issue on a local clone of the site, so I'm not able to pin down whether the issue is random sorting per se, or one or more posts in the result set that may be causing the problem. On the development environment, you could add a post ID filter and pass in the IDs of 4 posts that are known to appear as expected when order is not random...that would eliminate the possibility of a random problematic post breaking everything else. If the problem persists at that point, then it becomes obvious that the random order itself is the main problem.
You could also try adding the cached="off" parameter to the View shortcode:
[wpv-view name="widget-generic-article-by-placement-tag" wpvpagearticleplacementtag="things-to-do-more-information" limit="4" cached="off"]
This could help eliminate the possibility of Views caching contributing to the problem, but I'm not sure if this will help or hurt the situation.
