Display

Display → Positions. Pick as many as suit you.

• Below the content is where most shares happen. Someone who finished reading is the person most likely to pass it on.
• Above the content catches people who already know they want to share.
• Floating beside the content stays visible while reading. It hides itself on narrow windows, where there is no room beside the text, and steps aside while anything wide passes underneath it (a product gallery or a full-width image, say), coming back once it has gone. While it shows, it says how far in from the edge it reaches, as the CSS custom properties --trasl-stack-ms-trss and --trasl-stack-me-trss (the middle of the start and end sides), and Lucky Wheel's launcher, when it sits in the middle of the same side, steps in past it instead of covering its buttons.
• A bar pinned to the bottom is for phones, where the floating rail cannot fit. It can be shown on every screen size if you prefer. The page gets a little extra room at the very bottom, the height of the bar, so the last lines of the page (footer links, a cookie banner's buttons) can still be scrolled clear of it. The bar stays light whatever the visitor's phone is set to. Distance from the bottom (px) raises it above a theme's sticky footer or a chat button. While it is showing, the bar also publishes its height as the CSS custom property --trasl-bottom-inset, and the floating buttons of our other plugins, such as Lucky Wheel's launcher and the Dark Mode switch, move up by that much instead of covering its first and last buttons. Any other widget can do the same with bottom: calc(20px + var(--trasl-bottom-inset, 0px)).
• Product summary (below Add to cart) appears when WooCommerce is active. Product pages then show the buttons in the product summary, under Add to cart, instead of inside the Description tab. Tick Products under Display on as well. On product pages it takes the place of the buttons above and below the content, so a product never shows two sets.

Floating rail networks and Pinned bar networks, beside each one's own settings, decide which buttons the rail and the bar show:

• The same as the Networks screen is the default: the networks ticked there, in that order. Every site starts here, and one updating from an earlier version draws exactly what it drew before.
• Choose for this position opens the Networks screen's own tick list and arrows, for that position alone. It starts from what the position shows now, so it is a list to adjust rather than one to build, and the arrows work from the keyboard as they do on the Networks screen.

A phone has room for three or four buttons, so the pinned bar's list has Suggested for phones: WhatsApp, Copy link, More. One press ticks those three, puts them first in that order and unticks the rest. More opens the phone's own share sheet, which lists every app the reader has, so the three between them reach almost anywhere.

Saved with nothing ticked, a position goes back to The same as the Networks screen, because a bar with no buttons would be no bar, and the message after saving says so. Pinterest in a list of its own still leaves itself out of a page with nothing to pin, and a press is counted as any other, against the post and the network. The block, the shortcode and the template tag use the Networks screen's list or the one you give them, never the rail's or the bar's. A rail or a bar with a list of its own still shows when the Networks screen has nothing ticked.

On an archive — a category, a tag, the blog page — the floating rail and the pinned bar share the archive itself. The buttons above or below each post in the list share that post.

The buttons above and below the content go round each post once. Inside a post, a content block that another plugin's shortcode draws where it stands, such as Custom Post Widget's [content_block], gets none of its own. Nor does any inserted piece that visitors cannot open at an address of its own, and nor does an excerpt. A post that a Query Loop block lists with its whole text keeps its own buttons for its own address, as on an archive. A whole page that another plugin inserts into a post can keep its own buttons in the same way, sharing that page, when the plugin draws it as that page. To leave them off there, tick Hide share buttons on this post on the inserted page, which hides them on that page's own address too.

Printing a page leaves the buttons out, including when a reader uses the Print button.

Display on decides which content carries them. Tick the kinds of content — the list is built from your own site, so a post type you have added is already in it — and, if you want them there, the archives too.

There is nothing here about the cart, the checkout or the front page, and that is deliberate. Buttons attach to a piece of content; there is no article on a checkout to share, so a rule about one would be a rule that does nothing. If your front page is a static page, ticking Pages covers it, or name it under Specific pages.

Sharing an archive link is usually a mistake: it goes stale as soon as you publish again. That is why nothing under Archives is ticked to begin with.

Specific pages covers a single page that does not fit the pattern. Exclude always wins, and takes a page, a post, a product or a whole category — choosing a category covers everything filed under it. Everything is found by typing its name; there are no IDs to look up.

Common exclusions ticks the cart, the checkout and the account pages. Those three are worth a tick of their own because they are pages: tick Pages above and share buttons land on all three, which is almost never what anyone means. There is nothing to tick on the other side of the screen, because buttons attach to a piece of content and there is no article on a checkout to share.

Excluded addresses takes one path per line, with standing for anything — the same shape you already know from redirects. /account/ keeps it off every page under /account/. It is matched against the path only, so it works whatever your domain is, and it is not a regular expression: a mistyped one is a rule that matches nothing rather than a rule that matches the site.

You can paste an address straight from the browser, letters from other alphabets included. Earlier versions saved such an address as // (the front page), //* (every page) or /, or with letters missing; a line saved like that keeps doing what it did, so if the box holds one you did not mean, delete it and paste the address again.

Audience#

Devices limits it to desktop, tablet or mobile. Leave all three clear for every size. It is decided by the width of the window rather than by guessing from the browser, so a narrow desktop window counts as narrow and the answer survives page caching.

Login status limits it to people who are signed in or signed out. Tick Signed in and User roles appears underneath, narrowing it further — the role list is your own site's. A role is something only a signed-in visitor has, so the question is not asked until it can be answered.

When#

Leave it on Always and it runs until you say otherwise. Between two dates opens a window: a start, an end, particular days of the week, and a time of day. Everything is worked out against your site's clock, the one under Settings → General.

One caveat worth knowing: a page cache can outlive the moment a schedule ends, because the cached copy was made while the schedule was still running. If the timing has to be exact, keep those pages out of your cache.

Once you have ticked something, the exceptions box only offers what is inside those ticks. There is no sense excluding a product from buttons that only appear on posts.