Topic: per_member_upload to use original username?

[Teme]

per_member_upload
Turning this option on will force users to upload photos into their own directory. They will not be allowed to pick a category, and will not be allowed to upload into any other directory. If a directory for that user does not already exist, one will be created when that user uploads their first photo. They will no longer be presented with a "category" list, any photos they upload will automatically be saved into their personal directory.

This is very nice feature but there's one annoying thing about it. It uses only the member's custom name he's chosen instead of original username. Therefore user can make a new album by changing his name. It would be much better if only the original usernames that cannot be changed afterwards could be used for new user directories? Hopefully it can be done...

[Mike Bobbitt]

Good point. I'll have to look into that and see what I can do about it. Should be easy to do, but not so easy to stay backwards compatible...

[Teme]

Good point. I'll have to look into that and see what I can do about it. Should be easy to do, but not so easy to stay backwards compatible...

There's new version out know - have you included this fix in it?

[Mike Bobbitt]

Sorry, haven't gotten around to this one. Keep reminding me though, and I'll try to get to it...

Cheers

[Teme]

Sorry, haven't gotten around to this one. Keep reminding me though, and I'll try to get to it...

Cheers

You can count on me, not even a ban could stop me reminding you.
Hopefully you'll manage to make it as I really would like to use this.

[Teme]

Just reminding you. I'm going to need this kind of album soon...

[Mike Bobbitt]

You're talking about UBB, right?

[Teme]

You're talking about UBB, right?

No I'm using (this forum) YaBB SP1.1 but UBB might have same feature to change nick name. I don't know if the problem occurs with that. But it is at least with YaBB.

[Mike Bobbitt]

I looked at the code (finally) and it's a YaBB only problem. At any rate, it's now changed to use usernames. Hope this isn't going to cause too many people work!

Cheers

[Teme]

I looked at the code (finally) and it's a YaBB only problem. At any rate, it's now changed to use usernames. Hope this isn't going to cause too many people work!

Cheers

Thank you very much for the fix. What file should I use now? Is the version from front page updated yet? There still reads it's V5.6 so does read in album.pl file but if I look at the readme of the zip it says there should be version 5.7 which is dated 02/07/21 isn't that an old date too as it's now 24th day?
Still there stands in the modifications list of v5.7: "Changed YaBB per_member upload mode... "

Pretty confusing, isn't it?    Or have I missed something?

[Mike Bobbitt]

No, you didn't miss anything, it's just confusing...

The file you downloaded has the fix in it. I keep updating the download .zip file, but rather than increment the version number each time (a real pain) I wait until there are a bunch of changes and then release a new version.

But in the mean time, I keep track of all the changes in the revision history, under the next version number (in this case, 5.7). I stuck in the date of the 21st weeks ago, as an estimate of when 5.7 might be released. That date has come and gone, but I haven't updated it in the file to my next "guess" yet.

[Teme]

ok, that's good to know. Thank you.
Maybe some sort of message in the readme section that the files are updated but the version number hasn't been changed before actual release would be good.

[Mike Bobbitt]

Well that's kind of what the revision history part is. If I waited for the next real "release" to put new code out, I'd keep people waiting too long. (And this way, it gets tested before it gets too far... )

[Teme]

ok.


I've a tiny problem though... Looks like both "Apply" and "Reload" button do the same job which is Reload the page when I do the first time settings. I've chmodded the files correctly but it just simply won't accept any changes just reloads the first time configuration page.

With version 5.4 on other server it said after configuration: "Your configuration has been updated. From here, you have the following options". What should I do?

[Mike Bobbitt]

This sounds suspiciously like the caching problem I thought I fixed. If you in IE, hold down CTRL and click refresh after you've submitted the new config, and see if it changes the response...