5 Things I Don’t Like About WishList Member

Almost a year ago we started developing a web project for a client on a social networking basis. This was actually the second similar project for the past 2 years as we have also designed a dating site and the latter solution was a social networks with custom profiles and more. There were a few tricky features such as custom profile type creation (different professions to be defined with their fields and labels through admin) and financial stats for paid users, and the speed was an important requirement.

After some hardcore coding over 2 client-based websites using WishList member and comparing the amount of hours for development of the three projects (two projects here and the one I used to manage a year back) I’m pretty sure we could have done this in WordPress using this social networking plugin. It has paid members with expiring registration and a smart PayPal compatibility, different roles to be defined, registration pages, granular protected content for roles (including menu items). Pretty cool indeed.

However, as with an every single one piece of code that is not a custom module for the given project, here there are the top 5 reasons I don’t like WishList member although I find it being a pretty powerful tool.

  1. Paid. Yes, top plugins such as GravityForms are not free. I can live with that, developers had put tons of effort to make them user friendly, feature rich and stable. True story, but only if and when bullets 2 and 3 were covered.
  2. Encrypted. The WishList Member code is encrypted and protected from any modifications. I can’t even explain you the amount of hours involved to lookup the terribly documented hooks and the flow of the plugin, and also pimping some really simple and basic layout blocks. As the code has been denied from modification, I’m usually in the black box not being able to debug what happens nor even change it. It sucks big time.
  3. Poor support. The support forum has hundreds of questions with no answers. I can hardly find answered questions, and I filed a ticket 3 weeks ago that I believe is still unanswered.
  4. Dummy user guides. As the code is protected, the only video materials and documentations that I find usable are the user-based ones – how to use the straight-forward part of the system. A real project never gets in a way that the plugin could fulfill 100% of the requirements with its straight options. And the lack of fulfilling details on the core is absurd. After all we have some other requirements such as multilingual content and geo-based location conditions, so this misty lake is not the best place to swim in.
  5. Lack of custom profile integration. New profiles for the system extend the standard users module, but using it as a social network usually requires a custom post type for a better usability of the new profiles – such as featured images, tags and more. I believe it would be more appropriate to create a bridge between the standard registration and some custom post type.

The system itself is really a lot powerful, but the lack of a realistic customization and the auto magic on the back could dig the project way down. I have troubles editing the registration template as the only easily modifiable thing is the registration form panel with the fields (which is also poorly alterable according to my requirements). Or adding custom rules to the navigation menu. Or setting different default language for a given role. Aside of that the profile saves me hundred of hours for protecting even the post types content, taking care of paid users entirely and other fancy details.

 

4 thoughts on “5 Things I Don’t Like About WishList Member

  1. Wishlist Member support team is quite good in my opinion. They solved every problem I had with the plugin very quickly. I saw you wrote this review about a year ago, so I guess they had improved since then…

    1. I believe it is worth mentioning that you are a part of some affiliate campaign or something like that for wishlist products, aren’t you?

      However, my biggest concern is the obfuscated codebase. In an open source and GPL-driven world it doesn’t make sense at all.

  2. Great rant, couldn’t agree more. WLM is very expensive to use because it costs hours of hunting through source code and database schema, trying to reverse engineer how it does things so you can shoe-horn it into your own requirements. This obfuscation is Microsoftesque, narrow minded and petty. Hey WLM Help us to help people and enjoy the benefits of geek kudos, why don’t ya!

Your thoughts?