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're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Installing SilverStripe /

Getting SilverStripe up and running on your computer and on your web server.

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

files and images newfolder problem

Go to End

3 Posts   1695 Views


Community Member, 10 Posts

9 March 2010 at 7:25pm

I've installed silverstripe on the same server several times (different sites) and this is the first time i've had this problem.

when installing 2.3.6 i unrar to my ftp client (firefox) and it uploads to my server
i follow the install process and everything installs fine. i can create the website.

i came across a problem when i access the Files and Images in admin
I click on Uploads and create a sub folder
it creates a name called NewFolder
When I try to rename it to anything else I receive an "Error saving content" message.
When I attempt to upload an image file it appears to upload, but the file list displays "newFile" but no extension.
I cannot access this file when going to add it from the content editor.
When I go back to Files and images to browse the assets, it is gone. Only the "NewFolder" appears.

The folder permissions are set at 777 for assets/uploads as per install messages.

What is going on here? Again, first time in about 5 silverstripe installations.



Forum Moderator, 922 Posts

9 March 2010 at 9:10pm

Have you tried using the Firebug extension to Firefox to find out what the error was? "Error saving content" will always appear, but the full error can be grabbed by enabling Firebug extension in Firefox for your SS site, and watching what happens in the console.


Community Member, 10 Posts

18 March 2010 at 1:52am

Turns out it is a safe_mode issue in php.ini. make sure it is off!