Guest Posted December 19, 2005 Posted December 19, 2005 Greetings all. Happy holidays. I'm new to OSCommerce and think its a great product with an even greater support team. Q1 I have been trying to get my store running properly for about 3 weeks now. I'm not a coder, I'm a designer. So I really just wanted to get through the setup and installation and get straight to designing. When I go to my admin/index.php page and click on a link...like Configuration, I get a 404 Error & the following link - mydomain.com/admin/FILENAME_CONFIGURATION?selected_box=configuration&gID=1 It looks as though something is not pointing in the right direction. The only thing I did that did not follow the PDF installation guide is alter the installation path. I excluded the /catalog/ folder and installed directly in the root of my web server. I am hoping this did not throw anything off, although I assume the paths were set when I ran the install.php file and set the whole thing up. I had my host verify the permissions on all the files which required permission changes. Everything checked out. Q2 When I set my SSL up during the setup of the site I specified a path with /inflite/ at the end indicating my folder on the secured server. When I log into my site from the index page with an existing user name it 404 errors on me with the secured SSL path in the address bar, minus the /inflite/. It's like the handoff from one page to the next did not carry the /inflite/ over. Where would I look to correct this problem? Thanks. Jaysun
Guest Posted December 19, 2005 Posted December 19, 2005 no one has any experience with this problem or a possible solution?
G & T Posted January 17, 2006 Posted January 17, 2006 Hi Jaysun - did you get anywhere with your Q1 problem -I have something similar, althought the path shown varies slightly : http://localhost/admin/configuration.php?s...1782fc53dd88575 If you have cracked it, info on how you did it would be gratefully received!
G & T Posted January 17, 2006 Posted January 17, 2006 Have now cracked it myself ( yippee!) was a path problem in the admin/includes/configure.php file.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.