Slider (Nestable) Arrows

Place custom previous and next controls outside a native Bricks Slider (Nestable). The arrows connect to a specific slider instance through its Script ID.

Setup and First Use


Before starting, enable the relevant element or feature family under Bricks → BricksUltimate → General Elements, save, and reopen the Bricks editor. Integrations also require their corresponding plugin to be active.

  1. Add and configure a native Slider (Nestable) with several slides.
  2. Find that slider's Script ID in the builder or its rendered data-script-id attribute. Use the instance ID, not a CSS class or the title of the slider.
  3. Add (BU)Slider arrows near the target slider and enter that value under Script ID.
  4. Customize the provided Previous button and Next button children and their icons.
  5. Style size, color, background, border, spacing, and hover states.
  6. Save and test both directions on the live page. Repeat with more than one slider if the template includes several.

Controls and Settings


ControlPurpose and usage
Script IDLooks up the native Bricks Splide instance. Enter the ID without a # prefix.
Nested buttonsThe supplied children identify previous and next actions. Preserve their functional arrow classes when changing the visual design.
Styles / HoverCustomize button geometry, icon size/color, border, background, margin, and padding.
PlacementThe wrapper can be placed outside the slider, but must be on the same rendered page as its target instance.

One Instance, One Target


A template element ID or a duplicated visual label is not necessarily a unique runtime Script ID. Check the actual rendered instance when sliders are repeated in loops or loaded in popups. A single fixed Script ID cannot identify every repeated slider.

Native Slider Rules Still Apply


The custom arrows do not create slides or change loop, rewind, per-page, speed, or breakpoint behavior. If there are fewer slides than the visible page size, a valid slider may have nowhere to move. Hide duplicate native arrows only after verifying the custom controls.

Practical Example


Place a testimonial slider on the left and the BU arrow controls beside its heading. Connect both buttons to the slider's Script ID, then test the first/last slide behavior with the slider's actual loop setting.

Troubleshooting


  • No movement: check the exact Script ID and whether the native instance initialized.
  • Wrong slider moves: correct the target ID and duplicated instances.
  • One button stops working: restore the expected previous/next child classes.
  • Popup-only failure: check initialization after AJAX insertion before changing arrow colors or placement.

Related Documentation