The WordPress.org freemium trap: how to ship a Pro plugin without getting suspended
The article discusses the challenges of creating a freemium WordPress plugin while adhering to WordPress.org guidelines. It emphasizes that plugins cannot include locked features, even if they are hidden or dormant. The author presents a solution using WordPress's hook system to separate free and Pro functionalities effectively.
- ▪WordPress.org prohibits plugins from containing locked features, which can lead to suspension.
- ▪The guidelines specify that no Pro code can be included in the free version of a plugin.
- ▪The author suggests using hooks to create a bridge between free and Pro versions, ensuring that Pro features are not present in the free build.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3903131) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } ROBERTO ANGUITA MARTIN Posted on May 19 The WordPress.org freemium trap: how to ship a Pro plugin without getting suspended #wordpress #php #webdev #opensource If you've ever thought about building a freemium WordPress plugin and distributing the free version through WordPress.org, there's a compliance rule that will catch you off guard. You cannot ship locked features. Not locked behind a license check. Not hidden behind an if (is_pro()).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
