Hello, what about a username variable in comments?
To know what I mean, please watch
http://expressionengine.com/forums/viewreply/365460/
thanks you )

Doesn’t {author} solve this? Also, check this variable list.

*** EDIT ***

Ignore me. The screenshot didn’t load on the last page so I missed what you meant. Sorry.

Deviance - 01 April 2008 12:03 PM

Doesn’t {author} solve this? Also, check this variable list.

In this variables no “{username}”

I understand what you mean now and agree that would be useful in some situations. I can’t believe it isn’t already available.

Qrat, if you want to know why it’s because the users screen name is stored in the same table as the comments. This gets pulled out as the {author} instead of data being made available from the members table.

I guess my reason to have this feature is becuase the user’s screen name at the time of commenting will be permenantly attached to the comment. If a user changes their screen name their old one will still show for the comments made using it.

A permenant fix would be to modify the comment module with an SQL JOIN for the members table but I don’t need this feature right now so hopefully this feature will get implimented by the EE team.

I would like this feature as well so I can link to a member profile (i’m using solspace’s user module) using the the username in the url rather than the member id.

Hm, you could pack this into a plugin, but why not just using the query module?

Let me know if this works, worked for me on my test site.

Selecting more, you can fetch all the data from the members table.

You can just do (I think)...

The point is both approaches generate needless database queries. You could just do the whole retrieval of the comments using the query module joining the member data but it would be preferable for this facility to be built in. Hence the support of the feature request.

Thanks for the suggestion though.

mreeves - 05 June 2008 03:27 AM

You can just do (I think)...

{exp:member:custom_profile_data member_id="{author_id}"}{username}{/exp:member:custom_profile_data}

The point is both approaches generate needless database queries. You could just do the whole retrieval of the comments using the query module joining the member data but it would be preferable for this facility to be built in. Hence the support of the feature request.

Thanks for the suggestion though.

Yes, this should work too, but here you’r invoking the entire member field module and selecting all the fields whereas with the query module, you can just select the “username” field. Nevertheless, you have to do one query for each comment being displayed.

mreeves - 05 June 2008 03:27 AM

You can just do (I think)...

{exp:member:custom_profile_data member_id="{author_id}"}{username}{/exp:member:custom_profile_data}

The point is both approaches generate needless database queries. You could just do the whole retrieval of the comments using the query module joining the member data but it would be preferable for this facility to be built in. Hence the support of the feature request.

Thanks for the suggestion though.

It required more queries than peschehimself’s way I think

Fair comments. To improve further on above…

Elimiates the need for the join.

Best regards
Martin