Signocore Slate has two kinds of visibility settings. The Block Visibility screen decides which Slate blocks your editors can add to a page. The Visibility Settings panel on a block decides who sees that block on the live site: you can hide it on desktop, tablet or mobile, and you can show a row only to logged-in or logged-out visitors or to certain user roles.
Choose which blocks editors can insert
If your site only uses a handful of Slate blocks, remove the rest from the block inserter so editors are not tempted to use them:
- Go to Signocore Slate → Block Visibility. The screen is available to administrators.
- Uncheck the blocks you want to remove. The blocks are grouped in categories, and the checkbox in a category's header row checks or unchecks the whole category. The checkbox at the top of the table does the same for every block.
- Click Save changes.
The notice at the top of the screen confirms how many blocks are enabled and disabled. To bring every block back, click Enable all and confirm.
| Category | Blocks on the screen |
|---|---|
| Layout & Structure | Row Layout, Section, Spacer / Divider, Split Content |
| Content | Text (Adv), Buttons (Adv), Icon, Icon List, Info Box, Table of Contents |
| Media | Image (Adv), Gallery (Adv), Image Overlay, Video Popup |
| Interactive | Accordion, Tabs, Advanced Slider, Countdown, Count Up, Progress Bar |
| Forms | Form, Form (Adv) |
| Posts & Queries | Posts, Post Grid/Carousel, Testimonials |
| Dynamic | User Info |
| Site Structure | Site Identity, Navigation (Adv), Header (Adv) |
The Slug column shows each block's name, such as slate/rowlayout. The labels match the block titles in the inserter.
This setting only changes the block editor. Pages that already use a disabled block keep showing it to visitors.
Important: Only disable blocks that no published content uses. When a page contains a block you disabled, the editor can no longer edit that block and shows it as unsupported. Enable the block again to edit it.
Hide a block on desktop, tablet or mobile
Four blocks have device settings: Row Layout, Section, Spacer / Divider and Countdown.
- Select the block in the editor.
- In the block settings sidebar, open the Advanced tab.
- Open the Visibility Settings panel.
- Turn on Hide on Desktop, Hide on Tablet or Hide on Mobile, and update the page.
The settings take effect on the site, based on the width of the browser window:
| Setting | Hidden when the window is |
|---|---|
| Hide on Desktop | 1025 px wide or wider |
| Hide on Tablet | 768 to 1024 px wide |
| Hide on Mobile | 767 px wide or narrower |
To show different content on phones and computers, build two rows: one with Hide on Mobile and one with Hide on Desktop and Hide on Tablet.
Note: A block hidden by device is still part of the page. Visitors download it, and anyone who views the page source can read it. Do not use device settings to hide content that some visitors must not see.
Show a row only to some visitors
Row Layout blocks can also depend on who is visiting. The settings are under User Visibility Settings in the same Visibility Settings panel on the Advanced tab.
| Setting | What it does |
|---|---|
| Hide from Logged in Users | Hides the row from every logged-in user. When it is on, two more fields appear |
| Optional: Hide from Specific User Roles | Hides the row only from logged-in users with one of these roles. Other logged-in users see it |
| Optional: Show Only to Specific User Roles | Shows the row only to logged-in users with one of these roles |
| Hide from Logged out Users | Hides the row from visitors who are not logged in |
The role fields list your site's user roles, and you can pick more than one. Logged-out visitors are never affected by the role fields, only by Hide from Logged out Users.
Some common combinations:
- Only for logged-out visitors, such as a sign-up call to action: turn on Hide from Logged in Users and leave both role fields empty.
- Only for logged-in users, such as a members' notice: turn on Hide from Logged out Users.
- Only for editors and administrators: turn on Hide from Logged in Users, choose Editor and Administrator under Optional: Show Only to Specific User Roles, and turn on Hide from Logged out Users.
- For everyone except subscribers: turn on Hide from Logged in Users and choose Subscriber under Optional: Hide from Specific User Roles.
Restrict Content Pro memberships
When Restrict Content Pro is active, the panel also has Restrict based on Membership. Turn it on to show the row only to logged-in members whose access level reaches Minimum Access Level. To limit it further, choose one or more levels under Specific Memberships. Visitors who are not logged in never see a row that uses this setting.
There are no date or schedule conditions. To show a row only for a period of time, publish and unpublish the content yourself.
How hidden blocks are handled
The two kinds of settings work in different ways, and that matters for privacy and caching:
| Settings | How the block is hidden |
|---|---|
| Hide on Desktop, Hide on Tablet, Hide on Mobile | The block is in the page for every visitor, and CSS hides it at the chosen window widths |
| User Visibility Settings and Restrict based on Membership | The server leaves the row out of the page for visitors who should not see it. The row, and everything inside it, never reaches their browser |
Block visibility and page caching
Device settings work with any page cache or CDN, because every visitor gets the same HTML and the browser decides what to show.
Login, role and membership settings are decided when WordPress builds the page. A page cache that serves a stored copy of a page to everyone would show the same version to all visitors, whoever it was built for. Most caching plugins and hosts already skip the cache for logged-in users, which keeps these settings working:
- A row for logged-out visitors only is safe to cache, since only logged-out visitors get cached pages.
- A row for logged-in users, certain roles or members needs a cache that bypasses logged-in users. Check your cache or CDN settings, especially rules that cache every page regardless of cookies.
After you change a visibility setting on a cached page, clear the page cache so visitors get the new version.