LabelGrid Tools

1.6.5

• Important: fixes a 1.6.4 regression that made every Spotify pre-save fail. A check added in 1.6.4 did not recognise the reference the pre-save button sends, so the request was rejected before it reached LabelGrid and fans saw “We could not schedule your pre-save” or “We could not load your playlists”. Nothing was logged, so the failures were invisible to site owners. Download gates were not affected. If you are on 1.6.4, update.

1.6.4

• Important: download gates using “Upload artwork and description” could not be started by anyone. The gate required a linked release even when it had none, so every visitor saw “This download is not available right now” while the editor showed the gate as complete. Affects every previous version.
• Security: a shortcode attribute on the download-list block was placed into the page without escaping, so a user able to add shortcodes could inject markup that ran for visitors.
• Fix: a Spotify link that does not name what it points at — a short share link such as spotify.link/…, or an address ending at the artist or album segment — is now rejected when you save the action, instead of being accepted as a target that does nothing.
• Fix: after connecting Spotify, the connect button could be clicked again, which reopened a used authorisation link and showed an error. It now tells you the account is already connected.
• Fix: choosing two playlists in quick succession could hide a failure behind the other choice’s success message.
• Fix: pre-save and download-gate e-mail entries with the same numeric id no longer overwrite one another, so no collected address is lost.
• Fix: action links written with a different kind of line break are now read the same way everywhere, so the actions a visitor agrees to are exactly the ones performed.
• Improvement: the API token field is masked, with a Show button to reveal it — so it is not exposed in screenshots or screen sharing.
• Improvement: the pre-save and playlist requests now check the release belongs to this site before calling LabelGrid.
• Fix: a Spotify profile-follow action pointed at a username containing a dot, dash or underscore sent fans to the wrong account — the username was cut at the first punctuation. Affects the follow-a-profile action added in 1.6.0.
• Fix: a pre-save carrying an explicit save action for a different album no longer stops the release itself from being saved.

1.6.3

• Fix: automatic catalog sync is on by default. On some sites the setting had no stored value, which showed as disabled and quietly stopped syncing. Turning it off yourself still works and is respected.
• Important: uninstalling the plugin no longer deletes the e-mail addresses collected through your download gates. Those are your data and are now kept. Plugin settings, including the API key, are still removed.

1.6.2

• Fix: once the connection to LabelGrid was reported as inactive, the daily check stopped running, so a site could not recover on its own — even after the cause was gone. It kept showing the warning until someone re-saved the settings by hand. The check now runs whenever an API key is present, which is what the “we will check again automatically” message always promised. This affected every previous version, not only 1.6.1.

1.6.1

• Important: some older API keys are no longer accepted by LabelGrid. If your gates, pre-saves or catalog sync have stopped working, or the plugin says your key was rejected, create a new API key in your LabelGrid account and paste it into the plugin’s settings — nothing else needs changing, and your existing gates and pre-saves keep their configuration.
• Improvement: the “API disabled” warning now says which problem it is. A rejected key tells you to create a new one, a missing key says so, and a temporary connection failure says the check will retry instead of sending you to re-read a key that is fine. Previously every case showed the same “verify the API Token is correct”.
• Fix: after saving a working API key the warning at the top of the screen cleared only once the page was reloaded, so it contradicted the panel below it that already said the key was verified. It now updates as soon as the settings are saved.
• Improvement: the API token field is a single-line box, matching the shorter keys LabelGrid now issues.

1.6.0

• Important: Download gates and pre-saves now run entirely on the main LabelGrid API, using the same connection as the rest of the plugin. Existing gates and pre-save buttons keep working and need no changes — your fans will not notice the switch. If your API key is missing or expired the gate now tells you so directly in the plugin instead of failing quietly.
• Important: Download gate actions are Spotify-only in this release. SoundCloud and Twitter actions are paused while they are rebuilt. If a gate of yours used them, its SoundCloud and Twitter steps no longer run and no longer appear to fans — the gate keeps working with its Spotify actions.
• Important: Gates that asked fans to connect more than one service now ask only for the services still available. A gate set to “connect 2 accounts” while offering Spotify, SoundCloud and Twitter would otherwise have been impossible to complete once the other two were paused, because the fan could never connect a second account. This is adjusted automatically when the gate is shown — your saved setting is untouched, and it returns to normal when the other services come back. Please review any gate that previously required more than one account, and check its remaining Spotify actions still ask for what you want.
• Security: a fan’s gate identity is now a first-party cookie this plugin issues itself, replacing the PHP session it used to borrow. A session identifier planted in a visitor’s browser — from another subdomain, an insecure version of the same address, or a script injected into a theme — can no longer be used to take over the Spotify connection they are about to make. Note: a fan who is part-way through a gate at the moment you update will need to start that gate again; this affects only the few minutes around the update itself.
• Fix: gate requests that are refused now say so with a proper error instead of returning an empty successful response, so the modal can explain the problem rather than stalling.
• Important: a pre-save now always saves the release itself, in addition to any follow actions you configured. A pre-save set up with only follow actions previously could not be started at all.
• Security: gate and pre-save requests are now accepted only when they genuinely come from your own site. A crafted link could previously make a visitor’s browser perform a gate action without them choosing to.
• Security: when a visitor’s browser session cannot be started, the gate now refuses clearly instead of falling back to a shared identity. On hosting where PHP sessions are unavailable this previously merged all of a site’s visitors into one fan, so one visitor’s connection could unlock the download for everyone.
• Security: e-mail capture now only accepts submissions for a published gate or release.
• Fix: a pre-save with no optional follow actions could not be started at all. The release save is now always included, so a plain pre-save works as documented.
• Fix: unpublishing, trashing or drafting a gate now also closes download links already issued for it.
• Fix: fans returning to a pre-save they had already connected were shown a login button that could not work. They now continue straight to the playlist step.
• Fix: the pre-save confirmation is now shown only after the pre-save has actually been scheduled, and a failure offers a retry instead of a success message.
• Fix: gates that collect e-mail addresses no longer under-count first downloads.
• Fix: e-mail addresses and the address being saved could be recorded against two different visitor sessions and never join up.
• Fix: WordPress’s own privacy export and erase tools now reach gate e-mail entries. The erase tool previously would also have skipped roughly half of a large set.
• Improvement: the plugin no longer starts a PHP session on every page of your site, so full-page caching and themes that do not expect a session cookie are no longer affected. Sessions now start only when a fan actually uses a gate.
• Improvement: gate error messages now explain the actual problem — blocked cookies, or a request that could not be verified — instead of always suggesting a connection issue.
• New: Gates can ask fans to follow a Spotify profile, alongside the existing follow-artist, follow-playlist and save actions.
• Improvement: Gates can now carry far more Spotify actions than before, so larger action sets are accepted instead of being rejected. The gate editor shows how many you have used as you edit — note that each link counts as one action, so an action row holding three playlist links counts as three.
• Improvement: Follow targets are no longer restricted to artists in your own catalog, so you can promote collaborators and featured artists from a gate again.
• Improvement: Gates and pre-saves now report clearer errors when something is genuinely wrong — an expired key, a release that is not on your account, or a fan whose connection did not complete — instead of a generic failure.
• New: when a pre-save offers to add the release to one of your fan’s playlists, they can now search their playlists instead of scrolling the whole list. The list is also a little shorter, so the rest of the window is easier to read.
• Improvement: the actions a gate or pre-save will perform now link to the artist, playlist or profile in question, so a fan can see exactly what they are agreeing to before they connect.
• Improvement: choosing a playlist is confirmed in the window itself rather than in a browser pop-up, and a failure now says what went wrong and lets the fan pick another playlist.
• Improvement: while a gate or pre-save is working, the step a fan has just completed is replaced by a loading indicator, instead of leaving a question on screen they have already answered.
• Fix: a playlist with no cover art showed a broken image in the pre-save playlist list.