-
Notifications
You must be signed in to change notification settings - Fork 573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: A page on what the client caches. #863
Comments
This issue has been Linked to https://github.com/Drassil/git-wiki-theme/issues |
I think this might be related to the AC wiki more than the git-wiki itself I'm going to check cloudflare as soon as I have time |
There was a 4 hour cache on Cloudflare. I have disabled it, so we should only rely on the GitHub cache. How long did the cache last after you updated a page? |
For the record, this issue requests information on what the World of Warcraft game client caches, not anything related specifically to the wiki platform/software itself. |
oh wow, I completely misinterpreted it then. Since this has been linked to the main git-wiki repo I thought there was a caching problem with the wiki itself |
I thought all this time you meant client as the user in the website not about the wow client, i'm sorry about the missunderstanding from my part of this @Yehonal |
No worries! By the way, you can increase the cache version in the worldsever.conf to cleanup the client cache automatically to everybody. People should do that on every server update more or less. Or am I not on the right track? cc @Nyeriah |
Is your feature request related to a problem? Please describe.
There have been quite a few times where users and contributors have made changes that require the client cache to be cleared. Sometimes the client caches things that users might not expect, and thus don't clear the cache until they come to the Discord asking for support.
Describe the solution you'd like
Having a page describing what fields/tables end up in the client's cache would be quite useful.
The text was updated successfully, but these errors were encountered: