I had a problem that was in the URL. The email sent a message containing the url ~~/user/my_account.php. I found the typo(?) in a couple of the files, and changed it to ~~/user_interface/my_account.php and everything worked great.
-----Original Message----- From: Leif Madsen [mailto:leif@hacklocalhost.com] Sent: Tuesday, October 21, 2003 5:50 PM To: serusers@lists.iptel.org Subject: [Serusers] A couple of initial problems with SER
Good day all,
I have attempted to search through the archives before posting here, but alas, I have been unable to find the answers. If there are websites or links that would help me with finding the answers to my questions, those would be great as well.
I am mostly having problems related with my_account.php (or at least that is what is being accessed when things fail). I can create a new account, and it emails me the confirmation link fine, but when I go to click on the link, it just hangs in the browser with "Web site found. Waiting for reply..."
It never actually errors out (at least not for the last 5-10 minutes while I've registered and sent this email). The other problem I have is in the admin interface. If I click on "Account" then it ends up doing the same thing. It attempts to connect to the my_account.php script, but just hangs (doesn't even seem to timeout)
If there is somewhere I can check logs and stuff, that would also be great.
Thanks in advance!
Rork, Joseph (J.P.) wrote:
I had a problem that was in the URL. The email sent a message containing the url ~~/user/my_account.php. I found the typo(?) in a couple of the files, and changed it to ~~/user_interface/my_account.php and everything worked great.
I also noticed a couple of the typo's as I was going through the files and corrected them. It does appear to be going to the correct address now.
I checked my error_log and what I was getting was that SerWeb could not find /var/www/html/preload.js for some reason?
I have searched to try to find out what preload.js is... but I seem to be having no luck. I'm not totally sure if this is the problem or not, but it is definately something that is coming up in the error logs...
Unless I've missed some more typo's somewhere else.
Thanks,