Help Getting New Site Live via Network Solutions
Permalink 2 users found helpful
Hi there,
I am a complete newbie on websites and need some help...
I have a friend whose website is hosted by Network Solutions. I have uploaded C5 into her hpdocs directory on NS and created her new website there. The site is "live" if you use the url followed by "/concrete5-3.4.1.1 which takes you to my C5 index.php (home) page.
What I now need to do, is to get the site what I would call "properly live" so that when you put in her straight .com url you get to the new C5 site and the "/concrete5-3.4.1.1 piece of the address does not feature in the url of every page.
Having read some of the other posts here, I thought that it may have something to do with moving the C5 folder up to the root level as its own directory and then repointing the domain to the C5 folder (as opposed to the htdocs/concrete5-3.4.1.1 which is what NS advised me to do and does not work). When I tried to move my C5 folder up to the root level, it said that the root directory is not writeable...
Can someone let me know if getting C5 into the root directory and then redirecting the domain to the C5 directory is the way to go... and therefore now I only need to overcome the issue of root being writable, or am I on a wild goose chase and should be doing something completely different to solve the problem?
Many thanks (and sorry for such a long question)..
Loubelou
I am a complete newbie on websites and need some help...
I have a friend whose website is hosted by Network Solutions. I have uploaded C5 into her hpdocs directory on NS and created her new website there. The site is "live" if you use the url followed by "/concrete5-3.4.1.1 which takes you to my C5 index.php (home) page.
What I now need to do, is to get the site what I would call "properly live" so that when you put in her straight .com url you get to the new C5 site and the "/concrete5-3.4.1.1 piece of the address does not feature in the url of every page.
Having read some of the other posts here, I thought that it may have something to do with moving the C5 folder up to the root level as its own directory and then repointing the domain to the C5 folder (as opposed to the htdocs/concrete5-3.4.1.1 which is what NS advised me to do and does not work). When I tried to move my C5 folder up to the root level, it said that the root directory is not writeable...
Can someone let me know if getting C5 into the root directory and then redirecting the domain to the C5 directory is the way to go... and therefore now I only need to overcome the issue of root being writable, or am I on a wild goose chase and should be doing something completely different to solve the problem?
Many thanks (and sorry for such a long question)..
Loubelou
Dear Globalnerds,
You are a superstar! Thank you so much for your help. It is all sorted (except enabling pretty urls but I'll face that challenge tomorrow).
Many many thanks,
loubelou
You are a superstar! Thank you so much for your help. It is all sorted (except enabling pretty urls but I'll face that challenge tomorrow).
Many many thanks,
loubelou
The pretty urls are REALLY easy to re-enable. In the dashboard go to Sitewide Settings and then under the linking box, click enable pretty urls.
Can you close this discussion and mark it as helpful? Thanks!
Can you close this discussion and mark it as helpful? Thanks!
Basically, don't use Network Solutions. 3 years later they still have the same issue.
Especially if you are new to building web sites, you will get lost dealing with issues that NS has that nobody else (or any hosting provider that isn't a complete joke) has.
Ranging from root directories becoming randomly unwritable, to silently failing web application deployments, to a hellish web management interface (complete with broken back buttons and randomly expiring sessions), to unreliable SQL and Tomcat servers, yearly (at least) DDOS attacks, and on and on, NS is basically complete and utter crap.
Generally, it is very clear that the engineers responsible for NS's management interface have never once even remotely considered actually *using* their management tools to see how well they worked. Avoid at all costs.
If you run into "root directory is unwritable" errors; call support for a quick fix, but expect it to come back. Start looking for another hosting provider. These guys suck, they always have, they always will, and every single service they provide is an absolute joke.
Especially if you are new to building web sites, you will get lost dealing with issues that NS has that nobody else (or any hosting provider that isn't a complete joke) has.
Ranging from root directories becoming randomly unwritable, to silently failing web application deployments, to a hellish web management interface (complete with broken back buttons and randomly expiring sessions), to unreliable SQL and Tomcat servers, yearly (at least) DDOS attacks, and on and on, NS is basically complete and utter crap.
Generally, it is very clear that the engineers responsible for NS's management interface have never once even remotely considered actually *using* their management tools to see how well they worked. Avoid at all costs.
If you run into "root directory is unwritable" errors; call support for a quick fix, but expect it to come back. Start looking for another hosting provider. These guys suck, they always have, they always will, and every single service they provide is an absolute joke.
you needed to do that and go into your config/site.php and change the define('DIR_REL', '');
for example if your old one was
to use the site via the base url you would need to change this to:
note that after the comma those are single quotes without a space in between.
Once your site is ok using the base url, you can re-enable pretty urls again