It turned out that somewhere along the way safe_mode had been turned on. No idea how. The site was definitely set up with it turned off!
I think what happens is that safe_mode checks if files are owned by the same user that’s updating them. In the case of the image cache - parts of it were owned by apache and parts were owned by the main owner of the site. So safe_mode was preventing the server from generating the cached images.
I may have the details of the explanation wrong. And it may not be a universal cure. But it’s worth checking! It fixed it for me!!
I am in the same boat as you guys. Tried all the suggested mods (even though I am not a big fan of modifying the core files). Did anyone come across a solution. Please help!
So I saw the desperation in this thread and thought I would chime in and see if I can provide some insight for this..
Here is from a post that I wrote a while back…
This is a big issue.. I am developing on a MAMP case in sensitive system and my LAMP remote system is case sensitive..
I was able to resolve it with the tips in this thread:
http://www.magentocommerce.com/boards/index.php/viewthread/38352/
Running that script did not solve all my issues though, I actually had to upload the upper case folders as well.. basically all images uploaded before the 1.3.2.1 upgrade use uppercase folders and file names, and anything uploaded after 1.3.2.1 use lower case.. [this was after running the scripts provided on that thread]
Cheers,
J
I ended up having to maintain image directories that have upper and lower case folder names, I still run into image placeholders showing up every once and a while but the issue is more or less resolved for me..
The key to finding out if this is the issue is to check the file paths and determine if your install is looking for an “A” instead of an “a” ...
Hope it helps. I have now learned to develop locally on a case-sensitive partition…
I was having this issue as well; Images in the admin area were fine, but only the placeholders displayed on the frontend. This happened after I moved an install from a development location to a staging location. Magento would not create the product image cache because of this.
Check your phpinfo() and look at the GD section. If you don’t see:
I was having this same problem until now. Here’s the deal…
When specifying the amount of memory in your php configurations, you have to specify the M in uppercase. So, there are a few places you can specify it: index.php, php.ini, or .htaccess.
In all places I was using “512m” and no pictures would load, although the rest of the site was fine. I changed it to “512M” and voila!
Here’s an example for each of these three files:
index.php would be:
ini_set('memory_limit', '512M');
php.ini would be:
memory_limit = 512M
.htaccess would be:
php_value memory_limit 512M
You don’t necessarily have to use 512, but be sure that you are using an uppercase M.
First if you are moving your old media folder to your new install, then you might have capital letters in your Media/catalog/product/ folder.
it may look like this:
a
b
C
D
e
f
G
etc
When, i moved my media folder over it kept the capitalized letters while my new install was looking for lower case letters. To check this go to the admin and the go to a catalog item. When you mouse over the images you will get the x or broken image. right click and then choose inspect element.
This will give you the url of the image your install wants. then check that path with the path in your ftp program and make sure that the capital and lower case letters match.
Problem for me is still unresolved as no fixes here worked.
I am on a fresh install of 1.4.0.1
seems like a bug to me. Havent changed the core at all, as a matter of fact i havent changed ANYTHING. i just did a clean install and added a product. broken right out of the gate.
it looks like image.php is creating some convoluted path where the file doesnt exist.
the file is at
/[docroot]/media/catalog/product/f/i/file_9.jpg but the script is loading the path as