Skip to content
Traslatability traslatability

Social Share Buttons Changelog

Share buttons that load fast, look like your site, and count what people actually share.

Social Share Buttons

Release history

Every version, what changed, and when it shipped.

  1. 1.4.10
    • Saving now says what was saved. Every screen answered with the same word — “Saved.” — which tells you the one thing you already knew, that you pressed the button. Each screen names what it kept.
    • The confirmation message has no close button and more room at both ends: it leaves on its own after four seconds, and clicking anywhere on it dismisses it.
  2. 1.4.9
    • Confirmation and error messages are easier to see: rounder, and coloured by what they are saying — green for saved, red for something rejected, amber for something to look at — each with a mark of its own.
    • A licence message now looks like one. Activating a key answered in an unmarked grey box, whatever it said; it carries the right colour and a mark like every other message on the screen.
    • A licence key that could not be a key is refused on the spot, without a request to the licence server and without reloading the screen. An empty box used to mean a wait, and on an offline site it meant being told the licence server could not be reached.
    • A key pasted out of an email in lower case, or with the dashes lost, is put right rather than reported as wrong.
  3. 1.4.8
    • Confirmation messages line up properly and sit on rounder corners: they were top-aligned with the text nudged down two pixels to meet the icon, which on a one-line message read as a misalignment because it was one.
  4. 1.4.7
    • Confirmations are easier to see. The message after a save is bordered in the colour of what it is telling you, sized to the words rather than stretched to a fixed card, and it now says what was saved rather than just "Saved".
    • It stays for four seconds instead of three — long enough to read a sentence — and hovering it holds it open.
  5. 1.4.6
    • Tab changes are instant. The plugin's other screens are fetched quietly in the background while you read the first one, so by the time you click a tab there is nothing left to wait for — tens of milliseconds instead of a second and a half.
    • One at a time, never in parallel, started only once the screen you are on is ready and the browser says it is idle, stopped the moment you navigate, and skipped entirely on a metered connection.
  6. 1.4.5
    • An admin that never reloads. Every screen arrives without a page load and every save happens where you are standing — and the screen you are heading for is usually already fetched, because moving a pointer to a menu item takes long enough to fetch it.
    • Saved, and told so where you are looking. A save answers in a small message in the top-right corner that clears itself after a few seconds, instead of reloading the page and putting a notice above the header.
    • It is an enhancement, not a dependency: if a fetch fails or scripting is off, links navigate and forms submit exactly as they always did, and the server side is unchanged.
  7. 1.4.4
    • Notices redesigned: a quiet bordered card at 14px with the tone carried by a tinted icon, rather than a block of colour in coloured type.
  8. 1.4.3
    • Every notice this plugin prints now looks the same: a white box with a coloured rule down its edge — orange for something to do, red for something wrong, green for something that worked. WordPress tinted a warning cream and an error pink and gave each one its own border colour, so a few notices in a row read as a few different kinds of box.
    • The message on the licence screen after activating or deactivating a key now stays where it is printed, rather than jumping down the page a second after the screen has loaded.
  9. 1.4.2
    • Fixed: a notice from this plugin no longer jumps after the page has loaded. WordPress lifts any notice out of the page once it is ready and drops it under the page heading, so the screen settled and then everything below moved by the height of a notice — and painted once in WordPress's colours before ours arrived. Ours stay where they are put, styled from the first paint.
  10. 1.4.1
    • Tooltips are ours rather than the browser's. They appear the moment you hover or focus instead of after a second, they are styled like the rest of the screen, and somebody using a keyboard gets them too. On this plugin that is the copy button beside a shortcode.
  11. 1.4.0
    • Fixed: "Never on these" threw away every exception but the first. The field posts its choices as one line, and the code that read it back only knew how to split that line in one of the two shapes it arrives in — so choosing two pages to keep it off kept it off neither. It has been that way since the display settings were rebuilt. One choice always worked, which is why it went unnoticed.
    • Fixed: six settings on the Display screen were thrown away every time you saved. Quick exclude, Addresses to keep it off, Screen sizes, Visitors, Only these roles and the whole schedule all drew their controls, took your answer and discarded it, because the screen's list of the settings it may write left them out. They work.
    • Fixed: Screen sizes did nothing even once it saved. The rule was worked out and never reached the buttons, so a rail set to mobile only stayed on desktop too.
    • Quick exclude offers the basket, the checkout and the account pages. Those three are ordinary WordPress pages, so ticking Pages reached all three with no tidy way to say no. There is still nothing to tick on the show side: buttons attach to a piece of content, and there is no article on a checkout to share.
    • Fixed: a place could be chosen and ruled out at the same time when the choice came from a preset. "The front page only" left the front page tickable under Quick exclude, which is a rule that cancels itself. The preset now greys out the places it chose, and the setting is refused on save even if the form says otherwise.
    • Fixed: a place ticked under Quick exclude could not be unticked. It was written into the field below it as well, and that field posted it straight back on the next save. Named places belong to the ticks now, and individual pages and categories to the field, so nothing is written down twice.
    • Only these roles appears once Signed in is ticked, rather than sitting there inviting a rule that can never match: a role is something only a signed-in visitor has.
  12. 1.3.2
    • Fixed: the buttons could be switched off with no way to switch them back on. The Display screen saved an on/off setting that no control in the admin ever drew, so saving that screen turned the buttons off for good. It has been that way since the plugin shipped. There is a switch at the top of Display now.
    • Fixed: the same fault switched off "ask which Mastodon instance" on every save, which quietly broke sharing to Mastodon. It now has a control of its own, on the buttons screen where Mastodon lives.
    • The display settings no longer offer rules that could never apply. Buttons attach to a piece of content, so there is nothing about the basket, the checkout or the front page — only the kinds of content and archives that can actually carry them.
    • The menu says Display, like every other plugin's.
  13. 1.3.1
    • The display settings are laid out in two columns: what it shows on and who sees it on the left, what it is kept off and when on the right, so the pair can be read against each other.
    • Fixed: a place could be ticked both as somewhere to show and somewhere to exclude, which is a rule that cancels itself. Ticking one now greys out the other, and the setting is refused on save even if the form says otherwise.
  14. 1.3.0
    • The display settings are one structure now, the same in every plugin: a preset for the common answers, tick lists for the places, kinds of content and archives, and searchable fields for the exceptions.
    • Quick exclude ticks the places most often left out. They and the search field are one list, not two settings that can disagree.
    • Addresses to keep it off takes paths with a * wildcard, so a whole section can be excluded without naming every page in it.
    • Who sees it limits by screen size, by whether a visitor is signed in, and by role — the role list is your own site's.
    • When gives it a window: dates, days of the week and hours, worked out against your site's clock.
    • Every list is built from your own site. A site without WooCommerce is never offered a rule about a checkout it does not have.
    • Your existing settings are carried across; nothing needs re-doing.
    • The documentation and knowledge base cover all of it.
  15. 1.2.0
    • "But never on these" now takes a page, a post, a product or a whole category, picked by name — a category covers its archive and everything filed under it. Which kinds of content get buttons is unchanged.
    • Your existing exclusions are carried across.
    • The knowledge base has been updated to match.
  16. 1.1.0
    • Where a thing shows is now chosen by name, not by ID. Pick pages, posts, products, categories, tags or a named place — the basket, the checkout, the shop, the front page, search results — and exclude any of them. Which post types get buttons is unchanged.
    • The same vocabulary is used by every Traslatability plugin that asks the question, so you learn it once.
    • Your existing settings are carried across; nothing needs re-doing.
    • "Never on these posts" took a list of post IDs; it now takes anything, including a whole category.
  17. 1.0.12
    • The shortcode chip in a list is drawn as one object again — it had become a line of text with a copy icon adrift after it — and copying now turns it the same soft green as everything else that has gone well, rather than outlining it in dark green.
  18. 1.0.11
    • The shortcode boxes are drawn properly now. WordPress paints every piece of inline code with its own grey background, which put a second box inside ours; a long shortcode was also cut off at the edge rather than wrapping, so you could not read the end of what you were about to copy.
  19. 1.0.10
    • Every dropdown now draws its own arrow. A native select is nearly invisible against our surface on macOS and sometimes has no arrow at all elsewhere, so a dropdown could read as a text box — and a text box invites typing rather than clicking.
    • A shortcode is copied by clicking it. It used to be text to select by hand, which is a small tax on the one thing you came to the screen for.
  20. 1.0.9
    • The “delete everything on uninstall” setting has a control. It was saved and read by the uninstaller, but no screen ever drew it — so the one thing it exists to allow could not be switched on, and the knowledge base sent people looking for a toggle that was not there.
    • WordPress's own plugin details window now says what the plugin is, not only what changed in the last version.
  21. 1.0.8
    • Picking a button style changes the preview. It always drew Solid however many of the six you clicked: the preview read the style from the first radio in the group rather than the checked one, which is why every other control on the screen worked and only this one looked broken.
  22. 1.0.7
    • Settings screens lay out in two columns again. The rule that puts panels side by side was in two other plugins and never in the shared stylesheet, so a screen written for two columns rendered as one long one.
  23. 1.0.6
    • A colour field is one row again — a swatch and its value. Every one of them was showing its hex box and a Clear button at all times, because a rule meant for the opened picker was overriding the one that keeps them shut, so a screen of colours read as twice as many controls as it had.
    • Each swatch shows its own colour value instead of all of them saying “Select Color”.
  24. 1.0.5
    • The licence screen and its notices are in Spanish and French, as the rest of the plugin already was — 58 strings had never made it into the catalogue.
    • The dashboard figures are translated too.
  25. 1.0.4
    • The icons in the section bar are 17px, matching the other plugins — they were two pixels smaller here, which made the whole bar read as a different size.
  26. 1.0.3
    • The colour picker is laid out properly once opened — the hex box and Clear sat hard against the swatch button and each other with no spacing at all.
    • The plugin mark in the section bar is versioned by file time, so a redrawn icon actually reaches you instead of the browser serving the one it cached first.
  27. 1.0.2
    • The colour field is a proper colour picker with a palette, as it is in the other plugins, instead of a box expecting a hex code.
    • The licence chip has gone from the section bar, matching the other four plugins — Licence is still in the bar beside it.
    • The dashboard figures are laid out as cards rather than a run of unstyled text.
  28. 1.0.1
    • The plugin icon has lost the decorative braces that used to sit either side of the mark — on this one they collided with the share arms outright.
    • Fixed: setting up a site added to a multisite network after activation could fail outside the admin, where the function used to check network activation is not loaded.
  29. 1.0.0
    • First release.

Get Social Share Buttons

One licence, every feature. Updates and support included.

See pricing