|
It is possible to do, but I don't want to issue two additional queries for every user profile that is displayed.
On the old album, users are no longer associated by any other means than a username match. In fact, if you have pics in the old albums it is best to just re-upload them into the new member album and notify me to delete the old. The original album has existed so long that it is impossible to significantly reduce it's size, too many users have come and gone since 2001. The bottom line is that in two years, the old album will exist almost purely has a historical reference for folks who just want to browse older pics.
The New Member album does share a relationship to the user's profile, but since not everyone has an album I don't want write an additional database query to validate the presence of an album and then have to code a if/then statement to validate if a link needs to be displayed or not. As easy as the current member album is, only a small percentage actually contribute to it.
I have thought about adding a custom field where members can input the URL to their Member Album, which is quite easy to setup and easy to display (because the query is already done, I would be just displaying an additional bit of info within a member database record). However, I would have to consider some sort of validation process so that malicious users couldn't use it as a means to register and then encode a misleading URL in their profile.
As simple as it is for users to just input their two album URLs, it seems like sticking with that is the best solution for now.
Besides, when the Member Album is upgraded I'm going to re-introduce some features (such as Member-Owned Feature Albums, UserGroup-Owned Albums, and increased pic filesize limits) which will create some question as to what album a user will want to display in their profile.
It is a good suggestion though, keep em coming!
__________________
|
Linear Mode
