Can I reinstall Concrete and link it to the original DB safely?
Permalink
I started to build a new version of a site in a folder, and when I was happy with it I moved it to the root directory to have it seen by the domain name. I found one thing to fix in the config directory and now it works, but another domain I was trying to set up in a directory is having issues. I have a handful of sites running without incidence (though the version 5.3 sites load much faster than the 5.4 sites). This new domain won't load the site in the directory, it loads the site at the root level.
If I were to just reinstall Concrete5 in my root directory and link it to the same MySQL db will I lose my content? I am using a downloaded template currently, not one of the two defaults, and some free add-ons. No paid for add-ons.
Or should I only reinstall selected folders?
If I were to just reinstall Concrete5 in my root directory and link it to the same MySQL db will I lose my content? I am using a downloaded template currently, not one of the two defaults, and some free add-ons. No paid for add-ons.
Or should I only reinstall selected folders?
Interesting dilemma. Here's a little more background about my problem.
I have a domain name that when I point it to the folder in my hosting account where the right iteration of Concrete5 is it keeps resolving to the primary domain associated with the hosting account. But if I point the domain to another folder running another Concrete5 install that domain loads correctly. So clearly something it wrong with the instal of Concrete5 in the target folder.
What could be configured to prevent the site from loading and revert to the root directory? I can log into the admin account if I point to the directory address, not the domain name. I can view the site too. There are a bazillion files in the directory so any thing that will narrow down the search would be appreciated.
If I initialize another Concrete5 install in a second directory and point to the same MySQL database will it erase all the content? I haven't built lots of pages, but enough that migrating to another installation would be a hassle.
I have a domain name that when I point it to the folder in my hosting account where the right iteration of Concrete5 is it keeps resolving to the primary domain associated with the hosting account. But if I point the domain to another folder running another Concrete5 install that domain loads correctly. So clearly something it wrong with the instal of Concrete5 in the target folder.
What could be configured to prevent the site from loading and revert to the root directory? I can log into the admin account if I point to the directory address, not the domain name. I can view the site too. There are a bazillion files in the directory so any thing that will narrow down the search would be appreciated.
If I initialize another Concrete5 install in a second directory and point to the same MySQL database will it erase all the content? I haven't built lots of pages, but enough that migrating to another installation would be a hassle.
The plot thickens.
I set the domain to resolve to other folders in my hosting account and they worked fine. I pointed to a folder with a new Concrete5 installation and it took me to the set up page. I created a new database and configured the new site. It then resolved to the route directory of my hosting account.
So perhaps the issue is with the copy of Concrete that is sitting in my root directory. Hope this isn't impossible to fix.
I set the domain to resolve to other folders in my hosting account and they worked fine. I pointed to a folder with a new Concrete5 installation and it took me to the set up page. I created a new database and configured the new site. It then resolved to the route directory of my hosting account.
So perhaps the issue is with the copy of Concrete that is sitting in my root directory. Hope this isn't impossible to fix.
I don't know... there's only 2 places in Concrete5 that could cause such problems -- either the config/site.php file (the BASE_URL and DIR_REL definitions), or the .htaccess file (the REWRITE_BASE setting). If you've ensured that those have the proper settings, then the problem must lie with the DNS settings or your host's settings.
You can test this out by temporarily renaming the "index.php" file in your site to something else (like "index.php.backup"), then making a new index.php file with just some text in it. See if that file comes up or not -- if it does, then the problem is with C5. But if it doesn't, then the problem is with the server settings. If you do this trick with the "plain old php file", then your web host should be able to help you out more (sometimes if you mention you're using a CMS system they will not know what to do, but if you can demonstrate that the problem is there even with static files, then they'll be able to isolate it better and be more helpful).
Good luck.
-Jordan
You can test this out by temporarily renaming the "index.php" file in your site to something else (like "index.php.backup"), then making a new index.php file with just some text in it. See if that file comes up or not -- if it does, then the problem is with C5. But if it doesn't, then the problem is with the server settings. If you do this trick with the "plain old php file", then your web host should be able to help you out more (sometimes if you mention you're using a CMS system they will not know what to do, but if you can demonstrate that the problem is there even with static files, then they'll be able to isolate it better and be more helpful).
Good luck.
-Jordan
OK, problem solved. I didn't have the domain pointing to the actual domain when I created the site so I put in the working address at some point in the set up. Every time I reviewed the config>site.php page the values made sense to me, but a quick change to the actual domain name (without the www I gather so it works with and without?) and removed the directory name and now it works fine.
Still in the base template. Something to mess with another day.
http://ahts.org
Still in the base template. Something to mess with another day.
http://ahts.org
To be on the safe side, before deleting anything go to the Dashboard and run a database backup and then download the file for safe keeping.
Also copy the site's "config/site.php" file.
Then when you re-install the concrete5 files on your server, put the old "site.php" file you copied into the new "config" directory (do this BEFORE hitting the site in your browser) -- I believe this will let concrete5 know that it doesn't need to run the installation script and instead can just use the old database.
Note that you will have problems with whatever files were uploaded (images, etc.) though -- the database will have links to them in the /files/ directory but you just deleted them in the re-installation. So you probably want to copy those before deleting the old site as well.
Hope that helps.
-Jordan