Upload to /Userpics instead of /userpics/user directory Upload to /Userpics instead of /userpics/user directory
 

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

Upload to /Userpics instead of /userpics/user directory

Started by marcamillion, July 29, 2006, 12:31:33 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

marcamillion

I am just realising now, after examination of my db, that cpg has been uploading user pictures to the root userpics folder, and not to the specific user folders. I have a total of about 34,000 rows in my site_pictures table, and this problem started happening at about 16,500. I think this is where I had given some users the ability and instructions to do xp_publish upload, but I am not 100% sure. So the main problem is that about a third of my, 29,000 user-uploaded images, are all in the root /userpics folder, and I would like to put them back where they belong, and fix the db accordingly.

What would have caused this problem to start, and where can I get help on fixing it?


I did search the boards and havent been able to find anything of this sort.

Joachim Müller


marcamillion

So how do I disable silly_safe_mode, and how do I fix this mistake and put all the pictures in their rightful folders?

Nibbler

You remove the silly_safe_mode define() from include/config.inc.php. Moving the files into subfolders is a matter of moving the files physically and then updating the references to them in the cpg_pictures table in the db.

marcamillion

Are there any repercussions of me removing silly_safe_mode ? I think my server has safe_mode enabled, is that why this "function" kicked in? I don't want to change anything that will spark other problems that I might not have anticipated.

Joachim Müller

It didn't "kick in" - you must deliberately have enabled it by editing said file. Refer to the docs.