Replies in GetSatisfaction helpcenter are not showing up
After a reply in the GetSatisfaction helpcenter, the reply shows up after several minutes. Is this a feature to release the load, or is this a bug?
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?This is probably a bug... I thought we were bypassing the cache on topic pages in Helpcenter.
I'll let the guy we have helping with helpcenter, Ezra, comment on a fix. Unfortunately I've got waaaay too many other dev tasks to help out on this one. I'll forward this onto him. -
FYI... Ezra is in a different time zone so it may be a bit before he comes online. :) -
Inappropriate?We don't bypass the cache for topics. Scott, does the timestamp on the topic change when a reply is posted? I seem to remember that it doesn't. In which case, Help Center should invalidate the topic's cache, upon posting a reply.
It should be a small change, adding invalidate_http_cache($url), for the appropriate $url. Unfortunately, I'll be offline from this evening through Tuesday, so I can't make this change right away. -
Inappropriate?What is the status on this problem? I must admit I've been using GSFN instead of help-center, and it have worked out fine for me, but I'm curious wether this is fixed or not...
-
Good question. Let me track down that answer. -
I've poked a bit into the source, and it seems like it's fixed, but I'm not 100% sure -
Inappropriate?doesn't appear to be fixed - i am seeing this now
just setup helpcenter and got everything working up until trying to reply - same problem as the original post. if i manually remove the row from the http_cache table then all is good. so looks like the cache is not invalidating. -
just add:
mysql_query('delete from http_cache where url = \'' . $topic_id . '\'');
before:
redirect('topic.php?id=' . urlencode($topic_id));
in handle-reply.php and it'll work -
In the development tip we use:
$topic_url = $topic_id;
invalidate_http_cache($topic_url);
Looks like the fix may not have been released yet, I'll look into that.
Loading Profile...



EMPLOYEE


