Bricks Builder Integration

The Bricks Builder Integration lets Bricks layouts display OrbitalWP task data with Bricks dynamic data. It is useful when you want task templates, task archives, or task-related designs in Bricks to show Orbital task fields without manually typing those values into the page.

How This Fits In OrbitalWP

This integration connects OrbitalWP task fields to Bricks dynamic data. Bricks controls access to the Bricks page or template. OrbitalWP controls whether the current viewer is allowed to see the task data that the dynamic tag is trying to render.

The integration is for displaying task data. It does not give Bricks visitors permission to edit tasks, change custom fields, manage assignees, or bypass OrbitalWP permissions.

Where To Find It

In the WordPress admin, open Orbital, then open Plugin Settings. On the settings page, choose the Integrations tab.

The Bricks setting is labeled Bricks Builder Dynamic Data inside the Third-Party Integrations section. After changing it, use Save Settings.

The same section shows whether Bricks is available with either Bricks Builder is active or Bricks Builder is not installed or not active.

Before You Start

  • Bricks Builder must be installed and active.
  • Bricks Builder Dynamic Data must be enabled in OrbitalWP Plugin Settings.
  • The person changing the integration setting needs access to Plugin Settings.
  • Task custom field tags should be used where Bricks is rendering an Orbital task as the current item.
  • Viewers must have OrbitalWP read access to a task before task field data is shown to them.

What You Can Do

  • Display configured OrbitalWP task fields in Bricks using the Orbital dynamic data group.
  • Display the Parent Post Title for a readable related or parent item.
  • Use Parent Post Link where Bricks expects a link value.
  • Use your configured custom field labels and option labels in Bricks output.

Basic Workflow

  1. Confirm Bricks Builder is active on the site.
  2. Go to Orbital, then Plugin Settings, then Integrations.
  3. Turn on Bricks Builder Dynamic Data and choose Save Settings.
  4. Review Orbital, then Custom Fields, and confirm the task fields, labels, and options you want to display.
  5. In Bricks, add dynamic data from the Orbital group where Bricks allows dynamic data.
  6. Preview the design as a user who should be able to read the task.

Important Controls And Settings

Bricks Builder Dynamic Data controls whether OrbitalWP registers its Bricks dynamic data integration. The integration still loads only when Bricks Builder is active.

Custom field definitions affect what appears in Bricks. Field labels, option labels, and field availability come from OrbitalWP Custom Fields.

The Orbital dynamic data group includes your configured task custom fields, plus Parent Post Title and Parent Post Link.

What Affects What You See

Task field tags only render task field values when the current Bricks item is an Orbital task. If the current item is not an Orbital task, task custom field tags return no output.

If the viewer can open the Bricks page but cannot read the current Orbital task, the task data is replaced with You do not have permission.

Task read access can come from role permissions, task ownership with the right permission, assignment, administrator access, or task-specific access.

Parent Post Title and Parent Post Link also depend on whether the related or parent item is readable. If there is no readable item, Parent Post Title shows Not Set and Parent Post Link returns no link.

Deeper Notes

OrbitalWP formats several field types before they appear in Bricks. Assignee fields show the user’s display name. Dropdown and radio fields show the saved option label when one exists. Checkbox fields can show Yes, No, or a comma-separated list of selected labels. Date fields use the site’s date format.

Fields with no saved value show Not Set. If a field definition is removed or the tag no longer matches an available field, the tag returns no output.

Changing a custom field label or option label in OrbitalWP can change what users see in Bricks output. Existing task values still depend on the data saved on each task.

Common Problems

I do not see Orbital tags in Bricks. Check that Bricks Builder is active, Bricks Builder Dynamic Data is enabled, and the settings were saved.

A task field is blank. The Bricks design may not be rendering an Orbital task as the current item, the field may not exist anymore, or the task may not have a saved value for that field.

The output says You do not have permission. The viewer can reach the Bricks page, but OrbitalWP is not allowing that viewer to read the task. Ask an administrator to check the user’s role permissions, assignment, and any task-specific access.

Parent Post Title says Not Set. The task may not have a readable related or parent item for the current viewer.

Parent Post Link does not output a link. The related or parent item may be missing, not readable by the viewer, or unavailable as a link.