[Solved]: Can no longer add new files "The previous file could not be placed" [Solved]: Can no longer add new files "The previous file could not be placed"
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

[Solved]: Can no longer add new files "The previous file could not be placed"

Started by scatteredbomb, April 24, 2008, 04:17:05 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

scatteredbomb

This just started happening very recently (this week), but everytime i try to upload a file, either a single file or using the batch add i get an error.

When i try uploading a single file i get "The previous file could not be placed". When i try to add a batch file i get this as a result error "Unable to create thumbnail or reduced size image."

As far as I'm aware, nothing was changed on the server but I'm not really sure what could have changed to cause the problems. I've double-checked the permissions for the folders, all of which were set to 777.

i was running 1.4.2 when the problem started. I did successfully upload some images earlier this month. When this problem started, i upgraded to 1.4.18 and still can't get it.

Link to the page is http://www.greendayauthority.com/Picture_Vault/
user: test
pass: test1

Anyone have some ideas?

ammo

Our Gallery is having the same problem. We've updated, have GD2, 777, changed our password, etc. All our pictures show up and such, but we can't upload anything new. Just get to the upload page. It says sucessfully placed files, but they aren't there.

Joachim Müller

@scatteredbomb: do exactly as suggested in the upload troubleshooting section of the docs: set the number of file upload fields to 1, the number of URI upload fields to 0 and enable debug_mode for everyone.

@ammo: the same piece of advie applies to you:
Quotedo exactly as suggested in the uplpad troubleshooting section of the docs
Do so in your own thread.

scatteredbomb

Alright, did that. Debug is now setup along with the upload limits.

plorimer

Hi

Did you get it fixed?

If not look at your php info. I rather fancy that you have safe_mode enabled. Disable it and your uploads will work.

Hein Traag

Or read the documentation on how to deal with silly_safe_mode..

scatteredbomb

Am i missing something in the phpinfo that shows the safe mode on? This is what i see

[Edit GauGau] Replaced hotlinked image with attachment [/Edit]

scatteredbomb


scatteredbomb

Sorry for bumping this, but I'd really like to get this all sorted out. I really need the gallery right now.

can anyone take a look and see what i'm missing or what i need to do?

Joachim Müller

The error message you get is
QuoteCritical error
The file 'albums/userpics/10024/flower2.jpg' can't be inserted in the album

Unable to create thumbnail or reduced size image.

File: /var/www/vhosts/greendayauthority.com/httpdocs/Picture_Vault/db_input.php - Line: 402
What's your method for resizing images (set in coppermine's config). If it's ImageMagick, try switching to GD2. Also review your settings for "Max width or height of an intermediate picture/video" - make sure it's set to a value that actually makes sense (if it's set to "1", you have been hacked). Additionally, if this doesn't help, review your permissions for the albums folder - make sure that the webserver has write permissions.

scatteredbomb

oh man, that was simple enough. it was the 'Max width or height of an intermediate picture/video" setting.

It was hacked last month, i did do a fresh install of the software and got it all upgraded to 1.4.18

Thank you so much for helping me catch that.

Joachim Müller

Performing a fresh install is not a bright idea. You appear not to have have performed one anyway if those settings were changed. You should have read the sanitization thread and done as suggested there instead. Anyway, marking as "solved".