Miscellaneous updates
- Improved security layer of our Checkout.
- Fixed an edge case issue of production activation from a WordPress Multisite.
- Skipped proration for ThemeForest and CodeCanyon migrated licenses that don’t have a payment with Freemius.
Welcome to the changelog section of Freemius, here you'll find our weekly technical update notes. You can subscribe to all posts via Newsletter or follow us on Twitter to stay updated.
Before now, there was no way to check which affiliates had their balances paid once an affiliate had been marked as ‘Paid Out’.
We’ve implemented a feature in the PAYOUTS tab of the Affiliate page that allows you to filter the list of affiliates by their balance status.
With the help of the filter, you can list affiliates whom you’ve set as ‘Paid Out’ and view information about when the balances were marked as such.
Please login to the Developer Dashboard (also available in the Beta Developer Dashboard) to start using this function. If you want to get started with the Freemius Affiliate Platform, you can find all the essential information here.
We are excited to announce that the first major update to the new Analytics Dashboard has landed on our Beta Developer Dashboard. This update brings fresh new Audience metrics that are highly optimized and customizable.
You can now access the following version charts on the Audience Analytics page.
Each of the charts can be customized with
You can also choose between Chart View or Table View from the same menu.
Under the same page, you also get another section to view where your products are being used.
The charts have the same features as before, except for ‘Version Aggregation’ and ‘Coloring’.
If you’ve been using Freemius for WordPress Plugins and Themes, then you know that we have a 30MB
upload limit for plugin and theme zip
files.
This has been working well for our partners since the zip
files are usually much smaller than the plugin files.
Since we started allowing selling static products (Widgets and Templates), we realized that the original size limit might not be big enough. Therefore, we’ve increased the upload limit for Static Products only to 60MB
. This means that you can now upload zip
s of static products up to 60MB
from the Developer Dashboard and also from the Beta Developer Dashboard.
If you have any questions or have any other requirements for Static Products, please get in touch with us through our support form.
Following a feature request from our partners, we’ve added country of origin flag icons next to every Payments and Subscriptions log in the Developer Dashboard. This feature is now part of the Beta Developer Dashboard only (with the brand new stats).
You can view these icons on the Payments or the Subscriptions pages.
When viewing Payments and Subscriptions from the Users or the Sites pages, the icons are also present.
As part of our automated marketing efforts, we send out a reminder email to customers with expiring trials. However, if the product was uninstalled or the website was deleted, the links in the marketing email – which pointed to the user’s WordPress Dashboard – became ghosted, resulting in broken upgrade links. This is how the email looks when linking to the WordPress Admin Dashboard.
We fixed this issue by proactively checking if the site is active. Only once and if we have confirmed this do we include the WordPress Dashboard links. If the site is inactive, we link to direct checkout (in the context of the license), making sure that the user can always update their package should they change their mind.
If Freemius finds the site to be inactive, the email will look like this:
Please note: If the user activated the trial and then requested a data erasure, we respect their decision. Since we do remove this type of data from our database, we do not send any emails. This behavior has not changed.
Previously, you could use the “Team” feature in Freemius if you’ve been selling your products with us (i.e, if your product is in the Revenue Plan). But we understand that many of our partners have a main ‘Free Product’ with one or many ‘Premium Add-ons’.
To simplify team management – provided that you’re selling at-least one Premium Add-on on a Revenue plan with us – you can now use the “Team” feature with the parent product too.
Go to the Developer Dashboard > Settings > Team to get started.
We’ve been stripping premium-only JavaScript code written in between <fs_premium_only>
and </fs_premium_only>
comment tags. For example:
(function($){ /* <fs_premium_only> */ // ... my premium only code ... /* </fs_premium_only> */ })(jQuery);
Also, as a recommendation for minifiers, we mentioned the following:
module.exports = { optimization: { minimizer: [ new UglifyJsPlugin({ uglifyOptions: { output: { comments: /\<\/?fs_premium_only\>/i, }, }, extractComments: true, }), ], }, };
But in some cases, if you had other preserving comments with the /*!
style, we didn’t properly take care of that. With this update, we will now be stripping all JS codes between /*! <fs_premium_only> */
and /!* </fs_premium_only> */
tags.
We now only use a secure httpOnly cookie for the Developer Dashboard. The change is transparent and you shouldn’t notice any changes. Please be aware of the following:
This change won’t revert if you’ve been using your Developer Secret Key to communicate with the Freemius API.
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:
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: