Lainaus käyttäjältä: SleePy - toukokuu 21, 2009, 01:57:37 IP
Lainaus käyttäjältä: fals - toukokuu 21, 2009, 09:35:53 AP
Only one downside - attached images cant have the same filename anymore
Not true. All attachments use a unique hash and id. So you do not have to worry about that.
Well, its true - on my forum after todays update.
I have testet, uploaded a file called
avatars-popup.jpg, then made a reply and try upload same file again:
LainaaAn Error Has Occurred! Sorry! There is already an attachment with the same filename as the one you tried to upload. Please rename the file and try again.

(http://img200.imageshack.us/my.php?image=errorvvj.jpg)
The uploaded file itself does have a hashed filename (when i tjek via FTP), but i still get the above error.

(http://img194.imageshack.us/my.php?image=filenames.jpg)
I have run manually trough Post.php, Subs-Post.php, all edits are ok.
Sorry for bumping - i still have this problem.
Anyone knows where to look ?
That's what my avatar problem is!
I couldn't change back after i changed it the other day.
I went in and changed the name of the file and i could upload the same image i had before just another name.
Problem solved ! 8)
I compared with my other 1.1.9 forum og found the "error" in the database settings.
smf_settings in phpmyadmin.
attachmentEncryptFilenames was still set to "0" :o
After a quick set to "1", everything works fine again
Thanks :D
I had exactly the same problem after upgrading from 1.1.7 to 1.1.10 ... users getting the error :
"Sorry! There is already an attachment with the same filename as the one you tried to upload. Please rename the file and try again."
Checked your suggestion
smf_settings in phpmyadmin.
attachmentEncryptFilenames was still set to "0"
and ... mine was set to zero too ... changed to 1 and all good ... now users can use the same attachment name many times over 8)
Thanks ... this was the 1st time I have changed a setting in the database ... and it worked fine :D
Funny thing, I have two forums, both came up from 1.1.7 to 1.1.10 ... one had the problem ... one didn't ... both were set to encrypt attachments (via the old method) prior to upgrade ...
Thanks for the solution. Still working on smf 2.0 rc4