Due to my hosting company moving to a different server, I believe one of my installations of concrete has become corrupt. Or that is my best guess. My other concrete installations that were also moved continue to function properly.
If I do a complete reinstallation of concrete, would my original site remain intact if I pointe the new installation to the database file from the original installation by updating the database.php file in the config folder under the application directory?
Or is it more complicated than that?
Thanks for all the help!
John D.
Update: Here are more details.
The hosting company switched from apache to OpenLiteSpeed. (I have other Concrete installations which made the transition without a problem.)
When I load truthfactor.com/index.php, it opens to a blank page and when looking at the Elements (F12) I see the following:
body data-new-gr-c-s-check-loaded=“14.1235.0” data-gr-ext-installed=“”
div class=“theme-atomik ccm-page ccm-page-id-1 page-type-page page-template-full”
/div /body
However, when I try to load the login page (Human verification) I get the “This page isn’t working” page.
Does anyone have thoughts on what may have happened?
I would rather solve the problem than do a complete re-install and rebuild.
Thanks!
John Duvall
The first URL displays stuff for me. The ‘Human verification’ URL is reporting a 500 error so can you find your error logs on the server and see what it’s reporting?
If you think Concrete files are broken, you can copy the /concrete/ directory from a zip over your site’s /concrete/ directory. That won’t be a reinstall. It won’t loose any content. But you can be sure you have all the correct files.
When an environment changes, its not unusual for cache files to become broken. You can manually clear the cache by deleting the /application/files/cache/ subdirectories.
If you have phpMyAdmin, look at the database directly for the last few entries in the Logs table. That may provide more information on what is broken.
From your host cPanel you can also browse the files beneath /application/config/ and:
- disable all caches
- set database entities into development mode
- disable pretty urls
- enable full debug output
All of which may enable you to get back into the site and dashboard.
Hey JohntheFish! Thank you so much. The problem was the /application/files/cache directory. As soon as the cache directory was cleared, the page loaded up.
Thanks again!