+- Form Tools (https://forums.formtools.org)
+-- Forum: Form Tools (https://forums.formtools.org/forumdisplay.php?fid=1)
+--- Forum: Installation (https://forums.formtools.org/forumdisplay.php?fid=4)
+--- Thread: Error logging into Admin Panel after successful installation Step 6 (/showthread.php?tid=729)
Error logging into Admin Panel after successful installation Step 6 - jwalter - Jun 1st, 2010
I just went through a successful installation of formtools 2. The only change I made was to the prefix for the tables, instead of ft_ I made it ft2_. (I received an error on this step telling me that a table ft_... already existed, this would be correct since we have been using earlier versions of FT for several years.)
After completing step 5, it said the installation was successful and to delete the installation folder, then log in to the admin panel.
The admin panel does come up "with errors", there is no "design" to the page. I attempt to log in to the admin panel then get "this page cannot be found" error.
I kept the default name of the directory formtools instead of (ver. 1.5 - form_tools). Does the directory name need to be form_tools?
Also, I thought the data from the earlier version wouldn't be lost, when I log into the earlier version, all the forms are now gone.
Thank you for any help you can provide.
RE: Error logging into Admin Panel after successful installation Step 6 - Ben - Jun 1st, 2010
Hi jwalter,
Hmm...! No, the folder can be called whatever you want - so that's not it.
When you say that the admin panel shows up with errors, what kind of errors do you see?
Off the top of my head, it sounds like one of the following is the culprit:
1. All the files weren't uploaded via FTP. Connections can occasionally break. I'd try re-uploading the entire contents of the downloadable zipfile, with the exception of the /install folder. It'll overwrite everything and ensure that all the files are on your server. The only custom file is the config.php file and that won't be touched (since it's not in the zipfile).
2. the URLs / paths in the generated config.php file aren't correct. But if it was created by the install procedure, it should be fine...
Other than that... not sure! It's possible that sessions aren't working on your server perhaps...
Try #1 above and see how it goes.
Good luck!
- Ben
RE: Error logging into Admin Panel after successful installation Step 6 - jwalter - Jun 2nd, 2010
Hi Ben,
I tried step 1, still got the same results.
I check with our hosting site to verify the url path and that is correct.
I check with our hosting site and Yes sessions are turned on.
I have included a print screen of what the administration panel looks like when I log into it.
When I type in the username and password, I was get a 404 error, then I clicked forgot password and then got messages that the password doesn't match.
**I FIXED this one - I read in a different post that the passwords are encrypted in the accounts table. When I clicked on forgot password, it changed my password but did not mail it to me. So I went to this site and enter a password to get the encrypted version and put that into the db. ** Now I'm back to the 404 error.
I do like how formtools worked, but we need to move to 2.0 for smtp mail feature. I hope we can figure this out.
Thanks for your help.
RE: Error logging into Admin Panel after successful installation Step 6 - Ben - Jun 2nd, 2010
Hi jwalter,
Hmm... well, for starters, it's not even managing to load the stylesheets properly. So that means that (a) the paths to the CSS files are incorrect - which means the $g_root_url value in your /global/config.php file is incorrect, or (b) the CSS files don't exist.
Since you're sure you uploaded everything I guess it must be 1.
Take a look at that file. It should have a variable like this:
PHP Code:
$g_root_url = "http://www.yoursite.com/formtools";
Check that the URL in that field is the same as the login page (minus the /index.php part).
- Ben
RE: Error logging into Admin Panel after successful installation Step 6 - jwalter - Jun 3rd, 2010
Thanks Ben,
/formtools was missing from the url, it now works.