Hi, Thank you for your reply. I follow what you say but after a bit of further investigation I found that it only appears to be relevant to images which are presented using 'image.php'. Other images displayed without using image.php appear fine.
I have compared both the working site and my non working copy, and using google chrome to inspect the elements both are letter for letter identical including the trailing slashes before assets/images/IMAGE-FILE-NAME.jpg.
For clarification the working site shows <img src="/image.php?src=/assets/images etc and works with the slash before the word assets.
The site uses the snippet phx:phpthumb and looking through these files it seems to say it needs the trailing slash in order to work.
So in my limited understanding...
I have been given the original site in a zipped format. I uploaded it and unzipped it so all files and relevant folders should be the same. After clearing the cache all content and pages are generated correctly ( albeit with the new domainname ), images embedded with the command img src="assets/images etc" display , it is only the image.php parts that do not work.
The only differences I think there will be are:
1. different host and global settings ? ( I found others mentioning magic quotes ON causing problems with some users of phpthumb - this appeared to make no difference)
2. different directory structure ? I think that I must have this correct otherwise you cannot browse files via Elements > Manage files, and images display not using image.php.
3. Possible different MYSQL Settings? Modx site appears to use character coding Unicode (UTF-8) on both New and old hosts, however new MYSQL host uses UTF, but old host Reports - System Info appears to show Database Charset Latin1 and Database Collation Charset Latin1_Swedish_ci.
Rightly or wrongly I discount the SQL mismatch because the produced cached php files appear to be generated correctly... so I think there must be something to do with either the different host settings or directory structure.
phpthumb appears to have numerous options. Is there a way to generate useful error?
The best I can get is:
"Resource interpreted as Image but transferred with MIME type text/html:"
googling this suggests many causes including:
- your suggestions of image path set incorrectly.
- image is sent with wrong headers, add headers to image type via .htaccess
- capital letters on imagenames
So I think it is more specifically to do with the phpthumb settings ?
Also I just remembered I had to set Validate HTTP_REFERER headers to NO in order to get the manager to work initially - Could this be the reason?
Apologies for the long-winded post.
