Community member page vs. Gallery:One user

[maxz]

<P>In an answer to a <A

HREF="http://www.photo.net/bboard/q-and-a-fetch-msg?msg_id=007f1B">recent

question</A> Brian explained that the "Community member page" was

unavailable unless you logged in. I guess that this is in response to

the last number of days trouble with heavy queries caused by the <A

HREF="http://www.photo.net/bboard/q-and-a-fetch-msg?msg_id=007dg5">off-line

readers/harvesters</A>.</P>

<P>I have a suggestion. Can we have a page where you can see the

biography, the portrait, the homepage link, list of folders and other

"inexpensive" information that you get to whenever clicking on a users

name on photo.net, that do not require you to be logged in? On this

page you could then have links to pages (which would require login to

prevent abuse/DOS-attacks) with responses, general comments, etc that

seem to be the cause of bogging down the system. These links could

even be hidden from someone not logged in and instead replaced with a

"To access more information about this user, please log in"-link.</P>

<P>It is nice to have summary pages that gathers all kinds of small

information about one user in one place, but when this page becomes

unresponsive and even slows the site, perhaps it is time to divide it

into smaller pages and require the viewers to select what they want to

look for.</P>

<P>Today we have the <A

HREF="http://www.photo.net/photodb/user?user_id=322007">Gallery: One

user</A> page where you can see the list of folders among other

things. This page does not require you to be logged in (is this

intentional?). But here you cannot see the biography for example,

something that might be interesting for non-members.</P>

[mottershead]

They are separate pages and they are different, although they call the same functions to generate their information and therefore a lot of the information is the same.

 

There is no good reason for there to be two different pages, and one day I will probably make /gallery/user be generated by the same script as /shared/community-member. I actually have this implemented on my development server. I'm just waiting for time to test and release it.