Tabs are normally clicked one at a time, which works when there are three of them and less well when the content is meant to be walked through in order.
Connecting a Carousel Remote adds Next and Previous controls to a Tabs Tours block, so the visitor can step through it like a guided tour.
For every External Form Styler setting in one place, see the main Carousel Remote guide.
Before You Start
- Edition: Pro — the Carousel Remote block needs Nexter Blocks Pro.
- Block to enable: Carousel Remote, switched on under Nexter > Blocks in your WordPress dashboard.
- A Tabs Tours block already on the page with at least two tabs.
Video Tutorial
Steps
- Add your Tabs Tours block and set up its tabs.
- Set a Carousel ID on the Tabs Tours block — for example
Id1.
- Add the Carousel Remote block where you want the controls.
- Set the remote’s Carousel ID to the same value, and set Remote Type to Tab.
- Publish and step through the tabs on the real page.
Both blocks need the same Carousel ID. That one field is the whole connection. Measured: with matching IDs the controls drive the other block; with different IDs nothing happens at all and no error is shown.
How It Behaves
The Carousel Remote is a set of controls — arrows, dots or a counter — that you place somewhere else on the page and connect to a carousel, a tab block or a switcher. It holds no content of its own; it only drives another block.
- Measured on a two-tab block: Next moved from tab 1 to tab 2, Next again returned to tab 1, and Prev moved to tab 2.
- It wraps around. Measured: going past the last tab returns to the first rather than stopping.
- Remote Type must be set to Tab. This pairing uses a different mechanism from a carousel — leaving the type on Carousel will not drive the tabs.
- Both blocks need the same Carousel ID. That one field is the whole connection. Measured: with matching IDs the controls drive the other block; with different IDs nothing happens at all and no error is shown.
- The tabs still work normally — the visitor can click a tab directly as well as use the remote.
Limitations
- A mismatched ID does nothing — measured, the tab never changed. Unlike the carousel pairing, this one also writes a JavaScript error to the browser console on every click, which is a useful way to confirm the IDs are wrong.
- An empty Carousel ID makes the remote inert. Measured: with the field blank the block writes no connection information at all, yet the arrows still render and still look clickable. They simply do nothing.
- Next and Previous only. The remote steps through tabs in order; it cannot jump to a named tab.
- The connection runs on the published page only, not in the editor.
- Measured with Nexter Blocks Pro deactivated: the block renders nothing at all — no controls, no placeholder.
Troubleshooting
The Next and Previous controls do nothing
First check Remote Type is set to Tab, then check the Carousel ID matches on both blocks exactly.
How do I confirm the IDs are wrong?
Open the browser console and click the control. Measured with mismatched IDs on a tab pairing: every click logs a TypeError. With matching IDs the console stays clean.
It jumps back to the first tab
That is the wrap-around, measured: stepping past the last tab returns to the first.
Nothing happens in the editor
Expected — publish the page and test there.
