Skip Navigation

[Resolved] Add support for nickname to wpv-current-user

This thread is resolved. Here is a description of the problem and solution.

Problem:
How to display user nickname

Solution:
To display the nickname of currently logged in user, You can use following shortcode:

[wpv-user field="nickname"]

Relevant Documentation:
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-user

This support ticket is created 5 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by helenmaryC 5 years, 7 months ago.

Assisted by: Minesh.

Author
Posts
#1113601

wpv-current-user currently allows info= 'display_name' (default) | 'login' | 'firstname' | 'lastname' | 'email' | 'id' | 'logged_in' | 'role'

It would be useful if nickname was also an option.

Thanks!

#1114104

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Well - we have another shortcode which you can use to display the nickname of currently logged in user.

You can use following shortcocde:

[wpv-user field="nickname"]

More info:
=> https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-user

#1114331

Duh! I just assumed it would be part of wpv-current-user and didn't even look further.

My issue is resolved now. Thank you!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.