Liquid Web Breaking Images?
Permalink
Hi there,
We just set up an account with Liquid Web, running a cPanel server. We've found a really strange issue. On most sub-pages, the image blocks simply don't render, and if that happens, the rest of the system code fails to render as well, so no jQuery, no admin bar, no site edit features.
Also, frustratingly, there are no php or JS errors for me to go from. I placed a bunch of console.log() commands within the image block controller (/concrete/core/controllers/blocks/images.php) and can confirm that the entire php script does NOT complete, yet as I said there are no errors to be found.
http://64.91.227.177/~redskyma/...
Looking at the site with this URL will cause all sub-pages to 404, so don't be alarmed. I put the IP in my window's hosts file and am QAing it this way. When the DNS is swapped, it will live on:
http://www.redskymarine.com/
The crappy part: we developed this site on a different environment, and it worked fine (of course). We ftp'd the site files and copied the database over to the new environment, and these image blocks start having problems.
Anyone else had this problem with Liquid Web or cPanel?
We just set up an account with Liquid Web, running a cPanel server. We've found a really strange issue. On most sub-pages, the image blocks simply don't render, and if that happens, the rest of the system code fails to render as well, so no jQuery, no admin bar, no site edit features.
Also, frustratingly, there are no php or JS errors for me to go from. I placed a bunch of console.log() commands within the image block controller (/concrete/core/controllers/blocks/images.php) and can confirm that the entire php script does NOT complete, yet as I said there are no errors to be found.
http://64.91.227.177/~redskyma/...
Looking at the site with this URL will cause all sub-pages to 404, so don't be alarmed. I put the IP in my window's hosts file and am QAing it this way. When the DNS is swapped, it will live on:
http://www.redskymarine.com/
The crappy part: we developed this site on a different environment, and it worked fine (of course). We ftp'd the site files and copied the database over to the new environment, and these image blocks start having problems.
Anyone else had this problem with Liquid Web or cPanel?
I was doing some more digging, and know this this:
I think this issue might be related to the way either cPanel or CentOS or SOMETHING about the Liquid Web server configuration is causing the URL rewrites to fail on a fundamental level. Example of this is when we go tohttp://64.91.227.177/~redskyma/gallery/... and receive a 404.
However, if we go tohttp://redsky.myclocktower.com/gallery/... and take a look at how the images print out and how the Firebug Console looks. We should see A) the current page name above all images on this page, and B) the Firebug Console lit up with lots of image stats, like the image's height and width, rel path, full path, etc.
The Concrete5 CMS relies on getCurrentPage() to define the $c object to be defined in order to pull int he proper images for the pages.
If that object is NOT defined (ie, if the server can't interpret the url rewites, etc), the images can't be pulled up.
The difference between the Liquid Web Redsky and the myclocktower.com Redsky is that those page names aren't appearing above the images, meaning the Current Page object is not getting defined, and thus no images are available for retrieval, let alone output.
If we can solve the Rewrites issue, I think we'll solve the images issue, too.
I think this issue might be related to the way either cPanel or CentOS or SOMETHING about the Liquid Web server configuration is causing the URL rewrites to fail on a fundamental level. Example of this is when we go tohttp://64.91.227.177/~redskyma/gallery/... and receive a 404.
However, if we go tohttp://redsky.myclocktower.com/gallery/... and take a look at how the images print out and how the Firebug Console looks. We should see A) the current page name above all images on this page, and B) the Firebug Console lit up with lots of image stats, like the image's height and width, rel path, full path, etc.
The Concrete5 CMS relies on getCurrentPage() to define the $c object to be defined in order to pull int he proper images for the pages.
If that object is NOT defined (ie, if the server can't interpret the url rewites, etc), the images can't be pulled up.
The difference between the Liquid Web Redsky and the myclocktower.com Redsky is that those page names aren't appearing above the images, meaning the Current Page object is not getting defined, and thus no images are available for retrieval, let alone output.
If we can solve the Rewrites issue, I think we'll solve the images issue, too.
Going to see if this is a simple permissions issue at this point...