View Single Post
Old January 19th, 2005, 04:38 PM   #1 (permalink)
btyner
Registered User
 
Join Date: Dec 2004
Posts: 4
Issue posting comments, not your typical problem

I have 2 Windows 2003 Server environments where photopost is running. Both environments run the same database structure and same photopost code. One is the production environment and the other is my development environment. I am running an upgraded 4.8.6 installation. I upgraded from 4.1 code.

I'll preface this next section with an explanation that when I say "tries to post comments" it means that they either used the quick reply method at the bottom of the showphoto.php page or if they actually click the post reply button and redirect to the comments.php page and then try to post the comment they filled out. The problem I am having is that on the production environment, there are instances where a user tries to post a comment but when the comments.php page is initiated, it just hangs and eventually times out. Now when I try to post comments for that same image on my development box, it works just fine.

So here's the interesting facts behind this: On the production box, there are images that users can post comments to and images that users can't post comments to because the comments page hangs. Most of the time the owner of the images that can't be commented on, experiences this with all their images. These images, most of the time, have a common trait of being in this one category. However, I have found that one user was able to post a comment to an image that I can't. The correlation between the categories may not exist either because I think most of the people actually having issues are posting in the one particular category that has the issues and are not posting in the other categories that seemingly work.

I'm really at a loss as to why this is happening. I tried to look through the comments.php code for an suspicious looking behavior but I'm not a PHP person so the logic behind where everything is coming from isn't too clear to me. I have a feeling it's some strange hardware setting since this behavior is only present on the production box (go figure).

If anyone has any insight at all as to what could even remotely be causing this kind of behavior then please reply to this post. I'm not having much success at figuring this out.

Last edited by btyner; January 19th, 2005 at 04:45 PM.
btyner is offline   Reply With Quote