GoDaddy Install Troubles - Patch Done
Permalink
Hi all,
I am very excited about getting to use Concrete on a few sites and I generally use GoDaddy hosting. I researched this forum after having initial "site.php" troubles and found the GoDaddy php.ini patch as well as the modified base.php and request.php files.
After implementing the patch the installation completed, but the initial screen that appeared was Concrete content without any formatting. It was just a basic text page with links. None of the links worked. Clicking on any of them resulted in Page Not Found errors.
My assumption was that when I was asked for the Concrete path, I made the wrong choice when I entered (http://sitename/concrete). Since I uploaded the Concrete files to the root directory, I assumed I should have enteredhttp://sitename only.
I may have been right or wrong, but what I did to attempt to fix this was to dump all of the database tables in order to clear the installation, assuming it would bring back the initial setup screen when hitting the domain. Nope. I got a database error message instead.
I guess there's a file that's now been modified and is looking for database content in order to render the page, and it's no longer there.
I suppose I could reload the entire site and start from scratch again, unless someone can tell me what file(s) to edit to clear the initial configuration info and start fresh.
Another question is regarding the two URL's you're asked to enter as a part of the initial configuration form. One is the core site url, the other is the Concrete URL. If I upload the Concrete files to the root of the site, should both of these URLs be the same??
Thanks for any help,
Chris
Site URL:http://www.laketravislacrosse.org...
PHP Info URL:http://www.laketravislacrosse.org/phpinfo.php...
I am very excited about getting to use Concrete on a few sites and I generally use GoDaddy hosting. I researched this forum after having initial "site.php" troubles and found the GoDaddy php.ini patch as well as the modified base.php and request.php files.
After implementing the patch the installation completed, but the initial screen that appeared was Concrete content without any formatting. It was just a basic text page with links. None of the links worked. Clicking on any of them resulted in Page Not Found errors.
My assumption was that when I was asked for the Concrete path, I made the wrong choice when I entered (http://sitename/concrete). Since I uploaded the Concrete files to the root directory, I assumed I should have enteredhttp://sitename only.
I may have been right or wrong, but what I did to attempt to fix this was to dump all of the database tables in order to clear the installation, assuming it would bring back the initial setup screen when hitting the domain. Nope. I got a database error message instead.
I guess there's a file that's now been modified and is looking for database content in order to render the page, and it's no longer there.
I suppose I could reload the entire site and start from scratch again, unless someone can tell me what file(s) to edit to clear the initial configuration info and start fresh.
Another question is regarding the two URL's you're asked to enter as a part of the initial configuration form. One is the core site url, the other is the Concrete URL. If I upload the Concrete files to the root of the site, should both of these URLs be the same??
Thanks for any help,
Chris
Site URL:http://www.laketravislacrosse.org...
PHP Info URL:http://www.laketravislacrosse.org/phpinfo.php...
Well - The install went through again, but it still doesn't look like it's right. There's no formatting of the content, although I did get a nice pic of a grove of Birch trees this time...
Clicking on the link for Dashboard still throws a Page Not Found error, but it appears to be generated by Concrete rather than the web server.
Help?
Chris
Clicking on the link for Dashboard still throws a Page Not Found error, but it appears to be generated by Concrete rather than the web server.
Help?
Chris
Can anyone help?
Chris
Chris
I may come back to Concrete, but I can't wait so long for installation support.
Good looking product though...
Chris
Good looking product though...
Chris
I may come back to Concrete, but I can't wait so long for installation support.
Good looking product though...
Chris
Good looking product though...
Chris
These Forums are new, and not currently monitored by many users. Good luck. C5 was a troublesome install on my server but worth it.
chrison600,
I ran into the same problem on GoDaddy Shared Hosting, where the C5 dashboard site came up after install with no formatting. I'm not sure if this is what fixed it or not, but I ended up enabling "write" privileges for the entire C5 directory...
The other thing that it could be, is that the install page has a trailing "/" in it's example when asking for the install directory, but it really doesn't want that trailing forward-slash.
I don't know if this helps or not... I'm pretty new at this stuff.
I ran into the same problem on GoDaddy Shared Hosting, where the C5 dashboard site came up after install with no formatting. I'm not sure if this is what fixed it or not, but I ended up enabling "write" privileges for the entire C5 directory...
The other thing that it could be, is that the install page has a trailing "/" in it's example when asking for the install directory, but it really doesn't want that trailing forward-slash.
I don't know if this helps or not... I'm pretty new at this stuff.
Hey all,
I messed with MODx for a bit. Nice stuff, but I thought I'd try again with Concrete.
I tried the installation again using the 5.1 RC1 files. No GoDaddy patch. MySQL 5.0.
Installation went fine.
The only thing I changed other than using the 5.1 release candidate was the switch from MySQL 4.1 to 5.0. The variables required on the initial site setup screen have been reduced as well, which made the data required a little more straightforward.
So far, so good. Now I have to get the site looking/feeling like I want.
Actually, I think I'll blow away the MODx installation on the domain I want to use and reinstall Concrete there, so I'm actually working in the domain I intend to use.
I have some feedback on the installation instructions. Where should I send it?
Also, the forum search errors out, "Unable to complete search: Wrong segments.gen file format".
Chris
I messed with MODx for a bit. Nice stuff, but I thought I'd try again with Concrete.
I tried the installation again using the 5.1 RC1 files. No GoDaddy patch. MySQL 5.0.
Installation went fine.
The only thing I changed other than using the 5.1 release candidate was the switch from MySQL 4.1 to 5.0. The variables required on the initial site setup screen have been reduced as well, which made the data required a little more straightforward.
So far, so good. Now I have to get the site looking/feeling like I want.
Actually, I think I'll blow away the MODx installation on the domain I want to use and reinstall Concrete there, so I'm actually working in the domain I intend to use.
I have some feedback on the installation instructions. Where should I send it?
Also, the forum search errors out, "Unable to complete search: Wrong segments.gen file format".
Chris
Glad to have ya Chris..
Post your install feedback to this forum.
I bet search is punky cause we just moved this site to a new server, thanks for the heads up.
-frz
Post your install feedback to this forum.
I bet search is punky cause we just moved this site to a new server, thanks for the heads up.
-frz
just a note to anyone who came here that's running into the same issue I just ran into. I was setting up a c5 site on godaddy for a friend and the pretty urls weren't working, but apparently it just takes a little while for the .htaccess file to kick in (as jereme pointed out elsewhere). after a few minutes of just letting it sit is just started working.
A Japanese hosting company had the same problem.
And we fixed this by changing /index.php
Let me know if this works.
And we fixed this by changing /index.php
<?php if (isset($_GET["pathinfo"])){ $_SERVER["PATH_INFO"] = $_GET["pathinfo"] ; } require('concrete/dispatcher.php');
Let me know if this works.
Correct.
The first time you create a given .htaccess file on a Godaddy shared server, it will take up to an hour for the server to recognize the .htaccess file. Any subsequent changes to the file will take effect immediately.
The first time you create a given .htaccess file on a Godaddy shared server, it will take up to an hour for the server to recognize the .htaccess file. Any subsequent changes to the file will take effect immediately.
Chris