Random view stopped randomizing

This support ticket is created 2 years, 1 month ago. 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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: Toolset Blocks, Views, Views plugin

This topic contains 2 replies, has 2 voices.

Last updated by matthewC-9 2 years, 1 month ago.

Assisted by: Waqar.

Author

Posts

October 19, 2022 at 7:14 pm #2479509

matthewC-9

Hi! I have a view that has ordering set to random order. In the past, this has worked fine, and I don't think I've changed anything about the view. However, now it's always showing the same post instead of randomizing. Some examples are the "Meet the..." sections on hidden link, hidden link, and hidden link. Can you help get this working again?

thanks!
Sarah

October 20, 2022 at 6:08 am #2479769

Waqar

Hi Sarah,

Thank you for contacting us and I'd be happy to assist.

From the page's source code, I noticed that the "WP-Super-Cache" plugin is active on the website. Cache plugins generate the copy of the page once and keep using that copy for subsequent visits or reloads. This would explain, why the views are showing the same results over and over again.

Can you test this with the cache plugin disabled? Once confirmed, you can consult the "WP-Super-Cache" plugin's documentation or support team to learn how to exclude specific pages from being cached.

regards,
Waqar

October 21, 2022 at 7:50 pm #2480911

matthewC-9

OK, thank you! It does seem that it's a caching issue - weirdly, it doesn't get cached in all browsers. Now that I know it's updating on our cache expiry schedule, that's good enough.