Homepage not updating (Cloud, Users are logged in)

[Markus Jung]

At the top of my homepage/forumhome I have a block with new forum entries.

If I (or other users) come back after some time, it still shows the old list. Only if we hit F5 it will update. 

It happens on mobile and Desktop, browser is chrome.

You can find screenshots/examples here:

https://www.fernstudium-infos.de/topic/20001-startseite-aktualisiert-sich-nicht-mehr/page/3/

 

 

[opentype]

From what I read in that topic, it sound more like browser behaviour than server behaviour. Like those users have the old page still open in their mobile browser in the background and it is not actually reloaded but just put into focus again. Or something like that. 

But either way, I would reconsider the entire setup. Blocks aren’t meant to be used by active members to see new content. That’s what the /discover/ page is for. I would always put the latter in the main menu to get my active users to open that page as the default entry point. 

[Jim M]

I had to read a Google translated version so may not have gotten the full picture due to that, but I would tend to agree with @opentype. Mobile browsers, if they have a tab open or just simply minify and go back will not refresh the page (even though it may look like it does). To get the latest from the server, you would need to force a refresh or go to a new page and back (as one of your users mentioned).

[Markus Jung]

Thank you for your responses.

I do have links to new (/discover/) and unread content in my main navigation and at the top of my home page.

Still, many user (and also myself) are used to going to a news site or blog and seeing, at first glance, what's new.

1 hour ago, Jim M said:

Mobile browsers

It also happens to me, on my desktop computer with Wi-Fi connection and no data saving options activated.

Shouldn't the system trigger the browser to load a new version of the page if there are any updates?

I don't have this issues on other news sites or blogs I visit regularly. 

It sometimes even happens if I start on the homepage, then go to another page of my site and then turn back to the homepage. Only if I then click F5, I get a refreshed version of the homepage.

[Jim M]

7 minutes ago, Markus Jung said:

Shouldn't the system trigger the browser to load a new version of the page if there are any updates?

No, this is not how things operate, I'm afraid.

7 minutes ago, Markus Jung said:

It sometimes even happens if I start on the homepage, then go to another page of my site and then turn back to the homepage. Only if I then click F5, I get a refreshed version of the homepage.

This would be correct operation. Your browser often would cache pages when using the back button. You would need to go to the link a new using the breadcrumb or other navigation to trigger a refreshed view in your browser.

[Markus Jung]

I don't have this behavior on any other website.

Today I visited my community first time after the night (computer booted and new browser session), typing in the URL (autocomplete) – and got a version of the page that shows me, that the last entry was 14 hours ago. If I were an average user, I would think “okay, nothing new” and go away. 

Aren't cache headers (https://www.keycdn.com/blog/http-cache-headers) used to prevent this? At least for logged-in users? 

If I go to, e.g., LinkedIn, I always get an updated view. Also on news sites, even if I am not logged in.

[Jim M]

3 hours ago, Markus Jung said:

I don't have this behavior on any other website.

Today I visited my community first time after the night (computer booted and new browser session), typing in the URL (autocomplete) – and got a version of the page that shows me, that the last entry was 14 hours ago. If I were an average user, I would think “okay, nothing new” and go away. 

Aren't cache headers (https://www.keycdn.com/blog/http-cache-headers) used to prevent this? At least for logged-in users? 

If I go to, e.g., LinkedIn, I always get an updated view. Also on news sites, even if I am not logged in.

There would be no cache for logged in users. We actually tell the browser this (no-cache, no-store, must-revalidate, max-age=0, s-maxage=0). What you are stating about using the back button is different than loading a completely new browser session and the browser does not open a previous session. 

Keep in mind that if you're using a block to display new topics, they have their own internal cache and would not update frequently. As opentype mentioned.