[Solved] mark_all_read

[kelso]

No matter which computer im using, every time I visit the site and I goto mark all read, its the "mark_all_read" button that does nothing. Upon force-refreshing, I get the proper button with the dropdown and all is well... Except the next time I visit the site, its back to the old behavior. This happens on my macbook using chrome, as well as my desktop using chrome as well. Anyone else experience this?

[Sp4rkR4t]

You have to clear your browser cache.

[kelso]

Doesnt a force reload (control-f5/cmd-r) essentially do that for the page you're viewing?

[kelso]

apparently not

[luke]

On a related note, I think NodeBB should have a timeout on resources such as whatever's causing that mark_all_read bug. @julian @psychobunny

[julian]

Client-side templates should use cache buster · Issue #1392 · NodeBB/NodeBB

Client-side assets and stylesheets are invalidated properly, though the template can still get cached by the browser, and can interfere.

GitHub (github.com)