user side check status button not working right

durangod

hi on the user side, there are two buttons, open new ticket and check status buttons, the open new ticket button shows open.php when you run your mouse over it and it works fine..

but.....

the check status button shows tickets.php when you run your mouse over it and it gives me a page not found until i hit refresh then it comes up fine, when i use the check status link above it works fine..

any idea why one button would work fine and the other one on the same page gives me a page not found until i hit refresh, and both the form action commands are the same, one says action="open.php" and the other says action="tickets.php" but it cant find the tickets php on first click, its takes a refresh to find it..

any ideas??

Kelli

That's very strange.... what's the URL? I'd like to see this in action, not that I doubt you or anything. I'd just like to take a look at it happening and see if I can figure out why. You can PM me if you don't want to post it publically.

durangod

i sent you a pm thanks

hi i sent you a pm thanks for taking a look

Kelli

Are you using a Windows host, by chance? (it doesn't look like you are... but now I'm wondering if your apache version may be contributing to the problem)

Try commenting out line 65 of login.php

durangod

no im not on windows server

ok ill try that, but no im not on windows server at all.. it on linux and apache with lp

durangod

by the way before i do this which line is it just so im sure.. i have customized my version and just want to be sure. thanks

Kelli

@[deleted]('Location: tickets.php');

durangod

commented that line and it did not help, im really scratchen my brain on this one...

just fyi i did have the same issue on a dif software (noah classified) on the same server and i removed the login captcha and it fixed the problem but not sure what association that would have with this software other than maybe a server setting somehow...

Kelli

Ah, that's really confusing then... :/ without taking a look at the modified code, I have no idea. The commenting out the redirect was kind of a long-shot, anyway... but I'd seen similar problems in the SCP on a few Windows installations, so figured it was worth a shot.