Mephisto

What other people had to say

1. Tanc 11 23 2006 05:33 PM
   Can I ask whether you will fix the comments bug? The google group thread seems to have died with no solution and I still can't post more than one or two comments. This is on latest trunk, on Dreamhost with MySQL, Apache, FCGI etc. Comments used to work in older 0.6.x revisions I believe.
2. rick 11 23 2006 10:21 PM
   This is comment #2, meaning mephisto is working properly. I still haven't seen a failing test case showing what the bug is.
3. Andrew Montgomery 11 27 2006 05:49 AM
   I came across this bug. I 'fixed' it by putting @skip_caching = true at the beginning of dispatch_comments and dispatch_comment methods in the MephistoController class. Evidently, this issue has something to do with caching. Before my hack, I found that the caching mechanism was creating an empty comments folder in each of my articles when the first comment was made, and this stopped any requests from reaching mephisto (ie, no requests were in the production.log). I'm guessing the url handling of different servers is mistakenly sending the requests directly to this empty directory url instead of getting mephisto the handle the requests. Does anything even get stored in the comments folder that gets created by the caching mechanism? I didn't see any evidence that anything was actually cached in there, so a solution might be to stop said folder from being created in the first place since it serves no real purpose (my @skip_caching hack does this, albeit in a way that isn't neccessarily the best).
4. rick 11 27 2006 09:19 AM
   It's an "apache config":http://mephisto.stikipad.com/help/show/Developer+Tips issue.
5. Andrew Montgomery 12 01 2006 03:49 AM
   I'm aware this is an issue with apache, but changing the config for me didn't seem to fix this and on one server I tried the DirectorySlash directive wasn't even supported. On the other hand, the empty comments folder that gets created triggers the bug in the first place needlessly. Since the folder doesn't do anything cacheing-wise, considering its empty, there is no point in having it around - especially since it triggers this bug which can't be worked around by people who don't have access to their apache configs and can only alter their configs for their proxied servers like lighttpd/etc. Unless there is actually going to be something cached in the comments directory that gets created, I don't see the problem with making a change to make sure this unused directory doesn't get created since it is needlessly breaking peoples commenting systems.
6. rick 12 03 2006 06:08 PM
   Sounds good to me, anyone have a tested patch for that?
7. Duncan Ponting 12 20 2006 05:02 AM
   linked_tag_list does not appear to be in the 0.7.3 release ? Should it be there? It is in trunk but according to teh change log should in 0.7.3. Thanks, Dunc
8. Duncan Ponting 12 20 2006 05:04 AM
   Sorry for the incorrectly nested strong tag in my comment.