21490 Posts in 5783 Topics by 2622 members
|Go to End|
15 November 2011 at 9:46pm
I've got a bunch of images in my assets folder, but when I insert one in my html, the image doesn't load and I get a 500 error. I'm using dataobjectmanager and uploadify. I've set all the folder permissions to 777. What the heck is wrong?
Any help would be appreciated.
15 November 2011 at 10:08pm
How do you try to insert the images in the theme?
Do you activated Dev Mode for more informative errormessages?
Director::set_environment_type("dev"); // _config.php
15 November 2011 at 10:54pm
Yep. I have dev mode on as well as verbose error messages. Silverstripe itself isn't throwing an error, the server just can't access the image files, thus the http 500 error. And it isn't images that I'm trying to insert into my theme. Those are all working fine, most likely because they are stored in the images folder within the theme folder.
The trouble I'm having is images stored within the assets folder which are supposed to be available to my client via the cms to insert into the content boxes via the tinyMCE editor.
If you take a look at the image I've attached, you'll see what I'm talking about. If I take a look at the page resources, it shows that each of those images is throwing an http error 500, i.e. they cannot be accessed. I've tried resyncing the image cache with dev/tasks, but that didn't help. I have no idea what else to do.
16 November 2011 at 10:26am
you say all images and even the /assets folder has the correct rights?
do you have ssh access? if so try this:
chmod 777 /assets -Rf
I had a similar problem and thougt I set all the rights correct with filezilla, but that dont worked ...
I also had problems like this when I use a http basic auth to secure the site with a pwd ...
16 November 2011 at 12:04pm
on some hosts i've seen smtg like this. the .htaccess in the assets-folder caused the problem. can you remove it just to be sure it's not the cause in your case?
16 November 2011 at 4:48pm
Weird. Deleting the .htaccess file fixed it. I'll have to take a look at the file to see why it was causing the issue. Thanks for the suggestion.
|Go to Top|