Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

DataObjectManager Module /

Discuss the DataObjectManager module, and the related ImageGallery module.

Moderators: martimiz, UncleCheese, Sean, Ed, biapar, Willr, Ingo, swaiba

HTML 400 error


Go to End


1318 Views

Avatar
Bronwyn

Community Member, 22 Posts

22 March 2012 at 4:16pm

I just discovered a problem with my Department's actual live website. I moved it to a new server a couple of weeks ago and everything appeared to be going swimmingly, but I have just discovered I am unable to upload certain things.

I have Image_gallery, dataobject_manager, and swfupload installed with SS 2.3.10. On the new server I can no longer upload images, although I can upload other files.

In an image gallery page I can create, but not delete, a new album. I cannot upload images to the album. When trying to delete the album I get an error like so (in Firebug):
"POST admin/EditForm/field/Albums/item/20/delete?SecurityID=276c8564ce9d2feacee26274f8f10ad97f91c2de
400 Bad Request404ms"
when trying to upload an image I get a popup error saying "An error occurred in the upload. Try again later." followed by another popup with "There was a problem with the upload.
The server did not accept it."

In the files and images tab of the cms I can upload pdf files just fine, but I can't upload images to most folders. I seem to be able to upload them to my pdf folder (inside assets), but then I get the 400 error when trying to delete them. I also get the 400 error when trying to delete pdf files from this folder.

All of these folders are inside the assets folder and have the same permissions, and they have the same permissions as they had in the old server too - where they worked perfectly well.

Pulling my hair out - any clues anyone?