Our Concrete5 install is giving us errors we've never seen on any other host. We've tried to install various version of the CMS but we always get the same errors. The first issue came up on the install screen. Two of the "Testing Required Items" get stuck in a loop and the rainbow wheels just keep spinning. This can be seen at http://220.127.116.11/~nappaa6/test4/ We can get around this by installing COncrete5 through the cPanel. Once it's installed though we get the same stalling problem whenever we add or edit a Block. The Error Logs don't show anything. Has anyone experienced anything like this?
Did you ever get past this? I am finding the same thing today, so apparently it is still an issue...
<div style="background-color: #FFF; padding-left: 10px;">Hello KenWilson, and thanks for commenting and letting us know these problems might still be persisting.
Are you also attempting to access your Concrete5 installation over the <a href="http://www.inmotionhosting.com/support/website/how-to/using-your-temporary-url" target="_blank">temporary URL</a>, or just using one of your domain names? Sometimes accessing a CMS over a temp URL can lead to redirection issues.
Are you also getting any specific error, or simply encountering a looping scenario like was originally mentioned?
If you can let us know the steps you are taking, we can attempt to replicate these problems and provide a solution for you.
We're going to need a little more information to troubleshoot the issue. First, I tried looking at how your installation is configured, but certain configuration files were not present (in the test4 folder). What domain did you specify during the installation stage? If you used your primary domain, then that will be the most likely source of the issue since your domain is not pointed to our servers. Additionally, you mention that you installed it twice. Did you remove the previous installation before proceeding with the current one? Please provide us some information on the installation and we will be happy to investigate into the issue further.
If you have any further questions, please contact technical support or leave a comment at the bottom of the page.
I was using one of my domain names, not the temporary URL. No specific error is returned, it just continues to loop within the initial installation checks, as reported above. The first check is for, "Supports concrete5 request URL's" and the second is for "Cookies enabled." I am starting with a blank site, and the current Concrete18.104.22.168 install. Had not modified anything until after I began troubleshooting. I can confirm the "Softaculous" automated install works fine (tested that too), but was simply trying to do this manually.
So I did some further digging after I also tried a manual install of the latest <strong>Concrete5 (22.214.171.124)</strong> from their website, and also encountered this hanging scenario when attempting to manually install it.
It seems that the <strong>Supports concrete5 request URLs</strong> and <strong>Cookies Enabled</strong> checks both hang with the little loading icons just continuing to display.
This seems to be happening due to a ModSecurity error on the server getting triggered when the install process attempts to access the <strong>concrete/js/jquery.cookie.js</strong> file.
It turns out that a lot of people experience this issue, and the easiest solution I've seen that I've confirmed fixes it, is just directly access the setup part of the install and skip the check screen with the following URL format:
The ModSecurity error appears to keep happening, but it doesn't stop you from finishing the install process. Another alternative would be to <a href="http://www.inmotionhosting.com/support/website/modsecurity/disable-mod-security-via-modsec-manager" target="_blank">disable ModSecurity with the cPanel Modsec Manager</a>, and then install Concrete5, but we would highly discourage leaving ModSecurity fully disabled as it can help protect your website against a lot of common threats.
Aside from that it sounds like the <strong>Softaculous</strong> install still works without any issues, and appears to be the exact same version as a manual install so I would recommend using that if you keep encountering problems.