Installing on GoDaddy

[4erika]

I am in the process of installing the Shopsite pro app on my GoDaddy account. I'm already stumped and don't want to mess things up.

I already have a website up and running. I don't want to accidentally overwrite my current website, but I don't want to put it into a subfolder and have to move all the files later.

My plan is to name the new homepage, AmerikanBodyArt.com/index2, and then to just change the "index2" to "index" when I have the new website all built and am ready to overwrite the current website.

In order to install the app, it's asking me which directory to install it into or if I simply want it in the root directory. Any suggestions on how best to proceed?

Thanks!

[4erika]

Here's what the prompt looks like. It's the warning that freaked me out and made me think I better ask before proceeding.


Choose install directory

Install it into a folder:


http://www.amerikanbodyart.com/________________________________________



WARNING: Installing ShopSite v11 sp2 r5 into an existing directory can overwrite existing files.

[loren_d_c]

GoDaddy does their own stuff to install ShopSite automatically, but I would imagine the only file you might have to worry about being overwritten is your index.html page. So as long as you have a backup copy of that page, then you should be fine to go ahead and install ShopSite there.

Note that if ShopSite's Setup Wizard (that you will go through when you first login after installing) should detect if there is already an index.html page and not overwrite it. In that case it may automatically name the first page you create in the Wizard something like ss-index.html.

-Loren

[4erika]

Thanks, Loren. I'll give it a go.

[4erika]

Well....I can't say that went well. It did do the thing where it asked if I wanted to overwrite my index page. I said no, so it gave it the ss-index designation (which I later changed to index2). But when I went to look at my website, the home page of my current website was hosed up, and after a few minutes, I checked it again, and now it says access is forbidden. I checked both AmerikanBodyArt.com/index and AmerikanBodyArt.com/index2 and both are "forbidden." I thought it wouldn't affect my current website at all as long as I gave the pages addresses that were different from my current url's. Not sure what to do now. It will take me at least several days to build the new website and I can't have the old website down that whole time. Any ideas?

[loren_d_c]

Maybe the GoDaddy installer screwed with the file permissions. Make sure the home directory has 755 permissions and the index.html file has something like 644.

-Loren

[4erika]

Where would I see those numbers? I'm looking at the file management, and while it allows me to set file permissions to web viewable, writable, or executable...there are no numbers listed anywhere that I can see. I thought maybe changing the new website home page "index2" to not web viewable would help, but it didn't.

[loren_d_c]

Is there an Advanced option in the permissions list? Sorry, I am not familiar with GoDaddy's web interface. Directories should have execute permissions. For directories, try enabling all of the options. For .html files, read and write should be sufficient.

BTW, I can see the ShopSite page at www.amerikanbodyart.com/ss-index.html. The images missing from your regular home page is probably because of a permissions problem with the /images directory (which is not a ShopSite directory, so it should not have been messed with, but like I said, I don't know what else GoDaddy's install process might entail above and beyond the normal ShopSite install process). So try giving all permissions to the /images directory and see if that helps your homepage issue.

-Loren

[4erika]

I had to use filezilla to look at the permission numbers, and they are all either the numbers you recommended or above. So I'm guessing permissions is not the issue. I'm wondering if I should delete the old website and just pull a couple all-nighters to get the new website built.

[loren_d_c]

Sometimes 'above' is not good for permissions, i.e. there are often security checks built into the webserver that prevent access if there are 'too much' permissions. 755 should generally be good for directories and executables, and 644 for .html pages and image files.

-Loren

[4erika]

Thanks, Loren. Between you and Google, I was able to figure out what I needed to do. I managed to aquire Filezilla, learn how to use it, figure out what permissions are, and how to change them all in one evening.... The site seems to look like it did before. I wonder why GoDaddy would mess with the permissions just because I added an app to the account. Oh well, at least I learned some new stuff.

Now I hope that I can just work in the background by giving the new website different page names as I had intended.