Features Comparison Compare Freemius to EDD, WooCommerce, and CodeCanyon/ThemeForest.
Software Licensing Control what features to enable based on the plan and number of site activations.
Subscriptions Build a sustainable recurring revenue stream.
Automatic Updates Manage and deploy versions all in one place.
Buy Button Easily embed a buy button on your website.
Analytics & Usage Tracking Get actionable insights on user behavior.
User Dashboard A fully-featured members area for customers.
Affiliate Platform Manage affiliates. Track clicks, visits & referrals.
Cart Abandonment Recovery Recover lost sales with automated emails.
EU VAT & UK VAT Offload VAT handling to Freemius.
US Sales Tax Pass sales tax liability to Freemius.
Documentation Start by integrating your WordPress plugin or theme in 5 mins to get all our platform features.
Getting Started Getting Started 🚀Integration & ConfigTesting & DebuggingVersion DeploymentLicensing APIBuy Button JS API
Popular Topics Getting PaidSelling Add-OnsBundles & MembershipsOffering Free TrialsUser's Dashboard
WordPress SDK
PHP SDK
System Status
Changelog
PricingCustomers BlogVideosPodcast MarketingCustomer SupportInterviewsProduct FAQ

Changelog / Do NOT change SDK v2.10.1 directory to vendor

Do NOT change SDK v2.10.1 directory to vendor

We recently released WordPress SDK v2.10.1, which includes a recommendation to move the SDK from the root directory to the vendor directory. However, we strongly advise against changing the SDK directory at this time.

You can update the SDK to the latest version to enjoy the new features. However, if you also change its location, it will likely result in an error during the update process for your paid products. So, if you haven’t been using composer, please don’t migrate to it now or if you have the SDK in the root directory, do not move it to the vendor directory.

Regarding the error

The error is harmless and will not cause functional issues, but it may create a poor user experience for your customers. To avoid this, we ask that you refrain from changing the SDK location.

We are aware of the issue and are working on a solution. We will get back to you with more details after the holidays.

If you’ve already deployed a version where you’ve changed the SDK location

We recommend the following steps:

  • Unrelease the version from the Developer Dashboard.
  • Wait for an update from our end.

If you must release another version:

  • If most of your customers have already updated: Keep the new SDK location.
  • If only a small percentage of your customers have updated: Revert to the old SDK location.

In both cases, the error message may appear for some of your users.

We sincerely apologize for the inconvenience and appreciate your patience and understanding as we work on a solution. To give you an estimate, we have already built a fix and are in the process of refining and testing it to ensure it covers all use cases.

If you have any questions, please contact our support team.