m (trick) |
No edit summary |
||
| Line 5: | Line 5: | ||
Also, there's a trick to see the current image that is supposed to be in cache but not. View the actual file in your browser... and add "?1" without quotes to the end of it - that will show you the image that should be in cache but isn't. — [[User:Morder|Morder]] 15:35, 18 May 2009 (UTC) |
Also, there's a trick to see the current image that is supposed to be in cache but not. View the actual file in your browser... and add "?1" without quotes to the end of it - that will show you the image that should be in cache but isn't. — [[User:Morder|Morder]] 15:35, 18 May 2009 (UTC) |
||
| + | :might be fixed now! if you see an image thats supposed to be different, add <code>?action=purge</code> (or <code>&action=purge</code> if theres already a ? in the url) from the File: page, that should correctly tell the backend stuff to fix its self. everytime this happens, we get closer and closer to making it never happen again :) --[[User:Uberfuzzy|Uberfuzzy]]<staff /> 15:57, 18 May 2009 (UTC) |
||
Revision as of 15:57, 18 May 2009
Just so everyone knows cache servers are having issues with updates. It's a known problem and a solution is in the works. — Morder 02:49, 18 May 2009 (UTC)
Also, there's a trick to see the current image that is supposed to be in cache but not. View the actual file in your browser... and add "?1" without quotes to the end of it - that will show you the image that should be in cache but isn't. — Morder 15:35, 18 May 2009 (UTC)
- might be fixed now! if you see an image thats supposed to be different, add
?action=purge(or&action=purgeif theres already a ? in the url) from the File: page, that should correctly tell the backend stuff to fix its self. everytime this happens, we get closer and closer to making it never happen again :) --Uberfuzzy 15:57, 18 May 2009 (UTC)