FREE block. Displays a single meta value from any post, or from any organisation/user, anywhere on your site, including inside a Fundations grid. Block ID: get-fund/meta-field.

Why use this
Fundations and WordPress store a lot of information in post meta and user meta that no core block exposes: an organisation’s website, a custom field on a fundraising page, a logo saved against a user account. The Meta Field block reads any of those values by key and renders it, so you can surface custom data on a page or in a Query Loop card without writing a shortcode or a template part.
It reads from more than just Fundations posts. Point it at any public post type’s meta, or switch its source to the post author or the current logged-in user to show organisation and profile data.
What it does
The block resolves a value in three steps: it picks a source (a post, or a user), reads the meta key you chose, and renders it in the format you selected. When editing, a searchable picker lists the meta keys that already exist for the chosen source, and you can also type a brand-new key by hand.
Sources
| Source | Reads from | Notes |
|---|---|---|
| Post meta | A post’s postmeta | Defaults to the current post (single template or Query Loop item). Set a Post ID to pin it to one specific post. |
| User / organisation | A user’s usermeta | Choose Post author (organisation) to read the author of the current fundation, or Current logged-in user. Set a User ID to pin it to one specific user. |
Curated organisation and user keys
When the source is User / organisation, the picker leads with a curated list so these keys are selectable even before any user has filled them in:
| Label | Key |
|---|---|
| Organisation: Name | get_fund_organisation_title |
| Organisation: Description | get_fund_organisation_description |
| Organisation: Color | get_fund_organisation_color |
| Organisation: Logo URL | get_fund_custom_logo |
| Organisation: Logo (attachment ID) | get_fund_custom_logo_id |
| Organisation: Page URL | get_fund_org_url |
| User: Website URL | user_url |
| User: Display name | display_name |
get_fund_org_url is a synthetic key. It is not stored anywhere; it resolves at render time to the author’s organisation page. With Fundations Pro active it points to that organisation’s single page under /organisations/; without Pro it falls back to the author’s posts URL. It is filtered through get_fund_meta_field_user_link, so you can override the target in code.
Formats
| Format | Renders as |
|---|---|
| Text | The raw value, escaped, wrapped in your chosen tag |
| Number | The value formatted with a fixed number of decimals |
| Date | The value passed through a PHP date format |
| Link (URL) | An anchor whose href is the value; the visible text is your Link text (or the URL itself) |
| Image | An whose src is the value; accepts a URL or an attachment ID, with max width, max height, corner radius, and alt text |
How to use it
- Add the Meta Field block from the Fundations category.
- Choose a Source: Post meta, or User / organisation.
- Search for the meta key in the picker, or type a custom key. For the User source, pick one of the curated organisation keys or type your own.
- Choose a Format (Text, Number, Date, Link, or Image).
- Set format-specific options: decimals for numbers, a date format string for dates, link text for links, or max width/height and corner radius for images.
- Optionally add prefix or suffix text, fallback text, an HTML tag, alignment, and typography, or toggle Link to post to wrap the whole output in a link to its post.
Settings and options
| Attribute | Type | Default | Description |
|---|---|---|---|
source | string | post | post (post meta) or user (user / organisation) |
userSource | string | author | For the user source: author (post author) or current (logged-in user) |
userId | number | 0 | Pin the user source to a specific user ID (0 = resolve from source) |
postId | number | 0 | Pin the post source to a specific post ID (0 = current post) |
metaKey | string | (empty) | The meta key to read |
format | string | text | text, number, date, url, or image |
decimals | number | 0 | Decimal places for the number format |
dateFormat | string | (empty) | PHP date format for the date format (blank = site default) |
linkText | string | (empty) | Visible text for the link format (blank = show the URL) |
openInNewTab | boolean | false | Add target="_blank" to link/image links |
imageMaxWidth | number | 0 | Max image width in pixels (0 = no limit) |
imageMaxHeight | number | 0 | Max image height in pixels (0 = no limit) |
imageBorderRadius | number | 0 | Image corner rounding in pixels |
imageAlt | string | (empty) | Image alt text |
tagName | string | span | Wrapping element for text/number/date output |
alignment | string | left | left, center, or right |
prefixText | string | (empty) | Plain text before the value |
suffixText | string | (empty) | Plain text after the value |
fallbackText | string | (empty) | Shown when the value is empty (if the block is not hidden) |
hideIfEmpty | boolean | true | Render nothing at all when the value is empty and no fallback is set |
linkToPost | boolean | false | Wrap the output in a link to the resolved post |
fontSize | number | 0 | Font size in pixels (0 = inherit) |
fontColor | string | (empty) | Text color |
fontWeight | number | 0 | Font weight 100–900 (0 = inherit) |
What you can and cannot do
- You can read meta from any post type, not just Fundations posts, and from the post author or the current user.
- You can place the block inside a Query Loop so each card shows its own post’s (or author’s) value.
- You can render the same key as text, a number, a currency-style figure, a date, a link, or an image.
- Protected meta keys (those a user is not allowed to read) are not exposed by the picker or the block for the user source.
- The block does not write meta; it only displays it.
- The searchable key picker lists keys that already exist for the source. A key with no stored value anywhere still works if you type it by hand, it just will not appear in the list until something saves it.
Query Loop support
The Meta Field block declares Query Loop context, so inside a Query Loop or Greenshift query grid each rendered card resolves the value against its own post (and, for the user source, against that post’s author). This is how the organisation archive shows each organisation’s logo, description, and page link from one block placed once in the template.
Developer reference
| Symbol | Type | Notes |
|---|---|---|
get-fund/meta-field | block | Server-rendered, FREE, Query Loop aware. |
get_fund_org_url | synthetic key | Resolves to the author’s organisation page (Pro) or author posts URL (free). |
get_fund_meta_field_user_link | filter | apply_filters( 'get_fund_meta_field_user_link', $url, $user_id, $attributes ). Override the URL the get_fund_org_url key and the user-source Link to post produce. Fundations Pro uses this to point at the /organisations/ page. |
GET /wp-json/get-fund/v1/meta-keys | REST route | Feeds the editor’s key picker. Requires the edit_posts capability. Accepts post_type, or ?source=user for user meta. |
The render logic lives in render_meta_field_block() in includes/class-get-fund-block-editor.php, with format_meta_value(), build_meta_url_html(), and build_meta_image_html() handling each format.