Uh...I'm having some difficulties changing my profile picture. Anyone know what's up?
Quote from: Dr. James Semaj on January 14, 2011, 12:46:02 AM
Uh...I'm having some difficulties changing my profile picture. Anyone know what's up?
Hit refresh.
Quote from: Faust on January 08, 2011, 07:30:49 PM
hit refresh. Everyone who ever has this problem, hit refresh.
Ah, cool. Thanks, Phox.
No problem. SEE!? RELIGIOUSLY READING EVERY NEW POST COMES IN HANDY!
Quote from: Doktor Phox on January 14, 2011, 12:49:54 AM
No problem. SEE!? RELIGIOUSLY READING EVERY NEW POST COMES IN HANDY!
Well, looking in the meta forum where all the other technical stuff is and seeing the avatars thread might save some time before religiously reading every new post.
Ah. Dumbass, thy name is Semaj. Sorry.
Quote from: Faust on January 14, 2011, 12:52:01 AM
Quote from: Doktor Phox on January 14, 2011, 12:49:54 AM
No problem. SEE!? RELIGIOUSLY READING EVERY NEW POST COMES IN HANDY!
Well, looking in the meta forum where all the other technical stuff is and seeing the avatars thread might save some time before religiously reading every new post.
That too. :oops: :argh!:
:lulz:
Quote from: Dr. James Semaj on January 14, 2011, 12:53:44 AM
Ah. Dumbass, thy name is Semaj. Sorry.
Nah its my fault. We changed the way avatars are called in a thread which actually saves us a lot of calls per thread because each avatar isn't checked every time. Unfortunately it doesn't automatically clear the old one from the users cache.
Couldn't the page auto refresh when changed?
Quote from: Able on January 14, 2011, 06:37:41 AM
Couldn't the page auto refresh when changed?
We could I think, if its pretty simple then I'll add it to the update profile source.
I dunno if a <meta> refresh would also refresh the cache, but even if it works, it's the wrong solution.
It needs some kind of .htaccess "Etag" magic, where the browser sends a request with a hash of its cached version (Etag) and the server replies with "Not Modified" it it matches.
Or something.
Quote from: Triple Zero on January 14, 2011, 04:19:56 PM
It needs some kind of .htaccess "Etag" magic, where the browser sends a request with a hash of its cached version (Etag) and the server replies with "Not Modified" it it matches.
Or something.
That would be called pretty often if it checks every user, it also seems excessive like the meta method. I think its easier just to ask people to hit refresh after uploading the image.
Quote from: Triple Zero on January 14, 2011, 04:19:56 PM
I dunno if a <meta> refresh would also refresh the cache, but even if it works, it's the wrong solution.
It needs some kind of .htaccess "Etag" magic, where the browser sends a request with a hash of its cached version (Etag) and the server replies with "Not Modified" it it matches.
Or something.
Don't be fooled pd.com This looks like 000 engaging in harmless l33t speak but it is obviously secret code being sent out. We're all going to get "the visit" soon.
:lol: