Data

User Fields (Blocks)

User Fields extend WordPress user profiles with your own fields — job title, bio, avatar, social links — stored in user meta and displayable in blocks. They are the per-author layer of Tiger’s dynamic content. Where: WP Admin → Tiger Blocks → Data → User Fields. Enable the engine under Modules & Widgets → Dynamic Content. […]

2 min read Updated July 14, 2026

User Fields extend WordPress user profiles with your own fields — job title, bio, avatar, social links — stored in user meta and displayable in blocks. They are the per-author layer of Tiger’s dynamic content.

Where: WP Admin → Tiger BlocksDataUser Fields. Enable the engine under Modules & WidgetsDynamic Content.

Add profile fields

  1. Add a field and choose a type — the same set as Site Options (Text, Textarea, Number, Email, URL, Phone, Date, Color, Select, Image).
  2. Give it a label and a key.
  3. Save. Each field then appears on the user profile edit screen (both Your Profile and Edit User) and saves to user meta under tcp_user_<key>.

Display them

Bind a user field into a block with the author.<key> source, which resolves to the current post’s author. That makes User Fields ideal for author boxes, team listings and member profiles — the data you collect on the profile screen shows up in your design automatically.

Because the accessor and profile hooks load on the front end regardless, bindings keep resolving even when the admin definition screen is only available while the data engine is active. Combine User Fields with the Team or Post blocks to build author bios that stay in sync with each user’s profile.

Troubleshooting

My author.key value is blank on a page

The source resolves to the author of the current post, so it needs a singular context with an author — a single post or a template that has a queried post. On a static page with no meaningful author, or where the field is empty for that user, it renders blank.

The User Fields admin screen disappeared

The screen that defines fields only registers when the Dynamic Content engine is active (and when Tiger Blocks owns the data surface rather than deferring to Tiger Elements). Re-enable the module, or manage the fields in whichever plugin owns the surface; existing values still resolve on the front end.

Still stuck?

We’re here to help

Can’t find what you’re looking for, or hit something that looks like a bug? Reach the support team or ask the community.