Quote by: 1000ideenDid you check if that file /admin/install/install.php is among the extracted ones? Some unzippers may only extract the structure but not the files. If it is there, how did you transfer it all to the webspace?
I suppose it got FTPed to the wrong directory.
I transferred the files to the webspace via FTP. In situations like this one I use a program called FileZilla for FTP.
Within the geeklog-1.4.1 directory on my hard drive, there's an admin/install directory within public_html.
geeklog-1.4.1
|--public_html
....|--admin
..........|--install
...............|--install.php
The directions say that "public_html" is not supposed to be part of the URL when going through the upgrade process. So what I am wondering is this: should I take the contents of the public_html directory (as indicated above) and put them on the webspace within the directory where GeekLog is located? In other words, should I make it like this:
website's public_html
|--shopping cart
|--images
|--other directory A
|--other directory B
(etc.)
|--scsblog
....|--admin
..........|--install
...............|--install.php
Then I should be able to navigate to scs-matters.com/scsblog/admin/install/install.php just like it says in the directions.