Transparency Report #19 – Our Most Popular Free Theme (Zerif Lite) Suspended From WordPress.org

Welcome to the 19th edition of our monthly transparency report (for August 2016). In this series, I cover various aspects of running a WordPress business, discuss our own strategies and plans, as well as struggles and hardships. In short, this is where you can find out what’s going on behind the curtains at ThemeIsle and CodeinWP. Click here to see the previous reports.

Why you should care about the WordPress.org theme directory

I care a lot about the experience users get when they visit WordPress.org’s themes section. Ultimately, the quality of that experience is the driving force behind all WordPress.

In a sense, the end user doesn’t care about the software itself. They care about how it performs, and chief of all, how their sites look.

Quite naturally, the themes available in the official directory will be the starting point for most new users coming to WordPress for the first time. Even though premium marketplaces and theme stores have made their mark on the landscape, they are still – in my belief – a secondary place to go if someone needs a theme.

Frankly, for nearly everyone, the path is:

  • Need a theme > go to WordPress.org > nothing there? > go to Google > go to a marketplace

On that path, WordPress.org and the themes offered there are key.

If the themes become too hostile towards end-users – users who are not developers – they won’t even care to check alternative theme repositories … they will just leave WordPress as a platform altogether. And go to Squarespace or whatnot.

For that reason, again, what is in the WordPress.org’s theme repo is key. And it’s key to all our careers in the WordPress business. No matter if you’re building free themes, paid themes, WordPress.org-hosted ones, ThemeForest themes, or themes sold via an independent store; WordPress.org is a crucial stage on your user’s path to discovering you.

But despite its value, your relationship with WordPress.org can be a love-hate one…

I need to be honest with you … things haven’t been easy for us regarding the official theme repository.

As you may or may not know, Zerif Lite is our most popular free theme, with over 200,000 active installs, and it’s it was also a mainstay on the WordPress.org’s list of the most popular themes.

zerif lite installs

Over the years, the theme has been recognized by end-users, and has been an inspiration for other developers when building their themes.

But Zerif Lite has also been causing some inconvenience to the theme review team at WordPress.org. Long story short, the theme has been facing a possible suspension from the directory, and was given two weeks to fix all its alleged issues.

That was two weeks ago.

As of this writing, Sep 14th, Zerif Lite has indeed been suspended, and you are not able to get it through WordPress.org anymore. Going to https://wordpress.org/themes/zerif-lite/ gives you this:

zerif lite missing

Two things before I continue with the topic:

  • I don’t intend to make this a public drama kind of post. This is more about how we can avoid these situations in the future, and how other developers can approach similar problems if they ever come across them.
  • I won’t talk about the individual details regarding the issue, or anything like “how we are right and they are wrong.” This is not the purpose. We have our rights and wrongs on either side, and I don’t think it would be all that cool if I just poured out our grievances here in hope to get the community on our side.

So, like I mentioned at the beginning, because I care a lot about the experience users get when they visit the themes repo, I’d like to take this opportunity to talk about the problems with the whole environment itself, and discuss the possible ways of improving it.

(For those of you interested in the Zerif Lite issue, you can just hop over here – the official ticket at WordPress.org.)

On building WordPress.org themes, getting them approved, and then banned

From a developer’s perspective, building a *new* theme – with an emphasis on *new* – and then having it included in the WordPress.org repo is more or less a straightforward process. (Please bear with me.)

What I mean is that there are rules to follow, and if you do follow them well enough, you’ll get accepted. I’m not talking about the complexity or the utility of those rules. It’s just about the fact that certain rules need to be followed if you want to be included.

And that is fine.

But over time, when rules get changed – new guidelines being introduced, old guidelines removed, etc. – you might find yourself in a tricky situation.

The current WordPress.org repo landscape is divided into two parts, more or less:

  • When a new theme is submitted, it gets reviewed, and if it’s in tune with the guidelines, it goes online.
  • But the process isn’t as straightforward for existing themes. Any existing theme can be, at any point in time, brought to the review team’s attention as not being in tune with the newest set of guidelines.

The latter is most likely going to happen when authors of other new themes start asking, and rightfully so, “Why my theme can’t do Thing X, but this old theme over here can?”

At that point, you may be requested to update your theme so that it adheres to the most up-to-date rules, which seems reasonable. But this is also where the problems (can) start.

First, let’s set one thing straight. If any changes you’re requested to do eventually lead to a better overall product then this is all a non-issue. You’re simply getting someone from the theme review team doing the research work for you, and pointing out how exactly you can make your theme better. Great!

The real problems start when the changes forced on you aren’t necessarily good for the end-user.

Why would that ever happen?

This is a bit tricky, but I hope I can explain what I mean:

To begin with, let’s keep in mind that any theme previously accepted into the repo was 100% in tune with the rules at the moment of approval. So we’re not talking about a situation where a theme refuses to cooperate altogether.

Now, about rules themselves:

I don’t want to argue that the current theme rules are worse than they were, or the other way around. Rules are rules. Essentially, building a new product according to “Rules A” or “Rules B” is similar in nature. You just need to follow certain steps. However, the story is entirely different when moving from “Rules A” to “Rules B.”

Here’s the thing; as a theme developer, you might find yourself in a situation where your theme is perfectly user-friendly and perfectly okay with the rules at the time it was submitted. Then … new rules get introduced, and they seem reasonable too. However, right there, right there in the middle, lies the transition itself.

And that transition alone is rarely user-friendly.

What it all comes down to is that if you’re requested to remove a big chunk of your theme functionality just to be compliant with the new rules, what do you think happens to the theme’s current users when you make that move?

Yes, you are right, their sites stop working! Or maybe not stop working, but they lose the functionality that they were told they would get when they first installed the theme.

Essentially, you’ve promised them that each update will make their experience even better, yet you’re doing something exactly opposite. In an extreme scenario, you might render the theme useless.

Just to give you an example to explain what I mean. One of the things that we’ve been requested to change with Zerif Lite is using “faux custom post types.” Basically, this is about using those small custom content blocks that appear on the homepage of the theme to present things like team info, about block, testimonials, etc. Example:

team

Those are used just on the homepage and nowhere else. According to the current rules, we should have set true custom post types for those. This, kind of, makes sense if you’re building a new theme, but changing this in an existing theme means that whoever’s currently using it will get their site messed up. And in our case that means 300,000+ people (including the child themes).

So depending on what sort of changes you’re requested to carry out, the situation can be really difficult, it’s basically the hammer or the anvil:

  • On the one hand, if you don’t make the changes, you’ll be banned from the repo.
  • If you do make the changes, you stay in the repo, but you’re messing up the sites of your current users.

Which is worse?

Let me tell you how I see this from my own perspective.

I’m – we are – all about building products that follow the principles of “user first.” We want our stuff to be helpful, useful, and reliable. If we’re suggested a change that will make everyone’s experience better, we’re all for it!

But if the changes can lead to making our users’ lives exponentially more difficult, then we cannot take that step and feel good about it. It would be us betraying our users and customer base.

Ultimately, ending with a worse product/experience is not something that we care much about. In my view, disrupting the current user experience is just not worth it, and until we find a way to keep that user experience intact – and in a way that the review team is cool with (so far, our suggestions haven’t been received well) – we will have to stay suspended from the repo.

Sure, this will diminish our revenues a lot. Company-wide, I’m estimating probably around a 50% sales decrease post WordPress.org repo suspension.

This would certainly require quite a lot of optimization, but we are glad to be in a position where we can afford to do only what is best for our customers and us – the company – in the long run.

The solutions

The situation isn’t an easy one, and not only for us, but for other theme developers that have faced similar problems in the past, or are facing them right now.

I have a couple of propositions that could be the basis for discussion when we’re searching for viable solutions:

1. Not making the rules retroactive

I don’t believe that any one theme should be treated differently based on its reputation, popularity or whatnot. But, at the same time, I also don’t believe that any rules or laws should be retroactive.

As a rule, law is not retroactive; it affects only future activity, that is, what will take place after the law has gone into force.

Having similar rules in the directory would certainly help. And this would be quite simple:

  • If your theme got accepted to the directory and was found to be in-tune with then current rules, then it’s good to stay like it is.
  • Only if you want to submit an update that goes above critical bug fixes, you need to make it in-tune with the newest rules.

2. Introducing minimal requirements

The repos are working towards automation. We simply have too many themes and plugins submitted every single week, so doing human review for each addition is both too time consuming and also probably leaves a lot of room for oversight.

So one path we can take with automation is to just accept every secure and safe theme into the directory, and then have a better search algorithm (what plugin repo is doing) that would display the best match first (based on various factors).

I believe it to be both the easiest and the best thing we can do.

In a scenario like that, developers have more freedom and can experiment with various unusual solutions. See this quote:

Matt comment

Or this one; also Matt Mullenweg :

We have a lot of hard and strict rules designed to “protect” users, like around CPTs et al, but someone could make an informed decision to trade off future potential portability for current form or functionality. it would be a perfectly rational decision to make.

For example, Amazon takes advantage of their search mechanism to the max. It’s a free market economy there, basically. Good products get good reviews, so they come up higher in the search results. Bad products get buried. It’s the community of buyers that regulates it.

Having something like this for WordPress.org theme search would be awesome!

3. Allow on-boarding

Themes are sometimes incredibly complex pieces of software, and expecting the user to simply click the “activate” button and then be done with everything that needs their attention is just mad.

Being able to on-board new users is key to helping them configure their new theme, and also learn how to get all its benefits. This could help us to offer a great “look like the demo” experience, while focusing on what is good for the users at the same time.

4. Having a better previewer

This is maybe not 100% related to the issue at hand, but I do believe it’s crucial for the overall usability of the WordPress.org repo.

Quite simply, the current previewer is useless.

Its uselessness is all about making the preview look nothing like the theme screenshot.

This just needs to be better. Theme authors need to be able to tune up the previewer to really display an optimized demo – something that actually gives the user a good overview of what the theme has to offer.

What’s next for Zerif Lite users, post WordPress.org suspension

A couple of important things:

(a) We still love the theme and will keep it alive

Hey, Zerif has grown to be one of the top 5 most popular themes on WordPress.org for a reason. It is awesome! And we still believe in it wholeheartedly.

This means that we will still continue working on it and make it even better.

(b) You can still download Zerif Lite

Just go to our site and get Zerif Lite from there (no opt-in required).

zerif lite

(c) You can still get support

You can visit the main support section here. There you can find our in-depth documentation guides, FAQs, and also a way to contact us.

To get priority support, consider joining our theme club (premium).

(d) Contact us if you downloaded Zerif Lite through WordPress.org

Here’s the core of the problem: If we upload a theme to WordPress.org, we can’t have an update script added to the package. This means that if we want to deliver updates at any time in the future, we are forced to keep that theme on WordPress.org.

In our case, with the theme getting suspended due to the change of rules (without a reasonable way to fix things), more than 300,000 users have been put at risk due to using a theme that cannot be updated.

Even worse, we don’t know who those people are, so we can’t communicate with them. So basically, those aren’t “our users” anymore, even though we still appear as the developer of the theme.

For example, if a security issue is reported to us, we can’t do anything, yet we will still be blamed. This seems to be a pretty big thing.

So in the end, reach out to us if you’re a Zerif Lite user. Let’s keep your theme safe and secure.

 Update. The simplest way to keep your copy of Zerif Lite up to date is to download this new plugin of ours. All you need to do is install and activate it. Your Zerif Lite updates will happen automatically from that point on. 

(e) What’s next for us, business-wise

Like I mentioned earlier, I’m estimating probably around a 50% sales decrease as a result of this.

Obviously, we need to cut down on things and optimize. Here’s what we’re going to do in the near future:

Reduce costs

  • Cancel software subscriptions that we don’t use that often, or frankly don’t need (sorry, Mixpanel).
  • Stop doing sponsorship for the time being (less WordCamps, pods.io, etc.) … Essentially, less users means less support, which will allow some support members to work on the development side of the business, which they are perfectly capable of doing.
  • Lower some AdWords bids, and focus more on efficiency rather than reach. The same goes for re-targeting ads.

Reach out to our community

  • Inform as many users as we can and guide them through the process of keeping their theme up-to-date.
  • Inform popular news sources in the community.
  • Inform bloggers and content producers who linked to us in the past to edit/update their articles.
  • Direct everyone to the theme’s page on ThemeIsle.com, where they can download it without an email address.

Proceed with caution

We need to wait 48 hours or so to see how the community reacts to this whole thing, and also how effective we are in reaching our current users.

We’re releasing another post on the ThemeIsle blog, explaining the situation to our users and instructing them what to do going forward. We’ll also email everybody and do lots of re-marketing to get people on the new version of the theme.

Long term, we will need to wait a bit and see where we are, how bad/well things are going, and work from there. Nothing we can’t do.

In the end, I hope that by making our points here, we can help change things for the better, and also help out other theme authors who might be facing similar problems.

I also hope that we will be able to get the theme in the repo eventually, and, more importantly, that our users won’t suffer too much in the meantime.

As always, thanks for reading and for supporting CodeinWP! Stay updated and get new reports delivered to you by subscribing here:

All edits and witty rewrites by Karol K.

Ionut Neagu

Love to travel, share and help others, I am working with WordPress at ThemeIsle.com. Passionated by Growth Hacking and the big things around me (trying to understand people, society, economy and our world ).
  • An interesting read and sorry to hear that Zerif Lite has been banned. I use Zerif Pro so I am not affected, but seeing as there is such a broad customer base of Zerif Lite I feel your pain.

    I completely agree with the statement about making the rules not be retroactive with one exception that comes to mind: security – if there is a rule that needs to be changed (or created) which addresses security then this should be retroactive.

    I was wondering (and I make this suggestion not knowing how the Zerif Lite configurations etc are stored within WordPress database), as the changes required to make the Zerif Lite theme ‘compliant’ are so large, could you make the changes and get the theme reinstated, but with a migration tool built in that looks for a version less than or equal to the last version available before the ban, and if found when updating then the migration tool grabs the existing configuration and ‘reworks it’ to fit with the new ‘compliant’ theme?

    Just a thought… good luck!

    • Hey David,

      Thanks for your comment and for being a customer, I hope you are happy with Zerif Pro :).

      As for your suggestion, the problem is that we were not offered a solution to migrate custom widgets like : our team etc, also on another note we don’t believe that when we are talking about not so much data, designed just for 1 page, we should recommend a plugin which will create a Team custom post type, for most of the users this won’t be a better option.

      So is not only that we can’t get the theme added back, but we don’t want to have it there in a worst shape that it was and in the process affect the website of our users, this just for some short term $$. We will rather focus on developing better products ( at least what we consider better) and to serve our users, things that I hope in the long term will help us to be #1.

  • Thanks so much for the behind-the-scenes look at why a theme would be banned from the theme directory. In order to become compliant you’d need to make changes that would break people’s existing Zerif Lite’s sites? What a rough spot to be put in!

    • Yes, a lot of content will be lost + after upgrading you will have to install a plugin to add the functionality back.

  • Frank

    This is a very sad state of affairs. I agree with you on the point that new rules should not be retroactive unless they are security related. I think the WordPress theme directory is being too strict in this case and is causing harm to the community.

    Functionality plugins included with a theme are no better than bundling the code into the theme because they rarely work with any other theme. A Lot of modification is usually required to make them display the content properly thus rendering the argument that content shouldn’t be locked into themes moot.

    I hope this gets resolved and others can learn from it. At the very least they should allow you a migration script.

    I’m a theme author myself and over the last year or so releasing a new theme has become increasingly difficult. New obscure rules that change without warning, excruciatingly long review queues and very high competition for commercial themes.

    At this rate the WordPress community is going to lose a lot of developers to simpler technologies.

    • Hey Frank,

      Is just probably what is best for both us and repository in the current context, of course I would have loved to see less strict rules and a more democratized repo.

      Complaining won’t help here, we did what we thought is the best and we’ll look at further solution to see how we can build better products which the community can enjoy using 🙂

  • Woow. This is an interesting read, highly informative and actionable information. You have analysed the whole scenario pretty well and explained in a easy to understand manner. You have taken responsibility and are dealing with the situation in the best possible manner. Well done and keep up the good work please. Cheers.

    • Hey,

      I am glad to hear you have found this helpful!

  • Gaurav Agrawal

    Well, you seem to have misinterpreted your target users on the issue (trac) page. Being a user of WordPress since 2008, I would think of myself as an experienced user, specially since I do a lot of plugin development for WordPress and woocommerce. Zerif lite has been my default theme for about 2 years now. It is the first theme that gets installed on all my client sites after WordPress installation. The news is disheartening, but I don’t want to create a panic for my clients, so will keep watching this space.
    Thanks, for keeping the theme available and allowing a mechanism for future updates even if the worst comes to pass.

    • jameskatt

      The developer simply has to create Zerif New Lite – the corrected version of Zerif Lite. Then they can submit it to WordPress. Users of the old Zerif Lite can keep getting updates from the developer. They can also switch to Zertif New Lite.

      • Hey,

        We will at some point release a new version of Zerif, not sure if it will be in the repository or not.

        Thanks for suggestion!

    • Hey Gaurav,

      You are right, there both beginners as well as experienced users of Zerif, the goal here was more to inform the community about the news, nothing will be different once you re-download the latest version from our site or install the transition plugin :).

  • Gil C

    Interesting read. Thanks for this. As for me, I just downloaded the theme last week from the main website itself and by far, this is the easiest theme I have configured. I’m not a hardcore coder nor can be called a developer because I rely heavily on themes. I am using this theme not just for my clients but as for my website as well (under maintenance). More power and thank you for making this theme!

  • Ron

    What a load of horse shit.

    You had 16 MONTHS to fix this issue. You were contacted many tines about this. You chose to do nothing.

    You have nobody to blame but yourself.

    • Hey Ron,

      I am sorry that you feel that way, maybe the article isn’t clear enough so I will try to make my point again :

      As in the previous reports the goal here is not to complain, we stated that we will probably lose 50% of the revenues, as we stated that we grew by 1500%, we haven’t done this to complain, nor to brag ourself, I did it because I wanted to be transparent, because I thought that others might learn from my experiences. Some will get a better idea about market potential by sharing revenues, while others might be more careful while sharing our failures.

      Rules are rules, we are aware of them and we took the decision that we thought is the best, so we don’t blame anybody nor us :).

      I understand that it might be hard to grasp that I am just trying to share and help.

  • I really appreciate your openness and sharing about this Ionut While we all know the need for quickly enforcing upgrades for themes and plugins when there is a security issue(s), it often seems that the WordPress forced “upgrade or die” approach leaves the needs of our clients behind.

  • Great article… in fact i was surprised to learned that my theme needed 6 months to be reviewed from WP repo… however the fact that they are very strict about their rules is a good thing.
    What i have chossen is that i will sell my themes from my website and well… make my own rules!

  • Issa Bacsa

    While I was browsing WP themes, I found out that Zerif Lite is no longer in the selection. I saw this article and realized that the theme I’m using was suspended for reasons only developers and WP people know. I’m not a web developer, but I’ve used Zerif Lite since 2015 and still using it on my personal website. What I like about this theme is I can customize it the way I like it and I’m satisfied with the results. What will be the implication of this suspension for us end-users? I remembered updating the theme a few weeks back then this. Is there an alternative theme in case Zerif Lite is no longer supported by WP? Thanks!

    • Hey Issa,

      For you as a user nothing change after you either update the theme from our site or add the transition plugin, is not that the theme is no longer supported by wp, is just that the theme won’t be listed in the official repository.

      Thanks!

  • Robtamarindo

    No making the rules retroactive? Your theme’s JS and CSS are so heavy that it takes sites a long time to lead above the fold, making it not as mobile friendly as it was intent to. Not to mention the declined on search ranking and high bounce rates. You guys should fix the scrip loading issue, or stop the theme all together and not let new users fail into believing that their theme is going to help them on their mobile/google success.

  • Thomas Madigan

    No making the rules retroactive?! Your theme’s JS and CSS are so heavy that it takes sites a long time to lead above the fold, making it not as mobile friendly as it was intent to.

    Not to mention the declined on search ranking and high bounce rates. You guys should fix the scrip loading issue, or stop the theme all together and not let new users fail into believing that their theme is going to help them on their mobile/google success.

  • Seo Sem

    No making the rules retroactive? Your theme’s JS and CSS are so heavy that it takes sites a long time to load above the fold (even your sample theme is slow)– making it not as mobile friendly as it was intent to. In other words, your theme is too old.

    Not to mention the declined on search ranking and high bounce rates the theme is now causing to users due to updates on google rules and increase on mobile use. You guys should fix the scrip loading issue, or stop the theme all together and not let new users fail into believing that their theme is going to help them on their mobile/google success.

  • Sabina Ionescu

    You are right.
    Zerif Lite is live and kicking in the most popular themes page WP.org 🙂