Changelog

When a user leaves a review – either via email or the form – we now make it clear to them that the review will be publicly visible.

Here’s how it looks in the review email:

And here’s how looks in the review form:

After the recent update of the third-party cookie policy in Safari and Firefox, the PayPal express checkout momentarily stopped working in WordPress Dashboard in these browsers. We promptly pushed a fix to remedy this.

Additionally, we also worked on various performance and internal enhancements.

Added protection from mistakenly overriding existing releases by prompting the developer with a confirmation dialogue box after uploading a version that already exists.

If you’ve been using Freemius API for automated deployments, and if you want to override a release, you’ll need to send a PUT request mentioning the version number explicitly. Also, please note that we validate the version number accordingly to semver v2 when version is expressly mentioned.

WordPress 5.8 introduced a new Update URI header/ This should prevent WordPress from mistakenly downloading an update from WordPress.org when the plugin is not originated from wp.org, and therefore end up overriding the plugin with a different one.

Our WordPress SDK prevents such a situation from happening. Still, if the plugin is deactivated (i.e. the SDK is not executed as part of the updates logic), this problem can occur.

I’m happy to share that Freemius’s deployment mechanism now officially supports the Update URI header and works as follows:

1. Add (or override) the Update URI header for paid versions with https://api.freemius.com to prevent the problem.
2. If the Update URI header was already added before deployment to Freemius, it will be stripped from the free version when pointing to freemius.com. This is because we don’t support updates of free products, and also because we want to make sure that wp.org updates will work as expected.
3. For now, if there’s a custom Update URI header that is pointing elsewhere (not to freemius.com) keep it as is in the free plugin version, assuming you had a good reason to custom set it.

You can now search affiliates based on name, email, affiliate ID, or user ID:

We now support adding custom terms and conditions that will be integrated into the EULA. This feature is available only to the Multi Store Developer Dashboard.

To get started please go to your Store -> Settings. There you’ll find the new settings under Terms & Conditions textbox.

Once you’ve entered a valid URL and saved it, you will find the links show up on your product’s EULA pages.